MutePoint
Menu
Home / Fix-it / Voice isolation greyed out

Teams Voice Isolation Greyed Out? The Six Causes, in Order

By the MutePoint admin desk · Published

If Voice isolation is greyed out (grayed out, in US spelling) in Teams, the usual reason is that Teams has no voice profile for you yet: the option only becomes available after a 30-second recording under Settings → Recognition. If Recognition is missing altogether, an admin policy has switched enrollment off. Behind those two sit four more causes for a locked or missing noise-suppression toggle: the web client (the control is not there), an outdated build, music mode or system-audio sharing bypassing the filter, and a hardware ceiling. Work them in that order.

New Teams client, Windows & Mac — menu paths and policy names checked against Microsoft's voice isolation and noise suppression documentation.
Who holds the switch

Six causes, in the order to check them

Each cause from the short answer above, with whose move the fix is.

  1. no voice profilea 30-second recording under Settings → RecognitionYours to fix
  2. admin policydisabled voice isolation or enrollmentIT's call
  3. web clientthe control is not thereYours to fix
  4. outdated build… → Settings → About TeamsYours to fix
  5. music mode or system-audio sharingbypassing the filterTemporary
  6. hardware ceilingcan't support voice isolationHardware

What "voice isolation" is, and why the toggle has two modes

New Teams folds its noise handling into one switch. Settings → Devices → Noise suppression turns the filter on; once it is on you choose between two modes. Background noise only strips fans, keyboards and air conditioning while leaving other voices alone. Voice isolation goes further: it keeps a profile of your voice on the device and removes every sound in the call that does not match it, including the person talking behind you. During a meeting the same choice sits under More actions → Audio settings, or the arrow next to Mic.

That profile is the whole story of the greyed-out option. Voice isolation cannot run without one, so Teams locks the mode until it exists. Noise suppression itself may still be on and working in its milder mode, which is why people report "noise suppression not working" when what they are hearing is the difference between the two modes. Classic Teams never had this split; it offered Auto, High, Low and Off, and a colleague still on classic will see different controls for the same engine.

1. Record a voice profile

  1. Open … → Settings → Recognition.
  2. Under Voice, select Create (or Update), pick the microphone you normally use, then Start voice capture and read the passage aloud. Select End voice capture when you finish; the whole thing takes about 30 seconds.
  3. Took the opt-in route instead of reading the passage? That is express enrollment: Teams builds the profile during your next eligible meeting, not on the spot, so the option stays greyed out until that meeting has happened. Read the passage manually if you need it today.
  4. Back in Settings → Devices, the Voice isolation option is now selectable. Pick it.
  5. Profile saved and the option still won't light up? Quit Teams completely and reopen it; Microsoft's own in-call alert for this state is "Restart Teams to reload voice isolation". If it stays locked, delete the profile on the Recognition tab and record it again in a quiet spot, with the mic you actually use.
Why this works: the profile is the reference the model matches against; Microsoft's own instructions say to add a voice profile to start using voice isolation, and the option is locked until that reference exists. You can delete the profile at any time from the same tab.

2. If Recognition is missing: ask IT for two policy names

  1. No Recognition tab, or a notice that your admin has not turned this on = policy, not a bug.
  2. Ask whether voice isolation is disabled in your Teams meeting policy (the VoiceIsolation setting), or whether voice enrollment is disabled in the Teams AI policy (EnrollVoice, and PassiveVoiceEnrollment for express enrollment).
  3. Microsoft documents all three as enabled by default, so if yours are off someone chose that; request the change ticket or move on to the workaround below.
  4. Want to hand IT the exact fix? In Teams PowerShell it is Set-CsTeamsMeetingPolicy -Identity <policy name> -VoiceIsolation Enabled, plus Set-CsTeamsAIPolicy -Identity <policy name> -EnrollVoice Enabled (and -PassiveVoiceEnrollment Enabled for express enrollment).
Why this works: enrollment and voice isolation are separate switches living in two different policies, so one can be on while the other is off. Older tenants can also carry the meeting policy's legacy EnrollUserOverride setting, which Microsoft says the AI policy replaces; an admin thread on Microsoft's own Q&A from 2025 shows the AI policy on while that override still blocked enrollment. Naming the policies gets a precise answer instead of "we'll look into it".
When the tenant won't budge

