When you run the new Teams client on Azure Virtual Desktop, some features such as call recording, background effects, or the app switcher may disappear. This happens because the Teams desktop app in a virtualized environment relies on WebRTC media stack settings and registry keys that are not configured by default. This article explains the technical cause and gives you a step-by-step fix to restore missing features.
You will learn which registry keys control the media stack, how to enable the correct mode for AVD, and what to do when the issue persists after the main fix.
Key Takeaways: Restore Full Teams Functionality in AVD
- Registry key HKCU\Software\Microsoft\Teams\EnableMediaStackForTeams: Set this to 1 to force the WebRTC media stack that supports advanced call features.
- Registry key HKCU\Software\Microsoft\Teams\IsWVDEnvironment: Set this to 1 so Teams knows it runs in a virtualized environment and enables the correct UI elements.
- Teams admin center > Teams apps > Setup policies: Verify that the policy assigned to AVD users does not hide app features like the app bar or chat.
Why the New Teams Client Loses Features in Azure Virtual Desktop
The new Teams client is a progressive web app that runs on the Electron framework. In a normal desktop environment, Teams automatically detects the local hardware and enables features such as background blur, noise suppression, and call recording. In Azure Virtual Desktop, the client runs on a shared virtual machine where the media stack must be explicitly told to use the WebRTC protocol. If the registry keys that control this behavior are missing or set to zero, Teams falls back to a limited mode that disables several features.
The root cause is that the new Teams client does not automatically detect the AVD environment. The registry key IsWVDEnvironment tells the client that it is running in a Windows Virtual Desktop session. Without this key, Teams may show a blank app bar, missing meeting controls, or no option to change backgrounds. The key EnableMediaStackForTeams forces the WebRTC media stack, which is required for audio, video, and screen sharing to work correctly in a remote session.
Additionally, Teams policies can hide features. If your organization assigns a setup policy that disables the app bar or chat, those features will not appear regardless of the registry settings. This is why you must check both the client-side registry and the server-side policy.
What the Registry Keys Actually Control
The registry path HKEY_CURRENT_USER\Software\Microsoft\Teams contains several values that affect the new Teams client. The two most important are:
- EnableMediaStackForTeams – When set to 1, Teams uses the new WebRTC media stack. When set to 0 or missing, Teams uses the older media stack that lacks features like live captions and custom backgrounds.
- IsWVDEnvironment – When set to 1, Teams knows it is running in a virtualized Windows session and adjusts its UI to show all available controls. When missing, Teams may hide the app bar or meeting options.
Steps to Restore Missing Features in the New Teams Client on AVD
Follow these steps in order. You will need local administrator rights on the AVD session host to edit the registry. The steps apply to both Windows 11 and Windows 10.
- Close Teams completely
Right-click the Teams icon in the system tray and select Exit. Then open Task Manager with Ctrl+Shift+Escape and end any remaining Teams processes. - Open Registry Editor
Press Windows+R, type regedit, and press Enter. If User Account Control prompts you, select Yes. - Navigate to the Teams registry path
Go to HKEY_CURRENT_USER\Software\Microsoft\Teams. If the Teams folder does not exist, right-click Microsoft, select New > Key, and name it Teams. - Create or modify the EnableMediaStackForTeams value
Right-click in the right pane, select New > DWORD (32-bit) Value, and name it EnableMediaStackForTeams. Double-click it, set Value data to 1, and select OK. - Create or modify the IsWVDEnvironment value
Repeat the same process to create a DWORD named IsWVDEnvironment. Set its Value data to 1 and select OK. - Restart Teams
Close Registry Editor and start Teams from the Start menu. Sign in and check whether the missing features have returned. - Verify the Teams policy assignment
Open the Teams admin center at admin.teams.microsoft.com. Go to Teams apps > Setup policies. Select the policy that applies to your AVD users and confirm that the App bar and Chat options are set to On.
If the registry keys are already present and set to 1, skip step 4 and 5. The issue may be caused by a policy, so check step 7 first.
If You Manage Multiple AVD Session Hosts
For a fleet of session hosts, you can apply the registry changes through Group Policy. Create a Group Policy preference that sets the two DWORD values under HKEY_CURRENT_USER\Software\Microsoft\Teams. Link the policy to the OU that contains your AVD session hosts. This ensures every user gets the correct settings automatically.
If Teams Still Has Issues After the Main Fix
Teams Shows a Blank Window After Editing the Registry
A blank window usually means the Teams cache is corrupted. Close Teams, then delete the contents of %appdata%\Microsoft\Teams. Restart Teams and sign in again. This clears cached data that may conflict with the new registry settings.
Missing Features Persist for Only Some Users
Check whether those users have a different Teams setup policy. Go to the Teams admin center and compare the policies assigned to the affected users. You can see the effective policy by going to Users > Manage users, selecting a user, and opening the Policies tab.
Call Recording Is Still Not Available
Call recording is a Teams admin policy, not a client setting. Go to Teams admin center > Meetings > Meeting policies. Ensure the policy assigned to the user has the Allow cloud recording option set to On. Even with the registry fix, recording will not appear if this policy blocks it.
Background Effects Do Not Appear
Background effects require the WebRTC media stack. Verify that EnableMediaStackForTeams is set to 1. Also check that the user’s video device is working in the AVD session. If you use a USB camera redirection solution, confirm that the camera is available in Windows Settings > Devices > Cameras.
New Teams Client on AVD vs on a Local PC: Key Differences
| Item | New Teams on AVD | New Teams on a Local PC |
|---|---|---|
| Media stack detection | Requires registry key EnableMediaStackForTeams | Detected automatically |
| Environment awareness | Requires registry key IsWVDEnvironment | Not needed |
| Policy enforcement | Setup and meeting policies apply from the tenant | Same policies apply |
| Feature availability | Depends on registry and policies | Usually works out of the box |
| Performance | Relies on host resources and network | Uses local hardware |
The main difference is that AVD requires manual configuration to unlock the same feature set. Once you set the two registry keys, the new Teams client behaves almost identically to a local installation, with the exception of hardware-dependent features that need proper redirection.
Conclusion
You can now restore missing features in the new Teams client on Azure Virtual Desktop by setting the EnableMediaStackForTeams and IsWVDEnvironment registry keys. You also know how to verify that your Teams setup policy does not hide features. After applying the fix, restart Teams and check the app bar, meeting controls, and call recording. For advanced management, use Group Policy to push the registry keys to all session hosts.
If you still encounter missing features, review your meeting and setup policies in the Teams admin center. You can also run the Teams diagnostic tool from the admin center to identify policy conflicts. As a next step, test the fix on a single session host before rolling it out to the entire fleet.