Microphone Not Working in Microsoft Teams: How to Fix It

A microphone not working in Microsoft Teams is often a mute you never set — the organizer applied it. Teams gives hosts a hard mute, and a blocked permission or the wrong input device explains most of the rest. In each case the hardware stays perfectly healthy while your voice never reaches the meeting. It has to clear several stages first: the capsule, the operating-system privacy layer, the input Teams has selected, and finally the meeting's own mute controls. A break at any stage sounds identical from the other side. This guide checks each in order. Confirm capture first with a test call under Settings › Devices, or our microphone test. Then work through mutes, device selection, and the operating-system permission behind most reports. The closing sections cover the browser version, a Bluetooth profile trap, and the cache clear that revives a stubborn desktop client.

Microsoft Teams Microphone Not Working: Quick Fix Checklist

✓	In Settings › Devices, pick the mic and use Make a test call.
✓	Unmute, and ask the organizer to lift any hard mute.
✓	Grant the operating-system permission for Teams (Windows or macOS).
✓	Clear the Teams cache, then relaunch.
✓	For the web version, allow the browser’s microphone permission.

Test your microphone inside Microsoft Teams

Confirm that Teams hears you before you change any setting. The new Teams desktop app includes a dedicated tool for this. Open the Settings and more menu (…) beside your profile picture, then choose Settings › Devices. The Make a test call feature records a short message and plays it back. If you hear your own voice, the microphone and its permission are working. The problem then sits in the meeting itself, most often in mute. The same Devices panel holds the Microphone dropdown. It names the exact input that Teams is sending. The pre-join screen offers a second checkpoint. Before you select Join now, open the device settings and confirm the microphone there. A check at this screen catches a wrong device before the meeting begins. A browser-based test gives an independent second opinion. Our online microphone test reads your input level in real time, outside Teams entirely.

Test Your Microphone →

Teams exposes the microphone in several places. Knowing which one to trust saves time. The most reliable check is the test call, because it proves capture and playback together. The Microphone dropdown then confirms which device carried that voice. The table below maps each control and states what a reading in it confirms. Use it to decide whether a fault is a mute state, a device choice, or a permission block. Each row points you toward a different section of the fixes that follow.

Where to look	Path	What it confirms
Test call	Settings › Devices › Make a test call	Records your voice and plays it back through Teams
Microphone dropdown	Settings › Devices › Microphone	Which input device Teams is sending to the meeting
Pre-join device picker	Meeting join screen, before Join now	The input selected as you enter a call
In-call device settings	More (…) › Settings › Device settings	A device change without leaving the meeting

Why Teams stays silent when the microphone works

Mute and the organizer's hard mute

Mute is the most common reason a healthy microphone produces no sound. Teams shows a microphone icon with a slash when you are muted. A single click restores your voice. Keyboard shortcuts and headset buttons can mute you without your noticing. Large meetings add a second layer. An organizer can apply hard mute to keep a session orderly. Hard mute prevents attendees from unmuting themselves at will. You then see a mute state that your own click cannot clear. The remedy is social rather than technical. Ask the organizer to allow you to unmute, or to unmute you directly. Presenters and organizers are exempt from the restriction. This distinction matters when troubleshooting. A microphone that passes the test call but stays muted in one meeting is not broken. The meeting is controlling it. Always separate a device fault from a meeting policy before you change any setting.

The wrong input or a Bluetooth profile

Teams keeps its own device selection, separate from the operating system. It can point at an input you no longer use. You then speak into a headset while Teams listens to the built-in microphone. Bluetooth headsets add a familiar complication. A wireless headset offers two profiles. One is high-quality stereo for listening only. The other is a lower-quality mode that also carries the microphone. When the headset stays on the stereo profile, Teams plays audio but captures no voice. Reconnect the headset and select its hands-free entry in the Microphone dropdown. The label often reads "Hands-Free" or "Headset" rather than "Stereo". Suspect device selection first whenever the microphone works only sometimes. A meter that reacts in the test call but not in a meeting usually points to the same mismatch.

The operating-system gate and rival apps

Teams cannot hear you until the operating system allows it. Windows and macOS both place a privacy gate in front of the microphone. Teams receives silence when that gate is shut, and no error message appears. A second application can also seize the microphone for itself. Some devices let only one program hold the input at a time. If Zoom, a browser, or a voice recorder grabbed the microphone first, Teams finds it busy. Close the rival application, then restart Teams. A corrupt application cache produces a similar silence even when every setting looks correct. These deeper causes are less frequent than mute or device selection. They are still worth ruling out early, because each is quick to check. The next sections show exactly where each permission and each reset lives.

Fixing Teams, from the most common cause down

Work through these fixes in order. The sequence resolves the most cases first, with the least disruption. Do not jump to clearing the cache before you have confirmed the mute state. Return to the test call or our microphone test after each change. Re-check for a signal before you move on. That way you always know which step made the difference.

Clear the mute, then pick the right device

