A Teams microphone not working on a company laptop is far more often blocked than broken. Three things do the blocking: the operating system's privacy permission, a policy applied to the client by your tenant, and a device choice made by something other than you, such as a dock, a headset that reconnected in your bag, or the gap between the new Teams client and the classic one. Genuinely dead hardware exists, but it is the last suspect rather than the first. The three checks below sort you into the right category without an admin ticket. Our shorter page on a mic not working or too quiet covers the fast path; this is the version for a machine you do not fully control.
Blocked, broken, or simply pointed elsewhere
Broken means no software on the machine can hear you. Blocked means one layer refuses to pass a signal that exists. The difference takes about forty seconds to establish, and it decides whether you spend the afternoon on a ticket or on a dropdown. Open the sound settings your operating system provides, outside Teams entirely, and watch the input level while you speak. A moving level there and silence in Teams is a blocked mic, every time. Nothing moving anywhere, on any input, is the only result that justifies suspecting the hardware.
- Level moves in the OS, not in Teams: permission, policy, or the wrong device.
- Level moves in Teams, colleagues hear nothing: the call path, not the mic.
- No level anywhere, and a second headset behaves the same: hardware or the port.
- Everything works after a reboot, then fails again: a dock or a driver, not Teams.
That second line catches more people than it should. Teams can show a perfectly healthy level in its own device settings while the far end hears silence, because the level meter reads the input and the call uses whatever device was selected when the call began. Change a device mid-call and Teams does not always follow. On a managed laptop there is a third possibility layered on top: the setting exists, you can see it, and it is greyed out because your tenant decided so. That is not a fault, and no amount of reinstalling will move it.
Policy, permission, and two clients that disagree
On a personal machine you own every layer, so a Teams microphone not working is yours alone to fix. On a work device you own perhaps two of them, so it pays to know which are yours before you start changing things.
When the control is greyed out
A control your administrator has set is displayed but not editable, and it looks identical to a bug. Noise suppression is the usual example: the menu is there, the option is fixed, and the tooltip rarely explains why. The honest response is to stop clicking and work around the layer instead of through it, because the setting will reappear locked at the next policy refresh anyway.
New Teams and classic Teams keep separate device choices
The two clients store their own audio preferences. Switch between them, or get switched by an update, and the microphone selected yesterday is not the one selected today. Check the device dropdown in whichever client is actually open, by name, not by trusting the default. Get through this section and you may be perfectly audible and still hard to listen to, because your open-plan floor comes through with you.
The three checks, in order
Most reports of a Teams microphone not working end at check one or two. First, the operating system: on Windows 11 open the privacy settings, find the microphone section, and confirm both the device-wide toggle and the per-app entry for Teams; on a Mac, open the privacy section of system settings, tick Teams under Microphone, then quit and relaunch the app so the grant takes effect. Second, the device itself, chosen by name in the client. Our audio settings map shows where each control lives in both clients, and the guide to turning on noise suppression is worth a look while you are in there.
- Unplug the dock, test on the laptop's own port, plug it back in.
- Test in a call with yourself before you test in a meeting with your director.
- Note the exact wording of any error; it names the layer that refused.
- Reboot once before you raise a ticket, and say that you did.
Third, the policy layer. If the control you need is fixed, that is your answer and the fix belongs to your administrator, not to you. Our page on suppression greyed out explains what is happening and what to ask for. If the mic works but people describe you as underwater or cutting in and out, the cause is bandwidth or processing rather than permission, and robotic choppy voice is the closer match. There is also a known pattern where the setting looks correct and behaves otherwise, covered in Teams noise suppression not working.
Managed-laptop edge cases
The dock takes the microphone with it
A docking station presents its own audio devices, and Windows will happily route the mic through a port with nothing plugged into it. The tell is timing: it works at home and fails at the desk, or the other way round. Select the input by name in each location, and expect to do it twice, once per profile.
A headset connects to the phone in your bag
Wireless headsets remember several devices and will pair with whichever one wakes first. Your laptop sees a connected headset, the headset is listening to a phone in a bag, and the meeting hears nothing. Turn Bluetooth off on the phone before the call, or connect the headset by hand each morning.
A virtual meeting room grabs the input
Recording tools, note takers and room systems can install their own audio devices, which then appear in your dropdown with unfamiliar names. If a device you never bought is selected, that is why. Choose your physical headset explicitly, and check again after any managed software update.
Common questions from managed devices
Why is my Teams microphone not working on Windows 11?
Check the operating system before the app. Windows 11 has a device-wide microphone toggle and a per-app list under it, and Teams needs its own entry enabled. Updates and policy refreshes can reset that entry while the device toggle stays on, which produces a mic that works everywhere except the one app you need.
How do I test my Teams microphone properly?
Use the built-in test call for presence, then a real call for quality. The test call proves the signal reaches the service and comes back. It cannot tell you whether your level is too low for a room of fifteen. Ask a colleague for thirty seconds before your next meeting; you will learn more.
My microphone works in other apps but not in Teams. Why?
That result rules out hardware and points at three layers: the per-app permission, the device selected inside the client, or a tenant policy. Work through them in that order. Reinstalling addresses none of the three and costs you twenty minutes, so leave it until everything else has been eliminated.
Why is the noise suppression option greyed out for me?
Because your administrator set it centrally. Policy-managed controls appear in the interface but cannot be changed locally, and they reset at the next refresh even if a workaround briefly moves them. Ask your IT team which policy applies rather than trying to override it; that is the only route that lasts.
Do I need admin rights to fix a Teams microphone?
For the common causes, no. Privacy permission and device selection are user-level settings on most corporate builds. You need your administrator only for controls the tenant has locked, and for driver installs that the machine refuses. Establish which category you are in first, so the ticket you raise is the specific one.