Fix Teams Policy Assignment Does Not Apply After Waiting 24 Hours

You changed a Teams policy for a user, waited 24 hours, and the new settings still do not take effect. The most common cause is that the policy assignment is applied to the wrong scope, or the user is not receiving the policy due to a group assignment delay. This article explains why the delay happens and provides a step-by-step fix to force the policy to apply immediately.

You will learn how to verify the effective policy, clear the Teams cache, and use PowerShell to force a policy refresh. The fix works for meeting policies, messaging policies, and app setup policies.

Why Teams Policies Do Not Apply After 24 Hours

Teams policies are stored in Microsoft 365 and replicated to the Teams service. When you assign a policy, the change must propagate to all front-end servers and then to the Teams desktop client. Microsoft documents that policy changes can take up to 24 hours to fully apply, but in practice the delay is usually minutes.

If the policy still does not apply after 24 hours, the cause is almost always one of the following:

• The policy is assigned to a group, but the user is not a member of that group. Group policy assignments can take longer because the group membership must be evaluated.
• The user has a direct policy assignment that overrides the group assignment. Direct assignments always take priority over group assignments.
• The Teams desktop client caches policy data locally. A stale cache can prevent the new policy from loading even after the server has updated.
• The user has not signed out and back in to Teams. Some policies, like app setup policies, require a fresh sign-in to apply.

The fix involves checking the effective policy, clearing the cache, and using PowerShell to force a refresh.

Steps to Force a Teams Policy Assignment to Apply

Follow these steps in order. Each step addresses a common cause of the delay.

Step 1: Verify the Effective Policy Assignment

1. Open the Teams admin center
   Go to Teams admin center > Users > Manage users. Search for the affected user and click on their name.
2. Check the Policies tab
   Click the Policies tab. Look for the policy name you assigned and the Source column. The source shows whether the policy comes from a direct assignment or a group.
3. Compare with the intended policy
   If the source is Group, confirm the user is a member of that group. If the source is Direct, verify that the policy name matches what you set.

Step 2: Clear the Teams Cache

1. Close Teams completely
   Right-click the Teams icon in the system tray and select Quit. This closes the background process.
2. Open the cache folder
   Press Ctrl+R in File Explorer and paste this path: %appdata%\Microsoft\Teams. Press Enter.
3. Delete the cache subfolders
   Delete the Cache, Code Cache, GPUCache, and blob_storage folders. Do not delete the entire Teams folder.
4. Restart Teams
   Start Teams again. Sign in and check if the policy now applies.

Step 3: Force a Policy Refresh with PowerShell

1. Install the Teams PowerShell module
   Open PowerShell as an administrator and run Install-Module MicrosoftTeams -Force.
2. Connect to Teams
   Run Connect-MicrosoftTeams and sign in with an account that has the Teams Administrator role.
3. Check the current policy assignment
   Run Get-CsUserPolicyAssignment -Identity "user@domain.com" -PolicyType "MeetingPolicy". Replace the identity and policy type with your values.
4. Reapply the policy
   Run Grant-CsTeamsMeetingPolicy -Identity "user@domain.com" -PolicyName "YourPolicyName". This forces the policy to be pushed to the user immediately.
5. Verify the change
   Run the Get-CsUserPolicyAssignment command again to confirm the policy name is now correct.

Step 4: Sign Out and Back In

1. Sign out of Teams
   Click your profile picture in Teams and select Sign out. Close the client.
2. Sign back in
   Open Teams and sign in with the same account. This forces the client to fetch the latest policy data.

If Teams Still Has Issues After the Main Fix

If the policy still does not apply after completing the steps above, check for these related issues.

Teams Shows the Old Policy After a Group Assignment Change

Group policy assignments are evaluated every few hours. If you added the user to the group less than 4 hours ago, wait for the next evaluation cycle. To speed it up, use the Grant-CsGroupPolicyAssignment cmdlet with the -Force parameter to reapply the group policy.

Teams Policy Applies on the Web but Not the Desktop Client

The desktop client caches policy data more aggressively than the web version. Clear the cache as described in Step 2 and then sign out and back in. If the issue persists, uninstall Teams and reinstall the latest version.

User Has Multiple Policy Assignments

Direct policy assignments override group assignments. If you assigned a policy directly and also to a group, the direct assignment wins. Remove the direct assignment if you want the group policy to apply. Use the Remove-CsUserPolicyAssignment cmdlet to remove the direct assignment.

Direct vs Group Policy Assignment: Key Differences

Item	Direct Assignment	Group Assignment
How it is set	Applied to individual users via admin center or PowerShell	Applied to a Microsoft 365 group or security group
Propagation speed	Usually applies within minutes	Can take up to 24 hours for group membership evaluation
Priority	Overrides group assignments	Lower priority than direct assignments

Use direct assignments for urgent changes or when you need precise control over a single user. Use group assignments for policy management at scale, and plan for the propagation delay.

You can now force a Teams policy to apply immediately by verifying the effective policy, clearing the cache, and using PowerShell to reapply the assignment. Start with the admin center check, then clear the cache, and finally use the Grant-CsUserPolicyAssignment cmdlet to push the change. For group assignments, remember that the group evaluation cycle can add delay. As an advanced tip, use the Get-CsUserPolicyAssignment cmdlet with the -Effective parameter to see exactly which policy is active for the user.