Locked out by policy or hardware?

If IT has voice isolation or enrollment pinned off, escalate around it: Krisp filters at the device layer beneath Teams, where tenant policy has no reach, cleans both directions, and works in every call app on the machine. Seven full days free with no card; when they end, Krisp needs a paid plan, because the free tier is gone.

Start the 7-day evaluation Krisp for Teams users — the full picture →

3. Confirm you're in the desktop app

  1. Address bar visible? That's web Teams, and the noise-suppression control is genuinely not there.
  2. Install or open the desktop client, sign in, recheck Settings → Devices.
Why this works: Microsoft lists the feature for the desktop app, the iOS and Android apps, Teams Rooms on Windows and Azure Virtual Desktop. The browser is not on that list; the control is not hidden there, it is absent.

4. Update, then re-check

  1. … → Settings → About Teams (or the update banner) — let it finish.
  2. Fully quit and relaunch; a minimised Teams is still the old build.
  3. Re-open Devices.
Why this works: the Recognition tab and the two-mode toggle arrived in recent new Teams builds; a client that has not updated for months can predate them entirely, and Microsoft's own voice-profile troubleshooting starts with restarting Teams and checking for updates.

5. Rule out the temporary bypasses

  1. Sharing your screen with computer sound? Suppression steps aside until you stop sharing.
  2. High-fidelity music mode on? Microsoft's instructions for it let you switch off noise suppression and echo cancellation so music reaches participants unprocessed; check whether that was done, and turn music mode off for ordinary meetings.
  3. End both, recheck the toggle.
Why this works: both features exist to deliver unprocessed audio; the filter coming back the moment you stop confirms a bypass rather than a fault.

6. Accept the hardware ceiling, then route around it

  • Background noise only works, voice isolation won't take? Teams warns when your device is running too many apps and can't support voice isolation. Close other apps, then switch voice isolation off and on again; on a machine that stays too busy, use the mode you have plus better mic placement, or filter beneath Teams as above.
  • Fresh machine, missing everywhere? Sign out and back in; entitlements occasionally load stale.
  • One meeting only? The organiser's meeting options can restrict audio processing for attendees.

Teams noise suppression not working at all?

If the toggle is on, the mode is selectable, and colleagues still hear your keyboard, you are past the greyed-out problem and into a quality one. Three checks, in order: make sure Teams is listening to the microphone you think it is (a laptop array behind a closed lid will defeat any filter); confirm the mode is Voice isolation rather than Background noise only, since the milder mode is designed to let voices through; and test with a different headset, because a noise-cancelling headset or boom mic cleans much of the signal before Teams ever sees it. If all three pass and the noise remains, the page on a mic that is dead or too quiet covers the device side, and the Krisp for Teams write-up covers the software route that does not depend on the Teams filter at all.

Quick answers

Why is voice isolation greyed out in Teams?

Almost always because Teams has no voice profile for you. Voice isolation works by matching sound against a profile stored on your device, so until you record one under Settings → Recognition the option stays locked. If Recognition itself is missing, your admin has turned enrollment off.

Is voice isolation the same as noise suppression?

No. Noise suppression is the toggle; voice isolation is the stronger of its two modes. The other mode, Background noise only, removes fans and keyboards but lets other voices through. Voice isolation removes everything that is not your voice.

Can I force-enable it against tenant policy?

Not inside Teams — policy outranks the client. If IT has disabled voice isolation or enrollment, the only route is a filter at the device layer beneath Teams, which policy does not reach.

Why does my colleague's Teams show options mine doesn't?

Different policies or a different client. Voice isolation, enrollment and express enrollment are each a separate admin switch, and classic Teams exposed Auto/High/Low/Off where new Teams shows a toggle plus two modes.

Does voice isolation work in the browser?

No. The noise-suppression control is not in web Teams at all; it is in the desktop app, the mobile apps, Teams Rooms on Windows and Azure Virtual Desktop. Open the desktop client and look again.

I recorded a voice profile. Why is voice isolation still greyed out?

Three usual reasons. Teams has not reloaded the feature since you recorded, so quit it fully and reopen. You opted into express enrollment, which only builds the profile during your next eligible meeting. Or the recording was poor; delete it under Settings → Recognition and record again somewhere quiet. If none of that frees the option, a policy on your account is blocking it, and only IT can lift that.

Related fixes