Why Teams goes wrong in a particular way
Discord problems are usually about modes; Zoom problems are usually about level. Teams problems are usually about which device, because Teams is the conferencing app most likely to be running on a managed laptop that has three microphones attached to it: the lid array, a docking-station input, and whatever headset the person actually put on. Windows changes the default when hardware is plugged and unplugged, Teams remembers its own separate choice, and the two drift apart.
The result is a call where you are audible but sound like you are speaking from the corridor, because the lid array is picking you up from half a metre away while the headset hangs on your neck doing nothing. A yes/no microphone test cannot catch it. Reading the actual device name can.
Every audio control Teams exposes
The path is Teams on the desktop → the ••• beside your profile picture → Settings → Devices → Audio Settings.
| Control | Where | What it does | Browser equivalent |
|---|---|---|---|
| Microphone drop-down | Settings → Devices → Audio Settings | Microsoft’s article lists a primary audio device, a speaker and a microphone as three separate choices, which is why picking a headset once is not always enough. | deviceId |
| Automatically adjust mic sensitivity | Settings → Devices → Audio Settings | Teams rides the input level for you. | autoGainControl |
| Noise suppression | Settings → Devices → Audio Settings | Described by Microsoft as reducing background sounds picked up by your microphone. | noiseSuppression |
| Sync device buttons | Settings → Devices → Audio Settings | Lets the mute button on the headset itself act on Teams — the reason a headset can appear muted with nothing wrong in software. | none |
| Audio settings (in a call) | During a call: More → Audio settings | Microsoft lists picking the primary audio device, adding noise suppression and choosing high-fidelity music mode here. | none |
Which edition these labels come from. Microsoft publishes a separate device-settings page per edition and both were read on 2026-08-15: one for Teams Free, one for the work-or-school build. The control names above are common to both. The routes differ only in what Microsoft calls the ••• button — Settings and more in the work-or-school article, the ••• beside your profile picture in the Free one — and both end at Devices.
How to identify the device you are actually using
Open the Input device tab above and read the list. Three things there are worth more than any amount of clicking around in Teams.
- The names are the operating system’s names. Whatever your browser calls a device, Teams calls it the same thing, because both are asking Windows or macOS. Matching them is exact, not approximate.
- The counts tell you what is attached. The panel reports how many inputs and how many outputs exist. A laptop with a headset plugged in typically shows at least two of each; one of each means the headset is not being seen as a device at all, which is a cable or driver problem, not a Teams problem.
- The groupId proves the pairing. When your selected microphone shares a group with an output, the panel says so by name. That is the difference between “a headset is plugged in” and “I am recording through the headset”, which is exactly the confusion Teams’ three-device layout creates.
Browsers report devices in exactly three kinds, which is why a headset always appears twice:
audioinput, audiooutput, videoinput. The boom microphone is one entry, the earpieces are another, and only the group identifier ties
them together. The headset mic test goes through that in detail.
Audible, and still sounding like the corridor
A colleague reports you sound far away on every Teams call, though nobody says you are inaudible. You press start here and speak normally. The waveform moves, the hold figure sits well below the target band, and the device list shows Microphone Array selected while a USB headset also appears in the list. Recording ten seconds and playing it back confirms the room sound.
That is the lid array picking you up across a desk, and the size of the effect is something you can calculate. Sound pressure falls with distance, so moving from a lid array about 50 cm away to a boom about 3 cm from your mouth is a distance ratio of roughly 17 — worth around 24 dB in a free field, which is why the two devices sound like different rooms. Real rooms reflect and blunt that figure, so treat it as the ceiling rather than a promise; the direction is not in doubt. Select the headset in this page’s picker, repeat the test, then set the same device in Teams under Devices → Audio Settings. Nothing was broken; two devices were both working and the wrong one was chosen.
When the fault really is Teams
- This page works, Teams desktop hears nothing. Device choice or a hardware mute the app cannot see. Check Sync device buttons.
- This page works, Teams in a browser hears nothing. A site permission for the Teams URL, not a device problem. Microsoft’s web article walks through the per-browser permission screens.
- Neither works. The fault is below both, in Windows or the hardware — start at the Windows 11 microphone page.
- Both work but you sound processed. Noise suppression. Compare with the switch above, then match the setting in the Teams panel.