Fix Teams VDI Optimization Is Not Active after Upgrading to New Teams

When you upgrade to the new Teams in a virtual desktop infrastructure environment, the VDI optimization status can show as not active. This leaves calls and meetings running through the local network stack instead of the optimized media path. The cause is usually a missing registry key, an outdated VDI client, or a policy that blocks the new Teams optimization. This article explains the root cause and gives you step-by-step fixes to restore VDI optimization for the new Teams.

Why VDI Optimization Fails After Upgrading to New Teams

The new Teams uses a different media stack than classic Teams. In a VDI environment, the client redirects audio and video processing to the local endpoint to reduce latency and server load. This redirection depends on a registry flag that the VDI client must set on the host. When you upgrade to the new Teams, the installer may not update this flag correctly. The result is that Teams detects the VDI environment but cannot confirm optimization, so it falls back to the non-optimized path.

Another common cause is an outdated VDI client. The new Teams requires a minimum client version that supports the new media architecture. If your client is older, it does not send the correct signals to the host, and Teams reports optimization as not active. A third cause is a meeting policy that disables media optimization for the user. Even with the correct registry and client, a restrictive policy can block the feature.

How Teams Detects VDI Optimization

Teams checks the registry value IsOptimized under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams. The VDI client sets this value to 1 when it is ready to handle media locally. Teams also checks the client version and the meeting policy in real time. If all three conditions are met, the status shows as optimized. If any condition fails, Teams shows a warning and uses the non-optimized path.

Steps to Diagnose and Fix Teams VDI Optimization Not Active

Follow these steps in order. After each step, check the Teams client to see if the optimization status changes.

1. Check the current optimization status
   In the Teams desktop client, select your profile picture, then select About. Look for the VDI optimization status. If it says Not optimized or Not active, proceed to the next step. You can also press Ctrl+Alt+Shift+M to open the media diagnostics panel, which shows the media path and the optimization state.
2. Verify the registry key on the VDI host
   Open Registry Editor on the VDI host. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams. Find the DWORD value IsOptimized. If it is missing or set to 0, double-click it and change the value to 1. If the value does not exist, right-click the Teams key, select New > DWORD (32-bit) Value, name it IsOptimized, and set it to 1. Restart Teams.
3. Update the VDI client to the latest version
   Check the version of your VDI client, such as Citrix Workspace or VMware Horizon Client. The new Teams requires client version 1.7.00.32171 or later. Download the latest version from your vendor’s site and install it on the local endpoint. After the update, reconnect to the VDI session and check the optimization status.
4. Confirm the meeting policy allows media optimization
   Sign in to the Teams admin center. Go to Meetings > Meeting policies. Select the policy assigned to the affected user. Under Real-time audio/video, ensure that Allow media optimization for VDI is set to On. If it is Off, change it to On and save. Wait a few minutes for the policy to propagate, then ask the user to sign out and back in.
5. Force a cache refresh on the VDI host
   On the VDI host, close Teams completely from the system tray. Navigate to %appdata%\Microsoft\Teams and delete the contents of the Cache folder. Restart Teams. This clears any stale state that might prevent the optimization flag from being read.
6. Verify the WebRTC service is running
   Press Ctrl+Shift+Esc to open Task Manager on the VDI host. Look for the Teams WebRTC service. If it is not running, restart Teams. If the service stops repeatedly, reinstall the new Teams VDI package from the Microsoft 365 admin center.

If Teams Still Shows VDI Optimization Not Active

Teams Shows a Warning About Media Path in Calls

If the status still shows not active, the issue may be with the media path itself. Open the media diagnostics panel with Ctrl+Alt+Shift+M. Check the Network section. If the path shows UDP blocked, the firewall might be blocking the RTP ports used for optimized media. Open UDP ports 3478 through 3481 on the local endpoint and the VDI host.

VDI Optimization Works for Classic Teams but Not New Teams

This indicates the registry key is correct but the new Teams client is not reading it. Make sure you are running the new Teams client, not the classic one. You can check by selecting the ellipsis next to your profile picture and looking for the About option. The new Teams shows a version number of 2.x. If you are on classic Teams, switch to the new Teams by selecting Try the new Teams from the top of the app.

Policy Change Does Not Take Effect for VDI Users

If you enabled the policy but users still see not active, the policy might be overridden by a global policy. Check the effective policy assignment for the user in the Teams admin center. Go to Users > Manage users, select the user, and then select Policies. Confirm that the meeting policy shown is the one you edited. If not, assign the correct policy explicitly.

New Teams VDI Optimization vs Classic Teams VDI Optimization

Item	New Teams VDI Optimization	Classic Teams VDI Optimization
Media stack	New WebRTC-based stack	Legacy media stack
Minimum VDI client version	1.7.00.32171 or later	No strict minimum
Registry key	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\IsOptimized	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\IsOptimized (same key)
Policy control	Allow media optimization for VDI	Allow media optimization for VDI (same policy)
Diagnostics shortcut	Ctrl+Alt+Shift+M	Ctrl+Alt+Shift+M (same shortcut)

After following these steps, you should see the VDI optimization status as active in the new Teams client. Test a call or meeting to confirm that the media path is optimized. To avoid future issues, set a recurring schedule to update your VDI client whenever Microsoft announces a new Teams update. You can also use the Teams admin center to monitor media quality reports for VDI users, which will show if optimization drops again.