Teams microphone not working is a layered problem — there are multiple systems between your mouth and the person hearing you, and any one of them can fail. Rather than trying everything randomly, the two-minute diagnostic identifies which layer has the problem. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
Teams has a built-in microphone test: click your profile picture → Settings → Devices → find the Microphone section → “Make a test call” or look for the microphone level bar. Speak — does the bar move? If yes: your microphone works, and the issue is specific meeting configuration (the meeting host muted you, or the wrong mic is selected). If the bar doesn’t move: keep reading.
Windows microphone permissions — always check this
Settings → Privacy and security → Microphone. Three things need to be On:
- Camera access at the top (confusingly, this master switch covers the mic too on some builds)
- “Let apps access your microphone”
- “Let desktop apps access your microphone” — Teams is a desktop app, and this toggle specifically covers it
The third one, further down the page, is what people miss. Scroll past the first two and confirm it’s enabled. After turning it on, restart Teams and test again — the permission change doesn’t apply to an already-running app.
Select the microphone explicitly in Teams
Settings → Devices → Microphone → click the dropdown and explicitly choose the correct device by name. “Default” is unreliable — when new audio hardware connects (headset plugged in, Bluetooth connected), Windows changes its default without Teams updating to match. The dropdown shows all available microphones; picking the one you want eliminates the ambiguity.
Watch the level bar change when you speak after selecting each device. If the bar moves for one device but not another, that immediately confirms which physical microphone is working.
Exclusive control — another app has the microphone
Windows allows only one application to access the microphone at a time in Exclusive Control mode. If Zoom, Discord, or another communication app has the microphone locked, Teams shows it as available in its device list but can’t actually access it.
Close every other communication app. Check the system tray for any running audio apps. After closing them all, restart Teams and test. If the microphone works immediately after closing the other apps: one of them was holding exclusive control. In the future, open Teams first before other communication apps to ensure it gets primary access.
Also: right-click the speaker icon → Sound settings → More sound settings → Recording tab → right-click your microphone → Properties → Advanced tab → uncheck “Allow applications to take exclusive control of this device.” This prevents any app from locking out others.
In-meeting controls
Three things to verify during a meeting that are not settings but are frequently the actual cause:
- The microphone icon in the meeting controls — is there a slash through it? Click it to unmute.
- Was you muted by the host? Only the host can unmute you if they used a “mute all” command. Raise your hand in the meeting if you can’t unmute.
- The meeting’s own mute state vs the Teams app mute state — they can differ. The meeting controls (in the call bar) are what matters during a call, not the device settings.
Noise suppression over-suppressing
Teams Krisp noise suppression is aggressive. On some microphones — particularly those that capture a lot of room noise or have a narrower frequency response — Krisp interprets parts of the voice signal as noise and filters them. The result: voice sounds thin, cuts in and out, or disappears entirely for certain people’s voices or speaking styles.
Settings → Devices → Noise suppression → change from “High” to “Low” or “Off” and test. Also check: “Echo cancellation” — disabling it occasionally improves microphone clarity in specific hardware configurations where echo cancellation interferes with the signal.
Driver update
Windows updates frequently replace working audio drivers with generic versions. The generic driver often works for basic audio but may not correctly handle microphone array configuration — the algorithm that combines multiple microphone capsules on a laptop array for noise reduction and directionality.
Download the audio driver from the laptop manufacturer’s support page for the specific model. Not from Windows Update. After installing the manufacturer driver and restarting, test the microphone in Teams. The manufacturer driver typically includes the correct microphone array processing for that laptop’s hardware.
New Teams cache and reset
For persistent microphone issues that survive settings changes: Settings → Apps → Microsoft Teams → Advanced options → Reset. This clears Teams’ cached device configuration and forces it to re-enumerate audio devices on next launch. After the reset, reopen Teams and re-select the microphone in Settings → Devices.
For New Teams (version 2.x): the cache is stored at %localappdata%PackagesMSTeams_8wekyb3d8bbweLocalCacheMicrosoftMSTeams. Quit Teams → delete the Cache folder → reopen → reconfigure devices.
Related audio permission issues covering camera alongside microphone are in our Teams camera guide — the Windows privacy settings for camera and microphone sit in the same settings page and often need to be fixed together. For the audio driver layer that affects microphone quality across all applications (not just Teams), our audio troubleshooting guide covers the Realtek and manufacturer driver reinstallation. Microsoft’s Teams microphone documentation covers the audio quality diagnostic tool accessible via the /debug command and the real-time call statistics that show microphone signal strength during active calls.
Microphone works in test call but not in meetings
If the test call confirms the microphone works but participants still can’t hear you in a meeting: the issue is either the meeting’s mute state, a connection quality problem, or a Teams routing anomaly. Check: join a different Teams meeting or start a new meeting by yourself and confirm you can hear your own voice through the echo. If that works, the original meeting had a specific issue rather than a persistent microphone problem.
Also check the meeting’s audio settings during the call: three-dot menu in the meeting → Device settings → confirm the microphone shown is the correct one. Teams sometimes switches devices mid-meeting when a new audio device connects — headphones being plugged in, Bluetooth connecting — and the meeting’s device selection doesn’t update automatically the way the pre-meeting settings do.
Background app permissions and microphone access
Settings → Privacy and security → Microphone → scroll down past the device-level toggles to the app list. Each app that has requested microphone access shows here with its own toggle. “Microsoft Teams” should appear with its toggle On. If it’s Off even when the main toggles are enabled: this per-app restriction is blocking access despite the system-level permissions being correct.
This per-app restriction is the most granular level of Windows microphone control and is where the “it says it’s allowed but it doesn’t work” situations often end. Toggle it Off → wait 5 seconds → toggle it On → restart Teams. The toggle cycle forces Windows to refresh the permission grant to the application.
Headset vs built-in microphone — which one Teams is using
Plugging in a headset changes the available microphone options. Teams may switch to the headset microphone automatically — or it may stay on the built-in mic while the headset earphones handle audio output. This creates the situation where you hear participants clearly but they can’t hear you (or hear you very faintly from the built-in mic rather than clearly from the headset mic).
Settings → Devices → Microphone → check which is selected. If it says “Integrated Microphone” or “Array Microphone” while a headset is connected: manually switch to the headset’s microphone (usually labeled with the headset manufacturer’s name or “Headset Microphone”). After switching, test by speaking — the level bar should respond immediately if the correct microphone is now selected.
Corporate MDM policies restricting microphone
On Intune-managed corporate devices, IT can configure policies that restrict microphone access to specific applications or disable it entirely for devices that don’t meet compliance requirements. If microphone access is policy-controlled, the Windows privacy settings may show “Managed by your organisation” and the toggles are greyed out.
Check: navigate to a Settings page that shows the microphone toggle. If it’s greyed out with a lock icon or “managed by organisation” text: IT controls this. Contact IT to request microphone access for Teams — they can create policy exceptions for specific applications or user groups through the MDM console.
Audio drivers and the Microsoft Audio driver conflict
Windows includes its own Microsoft audio driver (the High Definition Audio codec driver). Some updates install this in place of manufacturer-specific Realtek, Conexant, or IDT drivers. The Microsoft driver lacks the microphone array processing configuration that manufacturer drivers include, so while basic audio works, the microphone captures excessive background noise or has very low volume.
Device Manager → Sound, video and game controllers → look at the driver listed for the audio device. If it says “Microsoft” rather than “Realtek,” “Conexant,” or the laptop manufacturer: the generic driver is installed. Go to the laptop manufacturer’s support page → search by model number → download the audio driver. Install it and restart. The Teams microphone should immediately behave differently (usually much better) with the manufacturer driver.
Teams web client as a microphone test
If the desktop Teams app consistently has microphone issues: test via the Teams web client. Open a browser → teams.microsoft.com → join a meeting or start a test call → the browser requests microphone permission separately from the Windows desktop app. If the microphone works in the browser version of Teams but not the desktop app: the desktop app’s audio configuration is the specific problem, and the app reset/reinstall approach is the right path. If it also fails in the browser: the issue is at the Windows driver or permission level rather than the Teams application itself.
Sample rate and bit depth mismatch
Teams expects specific audio formats from the microphone. When the microphone’s sample rate in Windows doesn’t match what Teams can work with, audio is either absent or distorted. Right-click the speaker icon → Sound settings → More sound settings → Recording tab → right-click your microphone → Properties → Advanced tab → Default Format. Try different settings — particularly 1 channel, 16 bit, 44100 Hz (CD quality), which is the most broadly compatible format. Some Teams issues with specific microphones resolve immediately when changing from 48000 Hz to 44100 Hz or vice versa.
After changing the format, Teams needs to be restarted before it detects the new format. Test immediately after restart — if the issue was a format mismatch, the microphone should work correctly now.
Recording device disabled in Sound settings
Sound settings → More sound settings → Recording tab — is your microphone listed? Is it the Default Device? Right-click an empty area in the Recording tab → Show Disabled Devices → confirm the microphone isn’t accidentally disabled. A disabled microphone appears greyed out in the list and produces no input to any application including Teams. Right-click → Enable to restore it to active status.
Also check: if the microphone is present and enabled but not set as Default: right-click → Set as Default Device. Teams uses the default recording device unless you’ve explicitly selected a different one in Teams settings. Both need to match for reliable microphone access.
One pattern worth calling out explicitly: microphone that worked yesterday and stopped today, with no software changes. This is usually the microphone permission having been silently revoked by a Windows update. Windows updates that touch the privacy settings occasionally reset per-app microphone permissions. The fix is quick — re-enable in Settings → Privacy and security → Microphone — but the cause being an update rather than anything the user did is worth knowing, because it recurs with major Windows feature updates and is worth checking again after each one.
The diagnostic priority for Teams microphone: (1) Teams built-in test call to confirm whether the mic is physically accessible. (2) Windows privacy settings — all three microphone toggles. (3) Teams device selection — pick the mic explicitly, not “Default.” (4) Close all other communication apps for exclusive control conflicts. (5) Meeting-specific mute state. These five steps resolve the vast majority of cases. The driver, noise suppression, format, and corporate policy issues are for the minority where the first five haven’t resolved it — they’re worth knowing but rarely needed. Related: Zoom Microphone Not Working.
And for the test-before-meeting approach: Teams → More menu (three dots) → Settings → Devices → “Make a test call” is an isolated session where you can record a message and play it back, confirming exactly what your microphone sounds like to other participants. This takes 60 seconds and gives you more information than any amount of settings checking — you hear exactly what others hear from your microphone, in the actual Teams audio pipeline. If the test call sounds clear, your microphone is working correctly regardless of any settings that might appear wrong. If this sounds familiar, Chrome Sync Not Working is worth a look.
