Microsoft Teams Microphone Troubleshooting for Work Calls
When people cannot hear you in a Microsoft Teams call, first separate a muted microphone from a device-selection or permission problem. Test one change at a time, then record whether the microphone works outside Teams. That comparison is more useful than repeatedly restarting everything.
This checklist is for employees and office managers using Teams for work on a Windows 11 laptop. It focuses on a personal headset or laptop microphone, not a meeting-room installation. Follow your organization's device rules; leave managed settings, driver changes, and software reinstalls to authorized IT staff.
Keep the meeting moving first
If the meeting has already started, tell the organizer through chat that you have an audio problem. Agree on a temporary way to contribute, such as typing your questions or using another approved device. Avoid turning the client meeting into a live troubleshooting session.
Choose one person to confirm whether they can hear you. If several colleagues offer conflicting instructions, pause and assign a single test partner. Use a harmless phrase such as “audio check from the office laptop,” not confidential client information.
Write down whether the problem affects every meeting, one meeting, or only a particular headset. A useful symptom is “others cannot hear me, but I hear them.” “Teams is broken” does not identify which part of the call has failed.
Check mute and the selected input
Look for both a Teams mute indicator and a physical mute control on your headset. A boom microphone may have its own mute position. In Teams, open Settings, then Devices, and check the selected microphone. During a meeting, the arrow beside Mic leads to audio settings.
If available in the desktop app, use Make a test call and listen to the recorded message. This test is not available in Teams for web. Microsoft's Teams microphone guidance also covers reconnecting an external mic and checking a Bluetooth headset's charge and connection.
Note the exact input name before changing it. A laptop, webcam, dock, and headset can present different choices. Select the device you intend to speak into rather than assuming that a familiar brand name identifies the correct input.
Make one controlled comparison
If company policy permits, compare the headset with the laptop's built-in microphone. Keep the same Teams session and test partner, and change only the input. Record the result before trying a different connection.
For example, if the built-in mic works but the headset does not, send IT that distinction. It narrows the investigation without proving the headset is faulty. A connection, selected input, mute control, or device setting could still explain the difference.
Check whether Windows receives your voice
In Windows 11, open Settings, then System, then Sound. Under Input, select the intended microphone. Open its properties and use the microphone test to record and play back a short sample. Microsoft's Windows microphone troubleshooting instructions describe this test and input-volume controls.
Under Settings, Privacy & security, Microphone, review whether microphone access and the relevant app access are enabled. Desktop-app access is a separate setting, and desktop apps do not appear in the individual app list. If controls are managed or unavailable, ask IT rather than attempting to bypass the restriction.
Do not grant microphone permission to unrelated applications. On a work device, ask your support contact which access settings your organization expects. Record a disabled or managed setting as evidence; it is not an invitation to remove company controls.
Use the result to choose the next step
Windows records clearly, but Teams does not: report the selected Teams input and whether you used the desktop app or browser.
Windows does not record the intended microphone: report whether the device appears in the Input list and whether another approved microphone works.
The issue occurs only through a dock: record the dock model and the result of an approved direct connection.
Several employees fail at once: report the shared timing and location so IT can check for a wider problem before replacing individual accessories.
These are routing clues, not diagnoses. A successful short recording does not prove that every meeting will work, and a failed recording alone does not identify a broken component.
Treat browser and remote sessions separately
For Teams in a browser, check the microphone permission for the actual Teams site. Do not broadly allow every website to record audio. Microsoft notes that browser permission is separate from the desktop app's settings; changing one does not establish that the other is configured correctly.
Tell IT if Teams runs inside a remote desktop or virtual workspace. Include where the headset is physically connected and where Teams is running. Stop short of changing remote-session policies yourself. A support technician needs that distinction before deciding which device or session to inspect.
Copy this audio issue handoff
Use the following fields in your support request. Keep screenshots free of private chat messages, meeting links, and customer information. For a broader incident, use our IT support ticket template.
Impact and deadline: which work call is affected, and when help is needed.
Setup: laptop asset label, Windows version, Teams desktop or browser, headset model, and any dock.
Symptom: who cannot hear whom, and whether the problem occurs in more than one meeting.
Selected input: the microphone name shown in Teams and Windows.
Comparison: Windows recording result, Teams test result if available, and alternate approved microphone result.
Changes and timing: what changed just before the issue, what you tested, and the outcome of each test.
Next owner: who will continue troubleshooting and the agreed temporary workaround.
An example entry might read: “USB headset is selected in both places. Windows sample is audible. Teams desktop test is silent. Built-in mic works in Teams. No driver changes made.” This is an illustrative handoff, not a client case.
Confirm the fix before closing the ticket
Repeat the original scenario with the same headset and connection. Ask a colleague to confirm intelligible speech, not merely that an audio indicator moves. Document the successful setup and any remaining limitation.
If the issue belongs to a shared room rather than one laptop, use the separate meeting room technology checklist. That review covers the room as a system instead of treating every failure as a personal headset problem.
For help organizing Teams and related business collaboration tools, discuss your setup with Sosa Solutions NYC through our Microsoft 365 and cloud services page.
Comments