Fix Teams App Is Blocked by Organization Policy in a New Teams Client

When you open the new Teams client and see the message that the app is blocked by organization policy, your account cannot start Teams. This block usually comes from an admin setting that restricts which client versions are allowed. The new Teams client is a different app from classic Teams, so it has its own policy controls. This article explains why the block happens and shows you how to fix it on your side or with admin help.

Why the New Teams Client Is Blocked by Organization Policy

The new Teams client is a separate application from classic Teams. It uses the same user account but has a different codebase and a different update mechanism. Because of this, Microsoft 365 admins can apply policies that specifically target the new client. When a policy blocks the new client, Teams shows an error message and refuses to start.

The most common root cause is the Teams client settings policy in the Teams admin center. This policy has a setting called Use new Teams client. If an admin sets it to Off, all users in that policy group see the block. Another cause is the Manage apps list. The new Teams client appears as an app called Microsoft Teams (new). If that app is blocked, the client cannot run.

On some machines, a local registry flag can also cause the block. This flag is created by a user or by an older installation. It forces the client to use classic Teams or disables the new client entirely. The registry flag overrides the default behavior even when the admin policy allows the new client.

Understanding the Policy Layers

There are three layers that can block the new Teams client. The first layer is the tenant-wide policy in the Teams admin center. The second layer is the app permission list that controls which Teams apps are available. The third layer is the local registry on the user’s Windows device. You must check all three layers to find the source of the block.

Steps to Diagnose and Fix the Teams App Block

Follow these steps in order. Start with the local checks because they are quick and do not require admin rights. Then move to the admin center if the block persists.

1. Check the exact error message
   Open the new Teams client and read the full error text. Look for words like blocked, policy, or administrator. If the message says Your sign-in was successful but your admin requires you to use classic Teams, the policy is the cause. Write down the exact wording because you may need to share it with your IT team.
2. Verify the Teams client version
   In the new Teams client, select your profile picture at the top right, then choose About. The version number appears. If you see a version starting with 1.7 or higher, you are using the new client. If you cannot open the client at all, check the installed version in Windows Settings > Apps > Installed apps. Look for Microsoft Teams and note whether it says new or classic.
3. Check the local registry flag
   Press Win + R, type regedit, and press Enter. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Teams. Look for a value named IsNewTeamsEnabled. If this value exists and is set to 0, the new client is disabled locally. Right-click the value and select Delete. Close the registry editor and try starting Teams again.
4. Clear the Teams cache
   Close Teams completely. Right-click the Teams icon in the system tray and choose Exit. Press Win + R, type %appdata%\Microsoft\Teams, and press Enter. Delete the contents of this folder. Do not delete the folder itself. Restart Teams and sign in again. This removes any corrupted local data that might cause the block message.
5. Ask your admin to check the Teams client policy
   If the block persists, contact your IT administrator. Ask them to open the Teams admin center and go to Teams > Teams client settings. They must set Use new Teams client to On for your policy group. Changes can take up to 24 hours to apply, so wait before testing again.
6. Ask your admin to verify the app permission
   Your admin should also go to Teams admin center > Teams apps > Manage apps. They must find Microsoft Teams (new) and ensure that Block is not selected. If it is blocked, they should select Allow and save the change.

If You Are the Admin: Change the Policy in the Teams Admin Center

As an admin, you can unblock the new Teams client for all users or for a specific group. Go to Teams admin center > Teams > Teams client settings. Select the policy that applies to your users. Under Use new Teams client, choose On. Then go to Teams apps > Manage apps, search for Microsoft Teams (new), and confirm it is allowed. Save both changes and wait for propagation.

If Teams Still Shows the Block After the Main Fix

Teams Still Says Blocked After Policy Change

Policy changes can take up to 24 hours to reach all clients. If the block persists after that, check the local registry again. Some users have a value named IsTeamsUpgradePolicyEnabled that forces classic Teams. Delete that value as well. Restart the device and try again.

Teams Opens Classic Instead of the New Client

If Teams opens the classic client even after the policy allows the new client, the registry flag may be set to force classic. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Teams and look for IsNewTeamsEnabled. If it is missing, create a new DWORD (32-bit) value with that name and set it to 1. Restart Teams.

Block Message Appears on a Shared Computer

On shared computers, the registry is per user. Each user must have the correct flag. If one user sees the block and another does not, the issue is the local user profile. Clear the cache and delete the registry value for the affected user. If the problem repeats, the computer may have a group policy that overrides the registry. Contact your admin to check the Windows group policy for Teams.

New Teams Client vs Classic Teams: Key Differences

Item	New Teams Client	Classic Teams
App name in admin center	Microsoft Teams (new)	Microsoft Teams
Update frequency	Monthly, automatic	Every few months
Performance	Uses less memory and CPU	Uses more resources
Policy control	Use new Teams client setting	Teams client version policy
Registry flag	IsNewTeamsEnabled	IsTeamsUpgradePolicyEnabled

The new Teams client is faster and receives updates more often. Classic Teams is stable but will eventually be retired. If your organization allows, switch to the new client for better performance.

You can now identify and fix the block on the new Teams client. Start with the local registry and cache, then escalate to your admin if needed. If you are the admin, change the Use new Teams client setting and the app permission. After the fix, test the client by signing in and opening a chat. For a faster experience, enable the new client and disable classic Teams in the policy. Use the Ctrl + Shift + M shortcut to toggle mute during a meeting as a quick check that the client works correctly.