Echo in Teams Calls: Trace It, End It

MBy the MutePoint admin desk · Published July 29, 2026 · Last updated July 29, 2026

This page contains affiliate links — see our disclosure.

Echo is a loop: meeting audio leaving someone's speakers and re-entering a live mic. The culprit usually can't hear it themselves. Trace via the People panel (whose mic indicator lights while others speak?), fix with headphones at that desk — and when one person joins on two devices, add the second without audio, which Teams explicitly offers.

New Teams client (classic noted where different), Windows & Mac — checked against official vendor documentation July 28, 2026.

1. Trace from the People panel

Open People during the echo.
Watch for the mic indicator glowing while someone else talks — that's re-broadcast in progress.
Organiser: mute candidates one by one until silence; then headphones for the guilty desk.

Why this works: the echo loop has exactly one open junction, and the indicator lights betray it — playback re-entering a mic registers as speech to Teams.

2. Join second devices audio-off

Teams detects an existing join and offers to add this device — take the option without audio.
Already doubled? Mute mic and zero the speaker volume on one of them.
Shared rooms: exactly one laptop owns audio; others join deaf-and-mute.

Why this works: two live endpoints in one room re-amplify each other beyond what echo cancellation can subtract; one-audio-per-room is the rule that prevents the whole class.

An admin's honest note

Echo fixed, background noise next?

Policy locks and hardware gates mean Teams' own suppression isn't always yours to fix. Krisp works underneath the client — no admin consent needed for your own mic — and the free 60-minutes-a-day plan covers a stand-up habit while you evaluate.

Evaluate Krisp free Krisp for Teams users — the full picture →

3. Align your own devices

Settings → Devices: set speaker and mic to the same headset where possible.
Run Make a test call — the playback exposes residual echo privately.
Using desk speakers regardless? Volume down, mic further away, mute between turns.

Why this works: Teams' canceller models the delay between its own output and your mic's input; matched devices keep that delay stable, and quiet playback keeps residue within subtractable range.

Still stuck?

Every call, every room? Windows audio-driver 'enhancements' can fight the canceller — disable them in Sound settings.
Conference room + laptops? The room system carries audio; laptops join silent.
Metallic garble rather than echo? Different fault — see robotic/choppy voice.

Quick answers

Why can't the person causing echo hear it?

Their voice never loops back to them — the meeting re-broadcasts everyone else through their open mic. That asymmetry is why tracing beats asking.

Will noise suppression remove echo?

No — separate subsystems. Suppression removes non-speech noise; echo is handled by cancellation plus sane acoustics, and headphones remain the reliable cure.