MS-700 · Question #207
Hotspot Question You have an Azure Virtual Desktop deployment. You have a Teams deployment. You deploy the Teams for virtual desktop infrastructure (VDI) client on an Azure Virtual Desktop session…
This question tests knowledge of Microsoft Teams VDI registry configuration on Azure Virtual Desktop session hosts, specifically how registry keys control whether Teams media (audio/video) is optimized via client-side redirection or processed server-side.
Question
Explanation
This question tests knowledge of Microsoft Teams VDI registry configuration on Azure Virtual Desktop session hosts, specifically how registry keys control whether Teams media (audio/video) is optimized via client-side redirection or processed server-side.
Approach. The key registry value tested is 'IsWVDEnvironment' (DWORD = 1) located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams. When this key is set to 1, Teams recognizes it is running in an AVD environment and enables media optimization - audio and video are redirected to and processed on the local client endpoint rather than the session host, reducing server load and improving call quality. If this key is absent or set to 0, Teams falls back to server-side media processing (non-optimized path), which consumes session host CPU/GPU resources and degrades call quality. A second common key, 'disableGPU' (DWORD = 1), disables hardware GPU acceleration for Teams rendering on the session host when set. Correct answers depend on interpreting these DWORD values: 1 for IsWVDEnvironment enables optimization; 1 for disableGPU disables GPU acceleration.
Concept tested. Teams for VDI registry configuration on Azure Virtual Desktop - specifically the role of the 'IsWVDEnvironment' and 'disableGPU' DWORD registry keys in controlling media optimization (client-side redirect) and GPU acceleration for Teams sessions on AVD session hosts.
Reference. Microsoft Learn: Use Microsoft Teams on Azure Virtual Desktop - https://learn.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd
Topics
Community Discussion
No community discussion yet for this question.