Fix Teams Sensitivity Label Does Not Appear after a Compliance Policy Change

When you apply a new sensitivity label through a compliance policy, the label may not show up in Teams. Users see the default label or no label at all, even though the policy appears active in the Microsoft Purview compliance portal. This usually happens because Teams caches label information or because the policy targets the wrong scope. This article explains why the label disappears and gives you the exact steps to force Teams to refresh and apply the correct sensitivity label.

You will learn how to verify the policy configuration, clear the Teams cache, and confirm that the label reaches the desktop, web, and mobile clients. We also cover common mistakes like assigning labels to groups instead of Teams and forgetting to publish the label. By the end, you will have a reliable method to make sensitivity labels appear consistently after any compliance policy change.

Why Teams Does Not Show the Sensitivity Label After a Policy Change

Sensitivity labels in Teams come from Microsoft Purview Information Protection. When you change a label or publish a new one, the change goes to the Microsoft 365 backend. Teams clients do not poll for label updates constantly. Instead, they cache the label set at startup and refresh it periodically. If the cache is stale, the new label stays invisible.

Another common cause is the label scope. A sensitivity label can be scoped to files, emails, meetings, or Teams. If you create a label for files only, Teams will never show it. The label must have the “Teams” scope enabled in the label settings. Also, the label must be part of a published label policy that includes the target users or groups.

Lastly, the order of the labels matters. If the new label is lower in the priority list, Teams may still show the previous default label. The default label is set in the label policy, not in the label itself. After a policy change, any user who already has a Teams session open will not see the update until they sign out and sign back in.

How Label Scoping Works in Teams

When you create a sensitivity label in Microsoft Purview, you choose the scope. For Teams, the scope must include “Teams” under the “Items” section. You can also select “Groups & sites” if you want the label to apply to teams or group settings. If you only select “Files” or “Emails”, Teams will ignore the label entirely.

The label policy then determines which users see the label. If the policy excludes the user group, the label will not appear. Also, the policy must be published to the same tenant. If you have multiple policies, the one with the highest priority wins. You can see the priority in the policy list.

Steps to Force Teams to Display the New Sensitivity Label

Follow these steps in order. Do not skip the cache clearing step, because that is the most common fix.

1. Verify the label scope in Microsoft Purview
   Go to the Microsoft Purview compliance portal. Select Information protection, then Labels. Find your label and open its settings. Under “Scope”, ensure that “Teams” is checked. Also confirm that “Groups & sites” is checked if you want the label to apply to team containers. If the scope is wrong, edit the label and save it.
2. Check the label policy publication
   In the same portal, select Label policies. Verify that your label is included in a policy that applies to the affected users. Check the “Published labels” list and the “Users and groups” assignment. If the policy does not include the users, add them or create a new policy. Also check the “Default label” setting. If you want the new label to be the default, set it here.
3. Sign out of Teams and close the app
   In the Teams desktop app, click your profile picture at the top right. Select Sign out. Then close the Teams window completely. Right-click the Teams icon in the system tray and choose Exit. This ensures no background process keeps the old cache.
4. Clear the Teams cache folders
   Press Ctrl+R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter. In the Teams folder, delete the contents of the Cache, GPUCache, Code Cache, and Local Storage subfolders. Do not delete the entire Teams folder, because that removes your signed-in profile. After deleting, reopen Teams and sign in again.
5. Restart Teams and check the label
   Launch Teams from the Start menu or desktop icon. Sign in with the affected account. Open a team channel and click the ellipsis next to the team name. Select “Sensitivity” or “Manage label” depending on your Teams version. The new label should now appear in the list. If not, proceed to the next step.
6. Use PowerShell to force a label refresh
   Open PowerShell as an administrator. Connect to Teams with the command Connect-MicrosoftTeams. Then run the command Get-Team -User | Set-Team -SensitivityLabelId . You can find the label ID in the Microsoft Purview portal under the label’s properties. This command directly applies the label to the team and bypasses the cache.
7. Test on the web client
   Open Teams in a browser at teams.microsoft.com. Sign in with the same account. Check if the label appears there. If it does, the issue is specific to the desktop client. If it does not, the policy or scope is still wrong. Recheck steps 1 and 2.

What to Do If the Label Still Does Not Appear

If the label is still missing after clearing the cache and applying it via PowerShell, the problem may be with the label policy propagation. Microsoft 365 can take up to 24 hours to propagate label changes to all clients. Wait a few hours and repeat the cache clearing. Also, verify that the user has the correct license. Sensitivity labels require an Azure AD Premium P1 or P2 license, or a Microsoft 365 E3 or E5 license.

If Teams Still Has Issues After the Main Fix

Teams shows the old label even after clearing the cache

This happens when the label policy has a default label that is still the old one. Go to Microsoft Purview > Label policies, open the policy, and change the “Default label for Teams” to the new label. Then repeat the cache clearing steps. Also, check that the new label is not below the old label in the priority list. If it is, move it up by editing the policy.

The label appears but cannot be applied to a team

If you can see the label in the list but selecting it gives an error, the label may be restricted to certain team types. For example, a label scoped to “Groups & sites” only works on team containers, not on channels. Also, the label may require a justification when changing from a higher classification to a lower one. Check the label’s settings for “Justification required” and enable it if needed.

Label is missing on the mobile app

The mobile Teams app does not show sensitivity labels in the same way as the desktop. Labels appear only when you view team settings or when you share a file. If the label is missing on mobile, update the app to the latest version. Also, the mobile app uses the same backend, so if the label appears on the web, it will eventually appear on mobile after a refresh.

Teams Desktop vs Teams on the Web: Label Behavior Comparison

Item	Teams Desktop	Teams on the Web
Cache refresh	Requires manual cache clearing or sign-out	Refreshes on browser reload
Label visibility	Shows label in team settings and file sharing	Shows label in team settings only
PowerShell application	Works with Set-Team cmdlet	Works with Set-Team cmdlet, no cache issue
Default label setting	Read from policy at sign-in	Read from policy at page load
Update delay	Up to 24 hours if cache persists	Immediate after browser refresh

The desktop client caches label data aggressively, so policy changes often require a manual refresh. The web client is more responsive because it loads the label set fresh with each session. Use the web client as a quick diagnostic tool to confirm that the policy is correct before troubleshooting the desktop cache.

Now you can force Teams to show the new sensitivity label after any compliance policy change. Start by verifying the label scope and policy publication, then clear the desktop cache. Use the PowerShell command Set-Team to apply the label directly if the cache step fails. Test on the web client to isolate the issue. If the label still does not appear, wait up to 24 hours for propagation and recheck your license requirements. For advanced control, explore the Get-Team cmdlet to audit which labels are currently applied to your teams.