Fix Teams Policy Assignment Does Not Apply in a New Tenant

When you create a new Microsoft Teams tenant and assign policies to users, the settings sometimes do not take effect. Users might still see the default global policy, or the meeting recording and chat features you configured remain inactive. This happens because policy assignments have a propagation delay and because the Teams admin center can display stale information. This article explains why the policy does not apply and provides the exact steps to force the assignment and verify it.

The root cause is usually a combination of the Teams policy propagation time and the way the admin center caches assignment data. In a new tenant, the policy service may take up to 24 hours to fully synchronize. You can speed up the process by using PowerShell to assign the policy directly and by clearing the Teams client cache on the user’s device.

Why Teams Policy Assignment Does Not Apply in a New Tenant

When you assign a policy in the Teams admin center, the change is written to the Microsoft 365 policy service. This service then pushes the policy to the Teams client on each user’s device. In a new tenant, the policy service may not have completed its initial synchronization with all backend databases. This is why the policy assignment appears in the admin center but does not affect the user’s Teams app.

Another factor is the Teams client cache. The Teams desktop app stores a local copy of the policy settings. If the cache is not refreshed, the client continues to use the old default policy even after the server-side assignment is correct. The cache is stored in the user’s AppData folder and is refreshed when the app restarts, but sometimes it requires a manual clear.

Finally, the admin center itself can display stale data. The policy assignment page may not refresh immediately after you make a change. You can force a refresh by signing out and signing back in to the admin center, or by using PowerShell to query the effective policy.

Steps to Diagnose and Fix Teams Policy Assignment in a New Tenant

Step 1: Verify the Policy Assignment in the Admin Center

1. Open the Teams admin center
   Sign in to admin.teams.microsoft.com with your Global Admin or Teams Admin credentials.
2. Go to Users
   In the left navigation, select Users, then select Manage users.
3. Select the affected user
   Click on the user’s display name to open the user detail page.
4. Review the Policies tab
   Scroll to the Policies section and check the assigned policy names. If the policy you set is not listed, the assignment did not save.

Step 2: Force the Policy Assignment with PowerShell

PowerShell gives you a direct connection to the policy service and bypasses the admin center delay. You need the Microsoft Teams PowerShell module installed.

1. Install the Teams PowerShell module
   Open Windows PowerShell as an administrator and run: Install-Module -Name MicrosoftTeams -Force -AllowClobber
2. Connect to Teams
   Run Connect-MicrosoftTeams and sign in with your admin credentials.
3. Assign the policy
   Run Grant-CsTeamsMeetingPolicy -Identity “user@contoso.com” -PolicyName “YourPolicyName” to assign the meeting policy immediately.
4. Verify the assignment
   Run Get-CsUserPolicyAssignment -Identity “user@contoso.com” | Format-List to confirm the policy is now effective.

Step 3: Clear the Teams Client Cache

1. Close Teams completely
   Right-click the Teams icon in the system tray and select Quit. Also end any Teams processes in Task Manager.
2. Open the cache folder
   Press Win + R, type %appdata%\Microsoft\Teams, and press Enter.
3. Delete the cache contents
   Select all files and folders inside the Teams folder and delete them. Do not delete the folder itself.
4. Restart Teams
   Start Teams again and sign in. The app will download the fresh policy from the server.

Step 4: Use the Teams Admin Center Policy Refresh

1. Sign out of the admin center
   Click your profile picture in the top right and select Sign out.
2. Sign back in
   Wait for 30 seconds, then sign in again to force a fresh session.
3. Re-check the user’s policy
   Navigate to Users > Manage users and open the user to see if the policy now appears.

If Teams Still Has Issues After the Main Fix

Teams Client Shows the Default Policy Instead of the Assigned One

If the client still shows the Global (Org-wide default) policy, the user may not have signed out and back in after the cache clear. Ask the user to sign out of Teams completely, then sign in again. If the problem persists, check the policy assignment in PowerShell with Get-CsUserPolicyAssignment. If the output shows the assigned policy but the client does not reflect it, the issue is the client cache.

Policy Assignment Appears in Admin Center but Not in PowerShell

This indicates the admin center saved the assignment but the policy service did not process it. Run Grant-CsTeamsMeetingPolicy again with the exact policy name. If the cmdlet returns an error, the policy name may be incorrect. Use Get-CsTeamsMeetingPolicy to list all available policies and copy the exact name.

Changes Take Longer Than 24 Hours

In rare cases, the policy service may be stuck. Create a new policy that matches your desired settings, assign it to the user, and then delete the old policy. This forces a fresh assignment path. Also verify that the user has an active Teams license, because policy assignments do not propagate to unlicensed users.

Teams Admin Center vs PowerShell for Policy Assignment: Key Differences

Item	Teams Admin Center	PowerShell
Assignment speed	May take up to 24 hours	Immediate
Bulk assignment	Manual per user or via CSV	Supports batch scripts
Verification	Shows effective policy	Shows raw assignment data
Error messages	Often generic	Detailed and actionable

Now you can force a Teams policy assignment in a new tenant using PowerShell and clear the client cache. Start by verifying the assignment in the admin center, then use the Grant-CsTeamsMeetingPolicy cmdlet to apply it instantly. For a long-term fix, consider using the Teams admin center to create a batch policy assignment for all new users. As an advanced tip, use Get-CsEffectivePolicy to see exactly which policy settings the user’s client is receiving.