Platform policy · Zoom
Zoom admin audio settings: governing sound from the portal down
Zoom's governance philosophy differs from Microsoft's in a way admins should exploit: alongside the web portal's setting locks, Zoom publishes a full policy catalog for its desktop client — registry keys you can push with the installer, GPO or MDM. That catalog includes the thing Teams famously won't give you: a way to set the background-noise-suppression level administratively.
Two control planes, one mental model
Plane 1: the web portal
Admin → Account Management → Account Settings, with group-level overrides under User Management's groups. Portal settings govern meeting features, and the lock icon is the enforcement primitive: locked at account or group level, a setting stops being a user preference and starts being policy. Zoom's setting inventory moves around; the lock mechanism is the durable part.
Plane 2: client policy keys
Zoom's mass-deployment kit for Windows documents policy keys applied at install time (MSI switches) or afterwards (registry via GPO/MDM). This is where client-side behavior — including audio processing defaults — becomes something you ship rather than something you request. macOS has an equivalent managed-preferences story via MDM configuration profiles.
The key you came for
From Zoom's mass-deployment documentation, verified 20 September 2026:
| Policy key | Values | Default | What it governs |
|---|---|---|---|
SetSuppressBackgroundNoiseLevel | 0 = Auto · 1 = Low · 2 = Medium · 3 = High | 0 (Auto) | The desktop client's background-noise-suppression level — the same four levels the client exposes, set administratively. |
Registry locations for MSI-deployed configuration, per the same doc: HKEY_LOCAL_MACHINE\SOFTWARE\ZoomUMX (64-bit) and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\ZoomUMX (32-bit). Delivery options, in rough order of how often we'd choose them:
- At install time, as configuration options on the MSI command line in your packaging pipeline;
- Post-install via GPO or Intune, writing the value under the policy path (
HKLM\SOFTWARE\Policies\Zoom\Zoom Meetings\General), not the install-time path above — the right move for fleets where Zoom is already installed (mechanics on our GPO and Intune pages); - Via MDM profile on macOS, using Zoom's managed-preference equivalents (see macOS MDM).
Choosing the value like an engineer
- 0 (Auto) — Zoom decides per situation. The honest default for a general fleet: it's what Zoom ships, and it rarely embarrasses you.
- 2 (Medium) or 3 (High) — worth pinning for populations whose environments are reliably hostile: home-office roles, open floors. High is aggressive; it can color voices at the margins, which is precisely the kind of trade-off you validate in ring 1 instead of discovering in an executive briefing.
- 1 (Low) — the special-case value for the rare desktop population that needs faithful audio (say, a music-lesson vertical); pair it with the original-sound policy key rather than fighting the suppressor.
SetSuppressBackgroundNoiseLevel, value by value
- 0AutoZoom’s default. The honest choice for a general fleet.Default
- 1LowThe special case: faithful audio, paired with original sound.
- 2MediumFor reliably hostile rooms: home offices, open floors.
- 3HighAggressive; can colour voices. Validate it in ring 1.
The neighboring keys worth setting in the same package
Since you're already shipping policy, four adjacent keys from the same catalog earn their place in a standard audio baseline:
| Key | What it does | Our take |
|---|---|---|
AudioAutoAdjust | Enables automatic microphone-volume adjustment | On for general fleets; kills the too-quiet-mic ticket class. |
AutoJoinVOIP | Auto-connects computer audio on join | On. Removes the “you're not connected to audio” minute from every meeting. |
MuteVoipWhenJoin | Joins meetings muted | On. The kindest default in this table. |
EnableOriginalSound | Enables the original-sound (musician) audio profile | Off unless a population specifically needs unprocessed audio. |
Where Zoom's levers stop
- Zoom-only scope. The policy key governs Zoom. The softphone, the recorder, the browser-based interview tool — all untouched. The moment that list matters, you're in deployed-layer territory.
- Keys drift between releases. Zoom's policy catalog is versioned with the client. Re-verify key names against the current mass-deployment doc during change planning — this page carries its verification date for exactly that reason.
- Registry state isn't user education. Pinning High on a population that then hears “robotic” colleagues will generate its own tickets. Pilot the value; don't decree it.
- The portal/client split is real. Some things you'll want live portal-side with a lock, some live client-side as keys, and the two don't cross-reference each other. Keep your Zoom audio baseline in one written doc that names both planes.
No affiliate relationship exists between this site and Zoom. This page exists because the free, documented policy surface is the correct first move for any Zoom fleet.
One key per app, or one layer for all of them
If your audio baseline document is growing a per-application section for every tool your company talks through, that's the signal to price the alternative: one OS-level suppression layer, deployed once, covering everything — with Zoom's own processing dialed down by the keys above so the two don't double-process. Krisp's 7-day trial (verified 20 September 2026) is the cheap way to A/B that architecture.
Referral link, declared: when an organization licenses Krisp after clicking this button, Krisp pays RolloutDesk a fee, and the quote you receive is the one you would get going direct. Zoom's policy keys are documented by Zoom and free regardless.
Related reading: the Teams equivalent (a stricter surface), shipping registry policy with Intune, and the full playbook these levers belong to.