QuietCall
Home / Teams / Fix echo

How to Fix Echo in Microsoft Teams Calls

QC By the Call Tonic Team Published: July 28, 2026 Last updated: July 28, 2026
This article contains affiliate links — see our disclosure.

Echo in Teams means somebody's speakers are reaching a microphone — theirs, or a second device joined in the same room. Headphones for the person causing it (usually the one who doesn't hear the echo) end it instantly. Joining from a laptop and a phone together? Add the second device with audio off — the room-join prompt exists precisely to prevent this loop.

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

1. Trace the echo to its source

The culprit rarely hears their own echo — everyone else does. Narrow it down:

  1. Open the People panel during the echo.
  2. Watch whose mic indicator glows while someone else is speaking — that open mic is re-broadcasting the room.
  3. As organiser, mute participants one by one (hover → Mute participant) until it stops, then ask that person to use headphones.
Why this works: echo needs exactly one open junction — live speakers near a live mic. The indicator lights betray it because the mic is picking up meeting audio as if it were speech.

2. Join second devices without audio

Presenting from a phone while attending on a laptop is the classic self-inflicted echo:

  1. When Teams detects you're joining a meeting you're already in, choose the option to add the device without audio.
  2. Missed it? On the second device, mute the mic and set its speaker volume to zero.
  3. In shared rooms, agree that exactly one laptop carries the audio; everyone else joins muted with sound off.
Why this works: two live audio paths in one room feed each other in a loop the echo canceller can't fully unwind. One audio connection per physical room is the invariant that matters.
Still hearing it?

The system-level option

In-app suppression is one layer. The other is a virtual-microphone tool such as Krisp, which sits between your mic and your meeting apps and removes noise in both directions before the call ever hears it. A 7-day free trial (no card needed) makes it easy to check whether it solves what the settings above couldn't.

See how Krisp works Read our full Krisp overview →

3. Use headphones (and ask the same of the culprit)

The fix that requires no diagnosis:

  1. Plug in any wired or Bluetooth headphones — meeting audio now ends at your ears, not your mic.
  2. Politely request the same from whoever the People panel identified.
Why this works: with no speaker output in the room, there's physically nothing for a mic to re-capture. It also improves what you hear — double win.

4. Check your device pairing in Settings → Devices

A subtler cause: mic and speakers on mismatched devices — laptop mic open while audio plays from desk speakers:

  1. Open Settings and more (…) → Settings → Devices.
  2. Set Speaker and Microphone to the same headset where possible.
  3. Use Make a test call to confirm — you'll hear your own recording back and catch problems privately.
Why this works: Teams' echo cancellation is calibrated around paired input/output. A desk-speaker + boosted-laptop-mic combination is the arrangement it struggles with most — aligning devices puts the canceller back in its comfort zone.

Still not fixed?

Frequently asked questions

Why do I hear my own voice back in Teams?

Another participant's speakers are loud enough to reach their microphone, so your voice is being re-broadcast from their device. They typically can't hear it themselves — use the People panel to spot whose mic lights up while you talk, and ask them to switch to headphones.

Does Teams noise suppression remove echo?

No — they're different subsystems. Suppression removes non-speech noise; echo is handled by the echo canceller, which needs sensible acoustics to work with. If speakers are loud and close to an open mic, no setting fully rescues it — that's why headphones are the reliable fix.