Troubleshoot Microsoft Teams for Azure Virtual Desktop
This article describes known issues and limitations for Teams on Azure Virtual Desktop, as well as how to log issues and contact support.
Known issues and limitations
Using Teams in a virtualized environment is different from using Teams in a nonvirtualized environment. For more information about the limitations of Teams in virtualized environments, check out Teams for Virtualized Desktop Infrastructure.
Client deployment, installation, and set up
- With per-machine installation, Teams on VDI isn't automatically updated the same way non-VDI Teams clients are. To update the client, you'll need to update the VM image by installing a new MSI.
- Media optimization for Teams is only supported for the Remote Desktop client on machines running Windows 10 or later or macOS 10.14 or later.
- Use of explicit HTTP proxies defined on the client endpoint device should work, but isn't supported.
- Zoom in/zoom out of chat windows isn't supported.
- Media optimizations isn't supported for Teams running as a RemoteApp on macOS endpoints.
Calls and meetings
- Incoming and outgoing video stream resolution is limited to 720p.
- The Teams app doesn't support HID buttons or LED controls with other devices.
- This feature doesn't support uploading custom background images.
- This feature doesn't support taking screenshots for incoming videos from the virtual machine (VM). As a workaround, we recommend you minimize the session desktop window and screenshot from the client machine instead.
- This feature doesn't support content sharing for redirected videos during screen sharing and application window sharing.
- The following issues occur during application window sharing:
- You can't select minimized windows. In order to select windows, you'll need to maximize them first.
- If you've opened a window overlapping the window you're currently sharing during a meeting, the contents of the shared window that are covered by the overlapping window won't update for meeting users.
- If you're sharing admin windows for programs like Task Manager in Windows, meeting participants may see a black area where the presenter toolbar or call monitor is located.
- Switching tenants can result in call-related issues such as screen sharing not rendering correctly. You can mitigate these issues by restarting your Teams client.
- Teams doesn't support the ability to be on a native Teams call and a Teams call in the Azure Virtual Desktop session simultaneously while connected to a HID device.
For Teams known issues that aren't related to virtualized environments, see Support Teams in your organization.
Remote Desktop WebRTC Redirector Service
The Remote Desktop WebRTC Redirector Service isn't pre-installed on the following Azure marketplace images:
- Windows 11 Enterprise multi-session + Microsoft 365 Apps Version 23H2 (build 22631.3593).
- Windows 11 Enterprise multi-session + Microsoft 365 Apps Version 22H2 (build 22621.3593).
To resolve the issue, either redeploy session hosts using the latest marketplace image where the WebRTC Redirector Service is pre-installed, or install it separately. You can find the download link and steps at Install the Remote Desktop WebRTC Redirector Service.
Collect Teams logs
If you encounter issues with the Teams desktop app in your Azure Virtual Desktop environment, collect client logs under %appdata%\Microsoft\Teams\logs.txt on the host VM.
If you encounter issues with calls and meetings, you can start collecting Teams diagnostic logs with the key combination Ctrl + Alt + Shift + 1. Logs will be written to %userprofile%\Downloads\MSTeams Diagnostics Log DATE_TIME.txt on the host VM.
Contact Microsoft Teams support
To contact Microsoft Teams support, go to the Microsoft 365 admin center.
Next steps
Learn more about how to set up Teams on Azure Virtual Desktop at Use Microsoft Teams on Azure Virtual Desktop.
Learn more about the WebRTC Redirector Service for Teams on Azure Virtual Desktop at What's new in the WebRTC Redirector Service.