After upgrading to the new Teams on a virtual desktop infrastructure, many users find their camera is grayed out or shows a disabled error. This happens because the new Teams client uses a different media stack than the classic client, and the VDI redirect settings no longer match. The camera becomes unavailable even though the physical webcam works fine on the host machine. This article explains why the camera is disabled and provides step-by-step fixes for both IT admins and end users.
You will learn how to verify the VDI plugin, adjust the Teams policy, and check the Windows privacy settings that control camera access. The fixes cover the most common causes, from missing WebRTC redirection to outdated registry keys. By the end, you can restore camera functionality in the new Teams without reverting to the classic client.
Key Takeaways: Fixing Teams VDI Camera Disabled After Upgrade
- Teams admin center > Meetings > Meeting policies > Media redirection: Enables the WebRTC redirection that the new Teams VDI requires for camera access.
- Teams VDI plugin installation: The new Teams needs the latest plugin version; an outdated plugin blocks the camera.
- Windows Settings > Privacy & security > Camera: Desktop app access must be turned on for the camera to appear in Teams.
Why the Camera Gets Disabled in New Teams on VDI
The new Teams client uses a different media engine for handling audio and video in virtual environments. Classic Teams relied on the Windows Media Foundation and a simple device redirection. The new Teams uses WebRTC, which requires a specific VDI plugin to redirect the camera from the local endpoint to the virtual session. When this plugin is missing or outdated, the Teams client cannot see any camera device, so it disables the video option entirely.
Another common cause is the Teams meeting policy that controls media redirection. In the Teams admin center, the policy setting Enable media redirection for WebRTC must be set to On for the new Teams to use the local camera. If it is off, Teams falls back to a simulated camera that is not available, resulting in a disabled camera icon.
Finally, Windows privacy settings on the local machine can block camera access for desktop apps. After an upgrade, these settings sometimes reset, preventing the Teams VDI plugin from accessing the webcam. The combination of these three factors explains most camera failures after upgrading to new Teams.
The Role of the Teams VDI Plugin
The Teams VDI plugin is a small software component that runs on the user’s local device, not inside the virtual machine. It captures the webcam feed and sends it to the virtual session. The new Teams requires version 1.0.0.23 or later of this plugin. If the plugin is not installed or is an older version, the camera will not appear in Teams settings.
Steps to Fix the Disabled Camera in New Teams on VDI
Follow these steps in order. Each step addresses a specific cause. Start with the simplest check and then move to admin-level changes.
- Check the Teams VDI plugin version
On the local machine, open the Teams VDI plugin installer from the installation folder. Look for version 1.0.0.23 or higher. If the version is older, download the latest plugin from the Microsoft 365 admin center and install it. Restart the Teams client after installation. - Verify the media redirection policy in the Teams admin center
Sign in to the Teams admin center at admin.teams.microsoft.com. Go to Meetings > Meeting policies. Select the policy assigned to the affected user. Under Media redirection, set Enable media redirection for WebRTC to On. Save the policy and wait up to 24 hours for propagation, or force a refresh by restarting Teams. - Enable camera access in Windows privacy settings
On the local machine, open Settings > Privacy & security > Camera. Turn on Camera access and Let desktop apps access your camera. If these are off, Teams cannot use the camera even with the correct plugin. Toggle them on and restart Teams. - Reset the Teams cache to clear stale device settings
Close Teams completely. Navigate to %appdata%\Microsoft\Teams and delete the Cache and blob_storage folders. Restart Teams. This forces the client to re-enumerate devices, which often brings the camera back. - Check the registry for VDI redirection keys
On the local machine, open Registry Editor and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams. Look for a value named EnableWebRTC. If it does not exist, create a DWORD value and set it to 1. This is a temporary workaround for some VDI environments that do not fully support the new plugin.
After completing these steps, restart the Teams client and test the camera in a test meeting. If the camera still shows as disabled, proceed to the next section for additional checks.
If Teams Still Has Issues After the Main Fix
Teams shows a black or gray camera icon in the device settings
This often means the plugin is not running. Open the Task Manager on the local machine and look for Teams VDI Plugin in the processes list. If it is not there, reinstall the plugin. Also, ensure the plugin is not blocked by antivirus software. Add the plugin executable to the exclusion list and restart the machine.
The camera works in classic Teams but not in new Teams
Classic Teams uses a different redirection method. If only new Teams fails, the WebRTC redirection policy is likely off. Recheck the meeting policy and confirm the user is assigned the updated policy. Also, verify that the VDI environment supports WebRTC redirection. Some older VDI versions require an update to the VDI broker.
The camera is enabled but the video is choppy or freezes
This is not a disabled camera issue but a bandwidth problem. Reduce the video resolution in Teams device settings. Also, check the network bandwidth between the local machine and the VDI broker. A minimum of 1.5 Mbps upload is required for video calls.
New Teams VDI vs Classic Teams VDI: Camera Support Differences
| Item | New Teams VDI | Classic Teams VDI |
|---|---|---|
| Media engine | WebRTC | Windows Media Foundation |
| Plugin required | Yes, version 1.0.0.23+ | No plugin needed for basic redirection |
| Policy setting | Enable media redirection for WebRTC | Enable media redirection |
| Camera compatibility | Requires local plugin and privacy permissions | Uses standard device redirection |
| Common failure | Camera disabled after upgrade | Camera works but with higher latency |
The table shows why the upgrade can break the camera. The new Teams relies on the plugin and the WebRTC policy, both of which are new requirements. Classic Teams had simpler redirection, so it worked without extra configuration.
Conclusion
You can now restore the camera in new Teams on VDI by checking the plugin version, enabling the WebRTC media redirection policy, and adjusting Windows privacy settings. Start with the plugin update because that is the most frequent cause. After applying the fixes, test the camera in a test meeting to confirm the video works.
Next, verify that the VDI broker supports the new Teams requirements. If you manage multiple users, deploy the plugin via a software distribution tool and set the policy through the Teams admin center. As an advanced tip, use the Teams diagnostic tool in the admin center to check the exact policy assignments for a specific user, which speeds up troubleshooting.