Teams Meeting Audio (Human Voices) Completely Muted Over Chrome Remote Desktop / RustDesk on Windows 11

Teams requires working device audio and, when used over remote connections, correct remote-audio redirection. If meeting audio (voices) is muted only when using remote desktop tools, the issue is with how audio is being redirected from the Host to the Client, not with a configurable “monitor-only” mode in Teams.

From the available guidance, the only supported way to ensure call/meeting audio is heard over a remote session is to:

1. Make sure Windows audio is working normally on the Host
   • On the Host PC, open Settings > System > Sound.
   • Under Choose where to play sound, select the intended speaker device and ensure it is not muted and volume is up.
   • If the device is missing or disabled, re‑enable it via Advanced > More sound settings and the Playback tab, or reinstall/fix drivers as needed (for example, using the Windows audio troubleshooter as in similar “no audio device” cases).
2. Ensure remote desktop audio redirection is configured correctly (where applicable)
   • For Microsoft Remote Desktop (RDP) scenarios, the documented requirement is:
     • On the Client, open Remote Desktop Connection → Local Resources tab → Settings… under Remote audio.
     • Set Remote audio playback to Play on this computer.
     • Set Remote audio recording to Record from this computer.
     • Select OK.
   • This configuration ensures that both playback and recording streams are redirected between the Host and Client so that apps like Teams can establish their media path.
3. Ensure Teams is allowed to use the Host’s mic and speakers
   • On the Host, verify device audio settings as described for Teams:
     • In Settings > System > Sound, under Input, select a valid microphone in Choose a device for speaking or recording and make sure it is enabled and unmuted.
     • If the mic is disabled, re‑enable it via Advanced > More sound settings → Recording tab → right‑click the mic → Enable.
   • Teams relies on the OS exposing valid input/output devices; if these are blocked or missing, call audio can fail.
4. Use Teams’ standard audio selection
   • When joining the meeting on the Host (desktop app or browser), select Computer audio so Teams uses the Host’s default speaker and mic.
   • Once in the meeting, the meeting window can remain joined with mic muted; Teams does not require active speaking, only that valid devices exist.

The provided documentation does not describe any supported method to bypass or relax Teams’ media behavior specifically for one‑way passive monitoring over third‑party remote desktop tools. The supported approach is to ensure:

• The Host has a valid, enabled playback device and (if required) an enabled input device.
• Remote desktop audio redirection is configured to Play on this computer / Record from this computer so that the media stack sees a working two‑way channel.

If third‑party tools like Chrome Remote Desktop or RustDesk do not fully emulate this behavior, they may not be able to carry Teams meeting audio reliably; in that case, using a remote solution that correctly exposes Windows remote audio in the way documented for Remote Desktop is required.

References:

• My microphone isn't working in Microsoft Teams
• My speaker isn't working in Microsoft Teams
• Manage audio settings in Microsoft Teams meetings
• Configure audio and video redirection over the Remote Desktop Protocol (dev-box)

Dear @Damir,

Good day! Welcome to Microsoft Q&A forum!

Based on your description, I understand that when accessing Microsoft Teams meetings through remote desktop tools (like Chrome Remote Desktop, RustDesk, or Parsec), you can hear system and app sounds normally, but the actual meeting audio (human voices) is completely muted. You’ve already tried multiple troubleshooting steps across different devices, and it appears the Teams media engine may be blocking inbound communication audio when a proper hardware audio channel isn’t detected on the host machine. You’re looking for a way to allow passive, one-way audio monitoring of Teams meetings over non-Microsoft remote desktop solutions.

Regarding this situation, you could try to clear Teams cache to check if the behavior changes.

If not, it requires deeper investigation from the backend or engineering teams.

I recommend raising a support ticket with Microsoft Support team because this will allow a Technical Support Engineer to perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis.    

Please note that this is a community forum where users help one another. We do not have control over user accounts, including login issues, password resets, or access changes.

Here’s what your Microsoft 365 Global Admin should do next:  

Submit a Service Request: The Global Admin should create a service request with Microsoft support to get advanced technical assistance and diagnostics. For detailed instructions on how to get support, please refer to: Get support - Microsoft 365 admin. 

If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread.