The Microsoft Teams product group has been working hard to deliver seamless user experience in Azure Virtual Desktop (AVD) for Teams users to provide similar experience on both physical and virtualized (aka AVD) session.
The capability to share your windows in Azure Virtual Desktop session while using Teams is now generally available.
That said, you need to ensure the following prerequisites are met:
- Running Azure Virtual Desktop client version 1.2.3770 or later (1.2.3770 is the latest version available at the time of writing)
- x64 download link https://go.microsoft.com/fwlink/?linkid=2139369
- ARM download link https://go.microsoft.com/fwlink/?linkid=2139370
- x86 download link https://go.microsoft.com/fwlink/?linkid=2139456
- Having the WebSocket service (aka Remote Desktop WebRTC) version 1.31.2211.15001 or later (1.31.2211.15001 is the latest available at the time of writing) installed – download link https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE5c8Kk
In addition, if Teams is running as a published application (remote app) – meaning users logon to Teams through the published application and not through a Windows session – you need to also have the below registry:
- Path: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\WebRTC Redirector\Policy
- Registry key name: ShareClientDesktop
- Registry type: DWORD
- Value: 0 (1 to disable, 0 to enable the feature)
You may also need the application sharing registry key too:
- Path: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\WebRTC
Redirector\Policy - Registry key name: DisableRAILAppSharing
- Registry type: DWORD
- Value: 0 (1 to disable, 0 to enable the
feature)