Skip to the fix
CallTonic
Menu
Home / Teams / Mic not working

Teams Mic Not Working or Too Quiet: The Complete Fix List

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

Work top-down: first confirm the OS allows Teams to use the microphone (Windows: Settings → Privacy & security → Microphone; Mac: System Settings → Privacy & Security → Microphone), then pick the correct device under Teams Settings → Devices, then run Make a test call to hear yourself. Too quiet rather than silent? Raise the OS input level — Teams doesn't amplify a weak signal.

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

1. Grant the OS-level microphone permission

If the operating system is blocking Teams, nothing inside Teams can fix it — so rule this out first:

Windows

  1. Open Settings → Privacy & security → Microphone.
  2. Turn on Microphone access, Let apps access your microphone and Let desktop apps access your microphone, and make sure Microsoft Teams is switched on if it appears in the app list. Already on? Microsoft suggests turning them off and on again, then restarting.

Mac

  1. Open System Settings → Privacy & Security → Microphone.
  2. Enable the toggle next to Microsoft Teams, then quit and reopen Teams.
Why this works: both OSes gate mic access per app, and a denied prompt during installation silently sticks forever. This single check resolves a huge share of "Teams can't hear me" reports — especially on a new Mac.

2. Select the right microphone in Teams

Teams follows its Devices setting, not whatever you thought was plugged in:

  1. Open Settings and more (…) → Settings → Devices.
  2. Under Microphone, pick your actual device by name — avoid trusting a generic default after connecting new hardware.
  3. Speak and watch the level indicator respond; no movement means the wrong device or a hardware mute.
Why this works: every USB dongle, webcam and Bluetooth headset registers its own mic, and the most recently connected one often steals the default. Explicit selection ends the roulette.

3. Run a test call

The definitive check — you hear exactly what callers hear:

  1. In Settings → Devices, click Make a test call.
  2. Follow the prompt: speak a message after the tone.
  3. Listen to the playback — silence, low volume or crackle here mirrors precisely what the meeting gets.
Why this works: the test call exercises the whole live pipeline — capture, processing, network — rather than just showing a local meter. If playback is clean, remaining problems are on the meeting or the other side, not your mic.
If the noise persists

When Teams's filter isn't enough

Teams can only clean audio inside Teams. If your environment is genuinely loud — street noise, kids, a mechanical keyboard — a system-level tool like Krisp filters your microphone before any app hears it, in both directions, and its 7-day free trial (no card required) is enough to tell whether it beats your in-app settings.

Give Krisp a 7-day trial Read our full Krisp overview →

4. Fix "working but too quiet"

A whisper-level mic is an input-gain problem, not a Teams problem:

Windows

  1. Open Settings → System → Sound, choose your microphone under Input.
  2. Raise Input volume, speak, and watch the meter reach a healthy level.

Mac

  1. Open System Settings → Sound → Input, select the mic.
  2. Raise Input volume while watching the level bars as you speak.
Why this works: Teams takes the level the OS hands it. When it doesn't: boom mics rotated away from the mouth, foam windscreens stuffed with lint, and hardware volume wheels on the cable all masquerade as software problems — glance at the physical mic too.

5. Unblock the device from other apps

A mic can be captured — exclusively — by whoever grabbed it first:

  1. Close other conferencing and recording apps (Zoom, OBS, voice recorders) before joining.
  2. Toggle Bluetooth headsets off and on if audio routes but the mic doesn't — the hands-free profile sometimes fails to engage.
  3. Restart Teams after any driver update; it enumerates devices at launch.
Why this works: exclusive capture and half-connected Bluetooth profiles both produce the same symptom — a device that looks present but delivers silence. Releasing and re-acquiring it resets the chain.

Using Teams in a browser? Allow the mic for the site

Teams on the web needs the browser's permission as well as the operating system's, and the test call isn't available there:

  • Edge: Settings → Cookies and site permissions → Microphone, and turn on Ask before accessing.
  • Chrome: Settings → Privacy and security → Site settings → Microphone. Pick the right device and let sites ask to use your microphone.
  • Safari: Settings → Websites → Microphone, and set it to Ask or Allow.

Still not fixed?

  • Works in test call, silent in meetings? Check you're not muted by the organiser's lobby settings, and that a hard-mute button on the headset isn't engaged.
  • Mic dies mid-call daily? Suspect aggressive laptop power management turning off USB audio — disable USB selective suspend (Windows power options).
  • Mic missing from every list on Windows? Open Sound settings → More sound settings → Recording, right-click the mic and choose Enable.
  • Need to talk right now? If Teams offers Call me back in the meeting's audio options, enter your number: the audio runs through your phone while screen sharing stays on the computer.
  • Nothing works in Teams but everything works elsewhere? Clear the Teams cache or reinstall — settings corruption is rare but real.

Frequently asked questions

Why does my mic work in Zoom but not in Teams?

Almost always separate permissions or a different selected device. Each app has its own OS permission entry and its own device picker — check the Mac/Windows microphone privacy list for Teams specifically, then Teams' Settings → Devices.

Where is the test call in the new Teams?

Under Settings and more (…) → Settings → Devices → Make a test call. It isn't offered in Teams on the web. Availability can also depend on your organisation's calling setup — if it's absent, a quick meeting with yourself works as a substitute.

Related Teams fixes