Teams Voice Isolation Greyed Out? Noise Suppression Fixes

QC By the Call Tonic Team Published: July 28, 2026

Voice isolation greyed out? Teams needs a voice profile first: go to Settings and more (…) → Settings → Recognition → Start voice capture and read the passage aloud, which takes about 30 seconds, then restart Teams. No Recognition tab at all means your IT admin has switched voice enrolment or voice isolation off.

A locked or missing noise-suppression control in Teams comes down to five causes, in rough order of likelihood: you're on the web client (no setting — use the desktop app), your admin policy has pinned it, the app is outdated, you're sharing system audio or music mode is active (suppression is bypassed while it is), or the hardware doesn't support the higher setting. Work the list below top to bottom. A sixth is the mode: new Teams splits noise suppression into Background noise only and Voice isolation, and only voice isolation removes other people's voices.

Menu paths checked against Microsoft's official Teams documentation (new Teams client, Windows & Mac).

1. Check you're in the desktop app, not the browser

The single most common cause — Teams in a browser tab simply doesn't offer the control:

Look at your window: a browser address bar means web Teams.
Install or open the Teams desktop app and sign in.
Recheck Settings and more (…) → Settings → Devices.

Why this works: the browser can't do the deep audio processing the desktop client ships with, so the setting isn't hidden — it genuinely doesn't exist there.

2. Update the Teams client

Audio options have moved and changed names across versions; an old build can be missing controls newer docs describe:

Click Settings and more (…) → Settings → About Teams (or the update banner if one is showing).
Let any pending update install, then fully quit and reopen Teams.
Recheck the Devices settings.

Why this works: Teams rolls features out gradually by build; a client months behind can lack the toggle entirely or show it disabled. Updating also clears the odd corrupted-settings state.

3. Ask whether an admin policy has it pinned

In workplaces, audio processing can be set organisation-wide:

If the toggle is visible but locked, or switches back after you change it, that's the signature of policy control.
Contact IT and ask specifically whether noise suppression is enforced for your account.
For a personal workaround in the meantime, join important calls from a personal account where you control settings.

Why this works: call-quality policies are commonly standardised in orgs with call centres or compliance recording, and no client-side fiddling overrides them — asking is genuinely the fastest route.

Settings only go so far

For rooms the settings can't fix

Everything above tunes the filter you already have. When the noise itself is the problem — constant, loud, or unpredictable — Krisp works at the system level instead, cleaning your mic and your speakers across every app at once. There's a 7-day free trial without a card, so you can compare it against these settings in your own room.

Try Krisp for a week Read our full Krisp overview →

4. Check for music mode or system-audio sharing

Two situational states temporarily take suppression out of the loop:

If you're sharing your screen with computer sound included, finish sharing and recheck.
If high-fidelity music mode is active for the call, ordinary suppression is deliberately bypassed — turn music mode off.

Why this works: both features exist to pass sound through untouched — suppression would defeat their purpose, so Teams sidelines it while they're active. It comes back when they end.

5. Accept the hardware ceiling (and route around it)

The strongest suppression level has CPU requirements, and some machines — notably certain ARM devices and older processors — don't qualify:

If only the highest setting is unavailable, use the level Teams does offer.
Compensate physically: a closer mic and a quieter corner recover more than one settings notch.
On a machine that can't run in-app suppression at all, a lightweight external tool is the practical alternative.

Why this works: the aggressive filter is a real-time ML model; Microsoft gates it to hardware that can run it without wrecking the call. That's a floor you can't toggle past — but it's exactly the case the box below covers.

6. Voice isolation greyed out, or suppression on but not working? Check the mode

On new Teams the toggle under Settings → Devices → Noise suppression has two modes behind it, and the difference explains most "it's on but I can still hear typing" reports:

Background noise only removes fans, keyboards and hum but deliberately lets other voices through.
Voice isolation keeps only your voice. Microsoft asks for a voice profile first (its audio-settings page waives that when you're on a headset): … → Settings → Recognition → Start voice capture, about 30 seconds of reading aloud. Without one, expect the option to stay locked.
No Recognition tab at all? That is an admin policy switch (voice enrollment or voice isolation disabled for your account), not a fault. Admins control it with the VoiceIsolation setting in the Teams meeting policy and EnrollVoice in the Teams AI policy; both are on by default, so ask IT whether yours were turned off.
Profile recorded, still locked or failing? Restart Teams, which is Microsoft's own fix when voice isolation won't turn on. If your machine is busy, close other apps, then switch voice isolation off and on again.

Why this works: Microsoft's own guidance is to add a voice profile to start using voice isolation; the stronger mode cannot run without a reference for your voice, so Teams greys it out rather than guessing.

Still not fixed?

Toggle on but noise still loud? The setting isn't the problem — see our tuning guide and check mic placement.
Fresh install, still missing? Sign out, sign back in — entitlements load per-account, and a stale sign-in can hide features.
Only broken in one meeting? The organiser's meeting options can restrict attendee audio processing; try a test call on your own account.

Frequently asked questions

Why does new Teams not show Auto, High and Low?

New Teams replaced the classic Auto/Low/High/Off levels with a single toggle and two modes, Background noise only and Voice isolation. The old levels remain only in classic Teams and in the Teams iOS app.

Is noise suppression available in Teams on the web?

No — the browser version doesn't include the noise-suppression setting. Use the Windows or Mac desktop app to get the control.

Why is Teams noise suppression not working even though it's on?

Usually the mode. Background noise only ignores other voices by design; switch to Voice isolation once you have a voice profile. If that is already set, check which microphone Teams is listening to — a laptop array behind a closed lid defeats any filter — and test another headset.

Can I force high suppression on unsupported hardware?

No — the requirement is real-time processing capacity, not a licensing switch. If your machine doesn't qualify, use the available level plus better mic placement, or system-level software that carries its own lighter-weight processing.

Why is voice isolation greyed out in Teams?

Almost always because there is no voice profile yet. Record one under Settings and more (…) → Settings → Recognition → Start voice capture (about 30 seconds of reading aloud), then restart Teams. If there is no Recognition tab, or the option stays locked after you have a profile, your admin has turned voice enrolment or voice isolation off in policy, and only IT can change that.