Fix Teams VDI Camera Is Disabled on a Managed Device

When you run Teams in a virtual desktop infrastructure environment, the camera may appear grayed out or show a message that the camera is disabled on a managed device. This happens because Teams checks the Windows registry and group policy on the VDI host to decide whether the camera is allowed. The problem is not a hardware failure; it is a configuration issue in the VDI session or the host image. This article explains the root cause and gives you step-by-step fixes to re-enable the camera in Teams VDI.

You will learn how to verify the camera status in the VDI session, adjust the Windows camera privacy settings, and apply the correct Teams policy for media redirection. The fixes work for both Windows 10 and Windows 11 VDI hosts, and they apply to pooled and personal virtual machines.

Why Teams VDI Disables the Camera on a Managed Device

Teams in a VDI environment uses a special client that redirects media streams between the virtual machine and the local endpoint. The camera is not accessed directly by the VDI host; it is captured on the thin client or the user’s physical device and then forwarded to the Teams session. This redirection depends on several components being enabled at the same time.

When any of these components is off, Teams shows the camera as disabled or grayed out. The most common cause is the Windows camera privacy setting on the VDI host. Windows 10 and Windows 11 have a global setting that blocks desktop apps from using the camera. If this setting is set to Off, Teams cannot see the camera even if the hardware works.

Another cause is the Teams media redirection policy. In VDI, Teams uses a policy named EnableMediaRedirection that must be set to 1 in the registry. If this policy is missing or set to 0, Teams disables the camera and the microphone. The policy is usually applied by an administrator through group policy, but it can be overridden by a local registry change.

A third cause is the Teams permission policy in the admin center. An administrator can create a permission policy that blocks the camera for specific users. When this policy is assigned to the user, Teams disables the camera even if the VDI settings are correct.

How Media Redirection Works in Teams VDI

In a VDI session, the Teams client runs inside the virtual machine. The camera on the user’s physical device is captured by the VDI redirector component, which sends the video frames to the virtual machine. The Teams client then processes the video and sends it to the meeting. For this to work, the VDI host must support the correct version of the Teams VDI client, and the redirector must be installed on the local device.

The registry key EnableMediaRedirection tells the Teams client whether to use the redirector or to fall back to the local camera. If the key is set to 0, Teams assumes that no camera is available and disables the camera controls in the UI.

Steps to Re-enable the Camera in Teams VDI

Follow these steps in order. Each step fixes a specific layer of the configuration. If the camera is still disabled after one step, move to the next.

1. Check the camera status in the VDI session
   Open Teams in the VDI session and go to Settings > Devices. Under Camera, look for a message that says the camera is disabled. Also open the Windows Camera app on the VDI host. If the Camera app shows a black screen or an error, the problem is in the Windows privacy settings or the device driver. If the Camera app works, the problem is in Teams policy.
2. Enable camera access in Windows privacy settings
   On the VDI host, open Windows Settings > Privacy & security > Camera. Turn on the toggle for Camera access. Then turn on the toggle for Let apps access your camera. Scroll to the list of apps and make sure Teams is set to On. If Teams is not in the list, you may need to sign out and sign back in to the VDI session. After changing the settings, restart Teams and check the camera again.
3. Verify the EnableMediaRedirection registry key
   Open Registry Editor on the VDI host. Navigate to HKLM\SOFTWARE\Policies\Microsoft\Teams. Look for a DWORD value named EnableMediaRedirection. If the value is missing, create it as a DWORD. Set the value to 1. If the value is 0, change it to 1. Close Registry Editor and restart the VDI session. Then open Teams and verify the camera.
4. Check the Teams permission policy in the admin center
   Sign in to the Teams admin center at admin.teams.microsoft.com. Go to Teams apps > Permission policies. Select the policy that is assigned to the user in the VDI session. Verify that the option for Camera is set to On. If it is Off, change it to On and assign the policy to the user. The change may take up to 24 hours to apply. To force an immediate update, have the user sign out of Teams and sign back in.
5. Update the VDI client and the Teams version
   Ensure that the VDI client on the user’s physical device is the latest version. For Citrix, install the latest Workspace app. For VMware, install the latest Horizon Client. Also update the Teams client in the virtual machine to the latest version. Outdated components often cause camera redirection to fail.

If Teams Still Has Issues After the Main Fix

Teams Shows a Camera Disabled Message After the Registry Change

If you set EnableMediaRedirection to 1 and restart the session, but the camera is still disabled, check the registry key again. Some group policies overwrite the local value on each sign-in. To prevent this, set the policy in the group policy editor for the VDI host. Navigate to Computer Configuration > Administrative Templates > Microsoft Teams > Enable Media Redirection and set it to Enabled. Then run gpupdate /force on the VDI host.

Camera Works in the Windows Camera App but Not in Teams

This indicates that the Windows privacy settings are correct, but Teams does not have permission to use the camera. Go to Windows Settings > Privacy & security > Camera and verify that Teams is in the allowed list. If Teams is not listed, uninstall and reinstall the Teams VDI client. After reinstallation, sign in and grant camera permission when prompted.

Camera Is Disabled Only for Some Users in the Same VDI Pool

This points to a Teams permission policy difference. Check the assigned policies for the affected users in the Teams admin center. Use the policy analysis tool to compare the effective permissions. Also verify that the affected users are not in a group that overrides the camera permission.

Item	Windows Privacy Setting	EnableMediaRedirection Registry Key
Location	Windows Settings > Privacy & security > Camera	HKLM\SOFTWARE\Policies\Microsoft\Teams
Effect	Controls whether any app can access the camera	Controls whether Teams uses media redirection in VDI
Applies to	All desktop apps on the VDI host	Only the Teams client
Change method	Toggle in the Settings app	Registry Editor or group policy
Sign-out required	Yes, restart Teams	Yes, restart VDI session

Conclusion

You can now re-enable the camera in Teams VDI by checking the Windows privacy settings, the EnableMediaRedirection registry key, and the Teams permission policy. Start with the privacy settings because they are the most common cause. Then verify the registry key and the admin policy to cover all layers.

For persistent VDI environments, apply the registry key through group policy so it survives reboots. Test the camera in a single VDI session before rolling out the change to all users. Use the Teams admin center policy analysis tool to confirm that the camera permission is not blocked by another policy.