When Teams noise suppression is not working, it is nearly always one of four things: your tenant policy has locked the control, your hardware or OS path does not support it, Teams is filtering an input you are not speaking into, or the room is past what any filter can do. Each has a check that confirms it in under a minute, and each ends somewhere different. Three you can fix at your desk this afternoon. One you cannot, and being told to restart Teams for the fifth time is not going to change that.
Cause one: policy has locked the control
This is the cause people spend longest refusing to accept. In a managed tenant, administrators can restrict the suppression control, and when they do it shows up greyed out, or the level you set quietly reverts the next time you open Settings. It is not a corrupt profile. Reinstalling the client will not bring it back. Clearing the cache will not either, although you will find plenty of forum threads insisting otherwise.
- The control is visibly greyed rather than absent. A restriction usually leaves the label sitting there.
- The same laptop behaves identically after a clean reinstall and a fresh sign-in.
- A colleague on the same tenant, using different hardware, sees the same greyed control.
- Your own personal account on that same machine behaves differently.
If those line up, stop troubleshooting. The honest answer is that the built-in toggle is not returning to your account, and the route that still works is changing what Teams listens to. Teams uses whatever input device you select, so a microphone that arrives already filtered sidesteps the locked setting completely. We keep a longer write-up at suppression greyed out, including what to send IT if you want to ask, and what to do in the meantime.
Cause two: the hardware or OS path
Suppression can also be unavailable because of hardware or operating system constraints rather than any policy. Some headsets and conference devices run their own processing and take that path out of Teams' hands. Unusual OS setups and older builds can remove the option as well. The symptom differs from the policy case: here the control tends to vanish, or to accept a change and then do nothing with it, rather than sitting greyed with an explanation attached.
How to confirm it
Unplug everything, restart Teams using only the built-in laptop microphone, and look at the pane again. If the control comes back, your device was the cause, and your options are a firmware update from the manufacturer or accepting that the headset does the filtering instead. If nothing changes across two different machines on the same OS build, you are back in policy territory. Our audio settings map is worth a pass here, because a device that hides one control often hides others alongside it.
Causes three and four: wrong input, hopeless room
Cause three is the most common and the least dramatic. Teams is filtering perfectly well, just not the microphone you are talking into. A docked laptop, a headset, a webcam with its own mic and a monitor with speakers can present four inputs between them, and Teams will happily settle on the webcam. Open the Devices pane, look at the microphone dropdown, and speak: the level should move on the device you expect. If it moves somewhere else, you have your answer already.
Work through it in this order. Select the right input. Set the level to Auto rather than High, so you are testing the filter and not the processor. Make a test call and judge the playback instead of the meter, and our walkthrough on how to turn on noise suppression has the exact click path. If your voice arrives thin or breaks apart, see robotic or choppy voice. If the room is still audible, check whether it is really noise at all, because a delayed copy of yourself is echo in calls and no setting touches that. Cause four is the honest one: no filter removes the conversation happening beside you, and a hard room beats every level.
Edge cases worth knowing
It keeps turning itself off
A level that resets between calls points back at policy, or at a second install. The classic version is a personal account and a work account on one machine, each carrying its own settings. Check which account the window in front of you belongs to before deciding the feature is broken.
It works for you but not for them
Filtering is applied on the sending side. If a colleague's background is pouring into the call, nothing in your settings changes it, because the filter has to run on their machine. Ask them to check their own level, and until they do, reach for a mute key rather than an argument. Our notes on mute etiquette and shortcuts cover the ones worth memorizing.
You want the same thing on a phone
Krisp's live noise cancellation is desktop only, meaning Windows 10 or 11 and macOS, verified August 2026. Its mobile apps handle transcription and meeting notes rather than live filtering. On a phone, a headset with a boom mic remains the most reliable answer. Our Krisp for Teams page sets out what runs where.
Common questions
Why is my Teams noise suppression greyed out?
Usually tenant policy. Administrators can restrict the control, and a restricted control appears greyed rather than missing. Hardware and OS constraints produce a similar result. Confirm it by testing a personal account on the same laptop: if that account shows a working control, the machine is fine and the restriction sits on your work account.
Should Teams noise suppression be on or off while troubleshooting?
Set it to Auto and leave it there while you test everything else. Off removes a variable but also removes the thing you are trying to evaluate, and High adds processor load that can imitate a completely different fault. Auto gives you a stable baseline, so any change you notice afterwards came from the device rather than the level.
Will reinstalling Teams bring the option back?
Not when policy is the cause, which is most of the time. A reinstall replaces the client, and the restriction lives with your account and tenant instead. It is worth ten minutes only if a colleague on the same tenant and similar hardware sees a working control, since that points at something local to your install.
Why can I hear the noise but the other side cannot?
Because you are hearing the room with your ears, not through the microphone. Filtering happens on the outgoing signal, so your own experience of the fan or the traffic never changes. Record a test call and listen back. That playback is the only accurate measure of what your colleagues actually receive.
What can I use when the built-in filter is unavailable?
A virtual microphone you install yourself. Krisp adds one on Windows 10 or 11 and macOS, and you select Krisp Microphone as the input in the app audio settings, with processing kept on your device. Free covers 60 minutes a day with no card. Core is $8 a month billed annually, or $16 month to month, verified August 2026.