When you change a messaging policy in the Teams admin center, the update normally applies to all assigned users within a few minutes. But sometimes one user keeps the old settings, such as read receipts or chat permissions. This usually happens because the policy assignment is missing, duplicated, or the user has a cached policy that overrides the new one. This article explains why the policy does not update for a single user and walks you through the exact steps to fix it.
You will learn how to check the effective policy, reassign it, and clear the Teams cache on the user’s device. You will also see what to do if the user still sees old settings after the fix. The steps apply to Teams desktop, web, and mobile clients.
Key Takeaways: Fixing a Stuck Teams Messaging Policy for One User
- Teams admin center > Messaging policies > policy name > Manage users: Shows the exact users assigned to a messaging policy and lets you remove or re-add the affected user.
- Teams admin center > Users > Manage users > Policies: Displays the effective messaging policy for the user, which reveals if the assignment is missing or overridden.
- Clear Teams cache (%appdata%\Microsoft\Teams): Removes stale policy data on the user’s device, forcing the client to fetch the latest policy from the server.
Why Teams Messaging Policy Stays Stale for One User
Teams messaging policies control features like chat permissions, read receipts, and the ability to delete messages. When you assign a policy, the Teams backend pushes the settings to the user’s client. The client checks for policy updates periodically, usually every few minutes. If the user does not see the change, one of these three things is wrong:
First, the policy assignment may be missing. You might have edited the policy but never assigned it to the user. Or the user was removed from the policy group by mistake. Second, the user may have a direct policy assignment that overrides the group-based assignment. Teams gives priority to direct assignments over group assignments. Third, the user’s client may have cached the old policy and not refreshed it. This happens when the client is left open for days or when the cache is corrupted.
The fix involves confirming the assignment, forcing a refresh, and clearing the local cache. You do not need to create a new policy.
Steps to Diagnose and Fix the Messaging Policy for One User
Follow these steps in order. Each step checks a different possible cause. Stop when the user’s policy updates correctly.
- Check the effective policy for the user
Sign in to the Teams admin center at admin.teams.microsoft.com. Go to Users > Manage users. Find the affected user and open their profile. Select the Policies tab. Look at Messaging policy. This shows the policy that is actually applied to the user. If it shows a different policy than the one you edited, note the policy name and continue to step 2. - Verify the policy assignment in the messaging policy
In the Teams admin center, go to Messaging policies. Open the policy you edited. Select Manage users. Check if the affected user is listed. If the user is not listed, select Add, search for the user, and add them. If the user is listed, remove them and add them again to reset the assignment. This step fixes missing or duplicated assignments. - Force a policy refresh on the user’s client
Ask the user to sign out of Teams and sign back in. On the desktop client, click the profile picture at the top right, then select Sign out. Close the client completely. After signing back in, the client fetches the latest policy. For the web client, close the browser tab and reopen Teams. For mobile, close the app and reopen it. - Clear the Teams cache on the user’s device
If signing out does not help, clear the local cache. Close Teams completely. On Windows, press Ctrl+Shift+Esc to open Task Manager. End all processes named Teams. Open File Explorer and go to %appdata%\Microsoft\Teams. Delete all files and folders inside this directory. Do not delete the Teams folder itself. Restart Teams and sign in again. The user will have to sign in again, but all settings and chats are stored in the cloud. - Wait for policy propagation
After reassigning the policy, wait up to 30 minutes. Teams policies propagate in batches. If the user still sees old settings after 30 minutes, repeat steps 2 and 4. In rare cases, the policy change may take up to 24 hours to reach all clients.
If Teams Still Shows the Old Messaging Policy
Teams Shows the Old Policy After Clearing the Cache
If the user still sees old settings after clearing the cache, the problem may be a direct policy assignment that overrides the group policy. Go to Users > Manage users > Policies for that user. If the Messaging policy field shows a policy that is not the one you want, select the correct policy from the dropdown and select Apply. This direct assignment takes precedence over any group assignment.
The Policy Applies to Other Users but Not This One
This points to a user-specific issue. Check if the user has a conditional access policy or a security group that blocks policy updates. Go to Azure AD and review the user’s group memberships. Remove the user from any group that has an explicit messaging policy assignment, then re-add them to the correct group. Also check if the user is a guest. Guest users may have different policy defaults.
Read Receipts Still Show for the User
Read receipts are a messaging policy setting called Read receipts. If you disabled read receipts but the user still sees them, the user might have a chat-level override. In Teams, a user can change read receipts for a specific chat. Ask the user to open a chat, select the ellipsis, and uncheck Read receipts. This is a client-side setting that the policy cannot override.
Messaging Policy Assignment Methods: Direct vs Group
| Item | Direct Assignment | Group Assignment |
|---|---|---|
| Where to set | Users > Manage users > Policies | Messaging policies > policy > Manage users |
| Priority | Higher than group assignment | Lower than direct assignment |
| Propagation speed | Usually within minutes | Can take up to 30 minutes |
| Best for | Single user exceptions | Bulk assignments to many users |
Use direct assignment when one user needs a different policy than the rest of the team. Use group assignment when you want to assign the same policy to many users at once. Group assignment requires an Azure AD group. You can create a group in the Microsoft 365 admin center.
Conclusion
You now know how to fix a messaging policy that does not update for one user. Start by checking the effective policy in the Teams admin center, then reassign the policy if needed. Clear the Teams cache on the user’s device to force a refresh. If the problem persists, check for direct assignments or group conflicts. For a quick check, use the Teams admin center > Users > Manage users > Policies tab to confirm the assigned policy. To avoid future issues, make a habit of reviewing policy assignments whenever you change a messaging policy.