Microphone Not Working on Microsoft Teams

Microphone Not Working on Microsoft Teams: Fix Guide

Microphone problems in Microsoft Teams come from three separate layers: OS microphone permission, Teams application audio device selection, and the hardware itself. Isolating which layer is responsible before adjusting settings saves significant troubleshooting time. A browser-based hardware test like this one confirms that the microphone is physically working at the OS level, independently of Teams entirely.

If the Noise Floor Grade returns any reading here, the microphone hardware and OS driver are both functioning. That tells you immediately that the problem is either Teams' device selection or Teams' microphone permission, not the hardware. Conversely, if the Noise Floor Grade fails here, the microphone problem exists below the Teams layer; it is in the OS audio driver or hardware. Fixing it there will resolve it in Teams automatically.

Check the hardware first

Run the Noise Floor Grade test. If you see any result, even a Noisy or Very Noisy grade, the microphone is active and accessible to browser applications at the OS level. This rules out hardware failure, driver malfunction, and OS-level permission denial as causes of your Teams problem. A successful Noise Floor Grade result proves that the microphone capsule is converting sound to electrical signals, that the USB or analog path is intact, that the OS audio driver is processing the stream, and that the browser permission is granted, all in a single three-second test.

Hardware baseline before Teams settings

The Clipping Detector can confirm that audio input is being received by watching for the input level indicator while you speak. If the Clipping Detector shows activity when you talk, the microphone signal is reaching the browser through the OS audio stack. This confirms the entire path from capsule to browser is functional, which means Teams should also be able to access the signal. Any Teams-specific problem at that point is in Teams' own device selection or permission settings, not in the underlying hardware or driver.

Once the Clipping Detector shows movement when you speak, the signal path is confirmed end to end through the browser, which is the same path Teams ultimately reads from. That makes the Noise Floor Grade a clean gate: hardware that produces any reading here is almost never the cause of a Teams-only failure, so your time is better spent in Teams' device menu than swapping cables or reinstalling drivers that are already working.

What the test results mean

Noise Floor Grade returns a result: microphone is working at the OS level. The Teams problem is in Teams' settings or Teams' own microphone permission. Go to Teams Settings > Devices > Microphone and verify the correct device is selected. Noise Floor Grade fails with "microphone not found": microphone permission is denied at the OS level, affecting both this tool and Teams. On Windows, check Settings > Privacy > Microphone and ensure both browser and Teams have access.

When the Noise Floor Grade works but Teams still shows no microphone

If the browser test succeeds but Teams reports no microphone, the issue is almost certainly that Teams is looking at a different audio device than the one the browser selected. Teams maintains its own device selection independently of the OS default¹, and it can cache a device ID that no longer exists after a USB microphone is reconnected to a different port. The fix is to open Teams Settings > Devices, manually reselect the microphone from the dropdown, and confirm the input level meter moves when you speak. This single step resolves the majority of "mic works everywhere except Teams" reports.

Platform-specific fix path

In Teams desktop app: Settings (gear icon) > Settings > Devices > Microphone. Verify the dropdown shows your intended microphone. In Teams web (browser): the browser's microphone permission for teams.microsoft.com must be granted, separate from the OS permission. Click the padlock icon in the browser address bar and check Microphone. In Windows 11: check that "Let apps access your microphone" is On under Windows Settings > Privacy & Security. Teams desktop and Teams web app use separate permission contexts, and the Teams desktop app uses its own embedded browser runtime that maintains a separate microphone permission from the system-level browser permission governing this testing tool². Granting microphone access to Chrome or Edge does not automatically grant it to the Teams desktop app, which has its own permission prompt the first time it accesses the microphone.

If you dismissed that prompt or clicked "Block" by accident, the desktop app will never access the microphone until you manually re-enable it in the app's permission settings or reinstall to trigger the prompt again. This is one of the most common causes of "mic works in browser but not in Teams desktop" reports.

After Teams reinstallation, microphone still missing

Reinstalling the Teams application does not clear its device configuration cache on Windows, which means if Teams stored a device selection that is no longer valid, reinstallation preserves that stale selection and the microphone problem persists even after a fresh install. After reinstalling, open Teams Settings and verify the microphone device selection explicitly rather than assuming reinstallation resolved the device issue, because the cached device ID from the previous installation may still be pointing to a disconnected or renamed audio device.

Teams stores its device preferences in a local cache that persists across reinstallations³. On Windows, navigate to %AppData%\Microsoft\Teams and delete the contents of the Settings folder. This forces Teams to rediscover all available audio devices on the next launch and present them fresh in the device selection dropdown. Always run the Noise Floor Grade before and after this reset to confirm the hardware is accessible to browser applications: if this tool can access the microphone before the reset, the hardware itself is not the problem. After the cache reset, verify the microphone appears correctly in Teams Settings before testing the audio in an actual call.

A cache reset is faster and less disruptive than a full reinstall because it preserves your Teams login, chat history, and workspace configuration while only clearing the device selection state that may be causing the microphone problem. Try the cache reset first; if Teams still cannot access the microphone after the reset, then proceed to a full reinstall as a last resort. This two-step approach saves the 10 to 15 minutes that a full reinstall and re-login requires while resolving the majority of cached device selection issues.

Preventing Teams audio failures after Windows updates

Windows updates often reset audio enhancement settings and can change the default communications device selection⁴. After a Windows update, rerun the Noise Floor Grade to confirm the microphone is still accessible, then open Teams Settings and verify the device selection matches your intended microphone. This two-step check takes under two minutes and prevents the common situation of joining a call and discovering Teams reverted to the laptop's built-in microphone because the update changed the OS default communications device.

Per-location device configuration in Teams

Teams Personal does not remember separate device selections for different physical locations, so if you move between a home desk with a USB microphone and a conference room with a different audio device, Teams may revert to the OS default each time. Configure the OS default communications device to match your current location's preferred microphone before opening Teams, and verify with the Noise Floor Grade that the correct device is active before joining any meeting.

Creating a Windows audio configuration checklist for Teams

Document your working audio configuration by noting the exact device names and gain levels when everything is working correctly. After a Windows update changes your audio behavior, comparing the current settings against this checklist takes under a minute and immediately reveals which setting the update modified. This proactive documentation approach is faster than troubleshooting from scratch every time an update silently changes a default device, yet reconfirm the Teams mic after a Windows update before trusting the cached selection.

When to use this

Use this test when Teams shows "Microphone not working" or when participants in a Teams call report they cannot hear you, before adjusting any Teams settings or reinstalling software.

Examples

Noise Floor Grade works fine in browser — hardware is OK; Teams reset to wrong default device by Windows update

Changed Teams device settings to correct USB microphone — immediately resolved

Noise Floor Grade: Excellent in Chrome. Teams web blocked by browser permission not granted for teams.microsoft.com

Granted microphone permission via Chrome padlock for teams.microsoft.com — fixed