Start with the mute icon in the meeting toolbar. Click it once and watch whether the slash disappears. If the icon will not change, hard mute is active, and only the organizer can release it. With mute cleared, open Settings › Devices. Set the Microphone dropdown to the input you intend to use. Do not trust whatever Teams selected for you. Run Make a test call and listen for your own voice on playback. If the test call reproduces your voice but the meeting does not, leave and rejoin the call. Rejoining forces Teams to reload the device you just selected.

Open the operating-system microphone gate

Teams needs permission at the system level. On Windows, open Settings › Privacy & security › Microphone. Enable both Let apps access your microphone and Let desktop apps access your microphone. The second toggle is easy to miss and blocks the classic desktop app. On a Mac, open System Settings › Privacy & Security › Microphone and switch on Microsoft Teams. Our Windows 11 and Mac guides walk through these privacy panels in detail. Grant the permission, then restart Teams so it rechecks its access on launch.

Clear the Teams cache when the settings look right

Suppose the correct device is selected and the permission is granted, yet Teams stays silent. The application cache has probably become corrupt. A stale cache can freeze the device list or ignore your selection entirely. The fix is to quit Teams completely and clear its cache folder. Confirm that Teams is fully closed first, including any icon still running in the system tray. Relaunch the app afterwards. It rebuilds the cache and rescans your audio devices on the next start. Sign out and back in if the device list still looks wrong. The matrix below pairs each symptom with its likely cause and the fix that resolves it.

Symptom	Likely cause	Fix
Nobody hears you; the mic icon shows a slash	You are muted, or the organizer applied hard mute	Unmute yourself; ask the organizer to release hard mute
The test call plays back silence	The wrong microphone is selected in Teams	Choose the correct input in Settings › Devices › Microphone
Teams hears nothing, but other apps do	Teams lacks operating-system microphone permission	Enable Teams in the Windows or macOS microphone privacy settings
The headset plays audio but captures no voice	The Bluetooth headset is on the wrong profile	Reconnect it; select its hands-free entry in the dropdown
The microphone list is empty or frozen	Another app holds the device, or the cache is corrupt	Close the other app; quit Teams and clear its cache
Every setting looks correct, yet still no sound	The Teams cache is corrupt	Quit Teams, clear the cache folder, then relaunch and sign in

Testing and fixing Teams in a browser

The web version at teams.microsoft.com behaves differently from the desktop app. It does not use the operating-system permission directly. Instead it relies on the permission you grant the browser. The browser asks to use your microphone the first time you join a call. If you dismissed or blocked that prompt, Teams on the web hears nothing. Open the site permissions and set the microphone to Allow. The exact route depends on your browser. Our Microsoft Edge and Google Chrome guides cover each permission panel. The browser still sits behind the same operating-system gate. Confirm that your browser itself is allowed in the Windows or macOS microphone settings. The Devices panel inside web Teams works like the desktop version. Choose your input from the Microphone dropdown there, then reload the tab if the change does not take hold.

Keeping your Teams microphone reliable

A few habits keep Teams dependable once the sound returns. Keep the app current. Microsoft ships frequent audio and Bluetooth fixes through automatic updates. Sign out and back in after a major update if devices start behaving strangely. Review your operating-system microphone permissions from time to time. Switch off access for apps that have no reason to listen. Pin your intended input in Settings › Devices so Teams stops re-electing a stray headset. Test the same microphone across every app you rely on. A microphone that is flawless in Teams can still be blocked in another tool. Our Zoom and Google Meet guides help you confirm each one. Run a quick browser-based test before an important call. It proves the hardware in seconds, independent of any single application.

Frequently Asked Questions

Why can nobody hear me in Teams even though my microphone works?

You are almost certainly muted. Check the microphone icon in the meeting toolbar for a slash. If your click will not clear it, the organizer has applied hard mute. Ask them to let you unmute. Otherwise confirm the correct input under Settings › Devices.

How do I test my microphone in Microsoft Teams?

Open Settings › Devices and choose Make a test call in the new desktop app. Teams records a short message and plays it back to you. Hearing your own voice confirms the microphone and its permission. Our online microphone test gives a quick browser-based check outside Teams.

Why does Teams not detect my microphone at all?

The device list is usually empty for one of two reasons. Either the operating system blocks Teams, or the app cache is corrupt. Enable Teams in your Windows or macOS microphone privacy settings. Then quit Teams, clear its cache, and relaunch.

Why does my Bluetooth headset play sound but not capture my voice in Teams?

The headset is on its stereo listening profile, which carries no microphone. Reconnect the headset and select its hands-free entry in the Microphone dropdown. Avoid demanding high-quality audio and the microphone from the headset at the same time.

Does the Teams web version need different settings from the app?

Yes. The web version relies on your browser's microphone permission, not the app's. Set the microphone to Allow for teams.microsoft.com in your browser. The browser must also be permitted in your operating-system microphone settings.