How to Fix Teams Microphone Not Working

“Can you hear me now?” is the most-asked question on any call, and a dead Teams microphone is usually why. The good news is that a mic that won’t pick up your voice is rarely broken hardware. Most of the time it’s the wrong device selected, a Windows privacy toggle switched off, or a headset that quietly handed the mic to the wrong profile.

This guide works through the causes in the order they actually happen, from the quick wins to the deeper fixes. Each step takes under a minute, and the Teams test call gives you a fast way to confirm whether each change worked before you move on.

Start with the device selection in Teams#

The single most common cause of a dead mic is the simplest: Teams is listening to the wrong microphone. This happens constantly on laptops with a built-in mic plus a headset, or when a virtual audio device from other software sneaks into the list.

Open Settings > Devices in Teams and look at the Microphone dropdown. Pick your actual mic, then watch the input-level meter under it while you talk — the bar should move. If it stays flat, that device isn’t hearing you, so try the next one in the list.

If the dropdown is empty or only lists a mic you don’t physically have, Windows isn’t presenting the device to Teams. That points at permissions or a driver problem rather than a selection mistake — covered further down.

Check Windows microphone privacy settings#

This blocks more mics than people expect, and it’s the first place to look on Windows 10 and 11 when the device picker looks right but still captures nothing. Windows has a master switch and a per-app switch, and both have to be on.

Go to Settings > Privacy & security > Microphone and confirm:

1. Microphone access is on (the system-wide master switch).
2. Let apps access your microphone is on.
3. The toggle for Microsoft Teams is on.

That last one is where the two clients differ. New Teams appears in the app list with its own toggle. Classic Teams runs as a traditional desktop program, so it falls under Let desktop apps access your microphone instead of having its own named entry. If you only see “Desktop apps,” that’s the toggle classic Teams relies on.

Headset and Bluetooth quirks#

Headsets are responsible for a surprising share of “they can’t hear me” tickets, because a single headset can register as several devices and switch profiles on its own.

A USB or Bluetooth headset often shows up as more than one entry in the device list — one for the headset mic, one for the laptop’s built-in mic, sometimes a separate one for speakers. If Teams picked the laptop mic while you’re talking into the headset, your voice goes to a mic pointed at the wrong place. Always confirm the Microphone dropdown names the headset, not “Internal Microphone.”

Bluetooth adds its own twist. A Bluetooth headset has two modes:

• A2DP (stereo) — high-quality audio, but the microphone is disabled.
• Hands-free / headset (HFP) — the mic works, but audio quality drops to a narrow, muffled band.

When Teams starts using the mic, Windows switches the headset from stereo to hands-free, which is why music sounds great until a call starts and then everything goes tinny. If a Bluetooth headset mic won’t work at all, or sounds awful, disconnect and reconnect it, or switch to the wired/USB option for anything important.

Turn off exclusive mode#

If the right mic is selected and permissions are on but Teams still captures nothing, a Windows setting called exclusive mode may be letting another app take sole control of the device. When that happens, Teams is locked out.

Fix it in the classic Sound control panel:

1. Right-click the speaker icon in the system tray and open Sound settings.
2. Scroll to More sound settings (this opens the classic Sound dialog).
3. On the Recording tab, double-click your microphone.
4. Go to the Advanced tab and clear Allow applications to take exclusive control of this device.
5. Click Apply, then restart Teams.

Sound settings > More sound settings > Recording tab
  > [your mic] > Properties > Advanced
  > uncheck "Allow applications to take exclusive control of this device"

While you’re on the Recording tab, check the mic’s Levels too. A microphone with its volume dragged to zero, or muted with the small speaker icon, behaves exactly like a broken one. Bump the level up and unmute it if needed.

Update, roll back, or reinstall the audio driver#

If Windows itself can’t capture from the mic, the driver is next. Open Device Manager and expand Audio inputs and outputs (and Sound, video and game controllers for the underlying audio device).

• A yellow warning triangle means the driver failed to load. Right-click and choose Update driver.
• If the mic broke right after a driver update, open the device’s Properties > Driver and use Roll Back Driver to return to the version that worked.
• If neither helps, Uninstall device, then reboot. Windows reinstalls a stock driver on restart, which clears a corrupted driver state.

For USB headsets and mics, try a different USB port — ideally one directly on the machine rather than a dock or unpowered hub. Docks are a common reason a USB audio device drops out intermittently.

1. Win + X  >  Device Manager
2. Expand "Audio inputs and outputs"
3. Yellow triangle?  -> Update driver
4. Broke after an update?  -> Properties > Driver > Roll Back Driver
5. Still failing?  -> Uninstall device, then reboot

Clear the Teams cache as a last resort#

When device selection, permissions, exclusive mode, and drivers all check out but Teams still won’t capture audio, a corrupted cache can be the culprit. It can leave the device picker stuck on a mic that no longer exists or stop the app from enumerating audio hardware. Clearing it forces a clean rebuild on the next launch.

Fully quit Teams first — right-click the tray icon and choose Quit, or end the process in Task Manager. The cache can’t be cleared while the app is running. Then clear the folder for your client version.

For classic Teams you can do it from PowerShell. Quit Teams, then:

Get-Process -Name Teams -ErrorAction SilentlyContinue | Stop-Process -Force
Remove-Item -Path "$env:APPDATA\Microsoft\Teams\*" -Recurse -Force -ErrorAction SilentlyContinue

After clearing, relaunch Teams, sign in, and rerun the test call under Settings > Devices. The first load is slower while the cache rebuilds.

Still silent? Narrow it down fast#

If you’ve worked through everything above and Teams still won’t pick up your voice, a couple of quick splits will tell you where the fault really lives:

• Test the mic in the Windows Sound settings. On the Recording tab (or Settings > System > Sound), speak and watch the input meter. If Windows sees no input, the problem is Windows or hardware, not Teams.
• Test Teams in a browser. If the web client captures your voice but the desktop app doesn’t, the desktop client is at fault — recheck device selection and clear the cache.
• Test on another machine. If the headset or mic works elsewhere, your original machine has the problem. If it fails everywhere, the mic itself may be dead.

For the broader set of meeting faults — join failures, dead cameras, screen-share trouble, and choppy audio — see the full Microsoft Teams meeting troubleshooting guide. If your camera is also misbehaving, the camera fix walkthrough follows the same logic.

Wrapping up#

A Teams mic that won’t work almost always comes down to the wrong device selected, a Windows privacy toggle that’s off, or a headset switching to the wrong profile. Run the test call, fix the device selection, confirm the privacy switches, and only then chase exclusive mode, drivers, and the cache. Working top to bottom keeps you from reinstalling drivers to fix something that was really a setting flipped off after the last update.