Fix Teams Meeting Policy Is Missing After Waiting 24 Hours

When you assign a meeting policy in the Teams admin center, the change should apply within a few hours. Some administrators report that the policy is still missing after waiting 24 hours. This article explains why the policy does not appear and how to force the update.

The delay usually comes from the Teams policy propagation service, which syncs changes in batches. If the sync fails or the policy assignment is incorrect, the update never reaches the user. You will learn the exact steps to verify the assignment, force a sync, and confirm the policy is active.

Why Teams Meeting Policy Is Missing After 24 Hours

Teams meeting policies are stored in the Microsoft 365 cloud and applied to users through a background synchronization process. This process runs every few hours, but it can be delayed by several factors.

The most common cause is that the policy assignment was made to a security group, not directly to the user. Group-based policy assignment can take up to 24 hours to propagate. If you assigned the policy directly but still see it missing, the policy may have been created in the wrong tenant or the user may be in a different licensing state.

Another cause is cached credentials in the Teams desktop client. The client stores policy information locally and refreshes it only on sign-in or when the app restarts. If the user has not signed out and back in, the old policy remains active.

Finally, a misconfigured policy assignment can block the update. For example, if the policy is set to “Global (Org-wide default)” but you assigned a custom policy to the user, the custom policy may not apply if the user is in a different policy hierarchy.

Steps to Force the Teams Meeting Policy to Apply

Verify the Policy Exists and Is Assigned

1. Sign in to the Teams admin center
   Open a browser and go to admin.teams.microsoft.com. Use an account with Global Admin or Teams Administrator permissions.
2. Open Meeting policies
   In the left navigation, go to Meetings > Meeting policies. Confirm the policy you created is listed. If it is not, create it again.
3. Check the policy assignment
   Select the policy name, then click Manage users. Verify the affected user is in the list. If not, click Add, search for the user, and assign the policy.
4. Confirm the user’s effective policy
   Go to Users > Manage users, select the user, and click Policies. Look for the meeting policy column. If it shows a different policy, the assignment is wrong.

Force a Policy Sync From the Client

1. Sign out of Teams
   In the Teams desktop client, click your profile picture at the top right, then choose Sign out. Wait for the sign-out to complete.
2. Clear the Teams cache
   Press Ctrl + Alt + Delete and open Task Manager. End all processes named Teams. Then open File Explorer and navigate to %appdata%\Microsoft\Teams. Delete the contents of the Cache, Code Cache, and GPUCache folders. Do not delete the whole Teams folder.
3. Sign back in
   Open Teams again and sign in with the affected user’s account. The client will fetch the latest policy assignments.
4. Restart Teams completely
   After signing in, close Teams fully. Use Task Manager to ensure no Teams process runs. Then reopen Teams.

Use PowerShell to Force the Policy Assignment

1. Install the Teams PowerShell module
   Open PowerShell as an administrator and run Install-Module -Name MicrosoftTeams -Force.
2. Connect to Teams
   Run Connect-MicrosoftTeams and sign in with an admin account.
3. Reapply the policy
   Run Set-CsUser -Identity "user@domain.com" -PolicyAssignment "MeetingPolicyName". Replace the user and policy names with your values.
4. Check the assignment
   Run Get-CsUserPolicyAssignment -Identity "user@domain.com" -PolicyType MeetingPolicy. This shows the effective policy and the assignment source.

If Teams Still Has Issues After the Main Fix

Teams Still Shows the Old Meeting Policy

If the policy still does not apply, the user’s Teams client may be running an outdated version. Go to Settings > About in the Teams client and check the version number. If it is below the latest release, update Teams manually by downloading the installer from the Microsoft 365 admin center.

Also, verify the user is not in a pilot or preview ring that uses a different policy set. Check Teams admin center > Teams > Teams update policies to see the update ring assigned to the user.

Policy Is Missing for a Group-Assigned User

If you assigned the policy to a security group, the propagation can take up to 24 hours. After that, sign out and sign back in to the Teams client. If the policy still does not appear, remove the group assignment and assign the policy directly to the user. Direct assignment takes effect faster and is easier to troubleshoot.

Teams Meeting Policy Missing in the Admin Center

If the policy itself is missing from the admin center, it may have been deleted accidentally. Check the audit log in the Microsoft 365 compliance center. Search for Delete meeting policy events. If you find one, recreate the policy with the same settings.

New Teams Desktop vs Teams on the Web: Policy Refresh Differences

Item	Teams Desktop Client	Teams on the Web
Policy refresh trigger	Sign-in or app restart	Browser refresh
Cache behavior	Stores policy locally	No local cache
Best for testing	After clearing cache	Immediate check

Use Teams on the web to verify the policy change quickly, because it does not cache policy data. Open the web app, sign in, and join a meeting to test the policy settings. If the web app shows the correct policy but the desktop client does not, the cache is the problem.

After following these steps, you can verify the policy is applied by checking the user’s effective policy in the admin center or by testing a meeting feature. To confirm the policy works, create a test meeting and check the meeting options. For advanced control, use PowerShell to export all policy assignments and review them in a spreadsheet.