Fix Teams Policy Assignment Does Not Apply for One User

You assigned a Teams policy to one user in the Teams admin center, but the user still behaves as if the policy is not active. The user can see the policy in their assigned list, yet changes like meeting recording or chat restrictions do not take effect. This usually happens because the effective policy comes from a different source or the policy assignment has not propagated. This article explains the root causes and gives you a step-by-step method to verify and fix a policy assignment for a single user.

Why Teams Ignores a Policy Assignment for One User

Teams policies are assigned at three levels: global, group, and direct user assignment. The effective policy is determined by the highest priority. If a group policy is assigned to the user’s group and the group policy has a higher priority than the direct assignment, the group policy wins. Another cause is that the policy assignment was made but not yet propagated. Propagation can take up to 24 hours, but usually it finishes within a few minutes. A third cause is that the user has a policy assignment in the Teams admin center that is marked as “Group” instead of “Direct”.

When you assign a policy directly to a user, the assignment type appears as “Direct” in the user’s policy list. If it appears as “Group”, the user inherits the policy from a group. You must check the effective policy for that user to see which policy is actually applied. The Teams admin center provides a dedicated view for this purpose.

Another common cause is that the policy assignment exists but the user is not signed out and back in. Some policy changes, such as meeting policies, require a restart of the Teams client. The user may need to close Teams completely and sign in again. This is not a technical failure but a client refresh issue.

Steps to Diagnose and Fix a Single-User Policy Assignment

Follow these steps in order. Stop when the issue is resolved.

Step 1: Check the Effective Policy in the Teams Admin Center

1. Open the Teams admin center
   Go to Teams admin center and sign in with an account that has Teams administrator permissions.
2. Go to the user’s policy list
   Select Users and then Manage users. Find the user in the list and click the user’s display name.
3. Open the Policies tab
   In the user’s profile, select the Policies tab. This shows every policy type and the assigned policy for each.
4. Check the assignment type
   Look for the policy type you changed, such as Meeting policy. The column Source shows whether it is Direct or Group. If it says Group, a group policy overrides your direct assignment.

Step 2: Assign the Policy Directly to the User

1. Open the policy type
   In the Teams admin center, go to the specific policy section, for example Meetings and then Meeting policies.
2. Select the policy
   Click the policy name you want to assign.
3. Open Manage users
   In the policy pane, select the Manage users tab.
4. Add the user
   Click Add, search for the user, and select them. Click Add again and then Apply.

Step 3: Use PowerShell to Force the Assignment

1. Connect to Teams PowerShell
   Open Windows PowerShell as an administrator and run Connect-MicrosoftTeams. Sign in with the same admin account.
2. Verify the current assignment
   Run Get-CsUserPolicyAssignment -Identity "user@domain.com" to see the effective policy and its source.
3. Force the direct assignment
   Run Grant-CsTeamsMeetingPolicy -Identity "user@domain.com" -PolicyName "YourPolicyName". Replace YourPolicyName with the actual policy name.

Step 4: Sign Out and Sign In the User

1. Close Teams completely
   Right-click the Teams icon in the system tray and select Quit. Do not just close the window.
2. Sign out
   Open Teams again and sign out from the account. Close Teams again.
3. Sign in
   Sign in with the user’s credentials. Test the policy behavior, such as starting a meeting to see if recording is allowed.

If Teams Still Has Issues After the Main Fix

Teams Shows the Policy as Assigned But the User Sees Old Behavior

If the policy is correctly assigned as Direct and the user signed out and back in, the issue may be client caching. Ask the user to clear the Teams cache. Close Teams, then delete the folder %appdata%\Microsoft\Teams. Restart Teams and sign in again. This forces the client to refetch all policy settings.

Policy Applies to Some Features But Not Others

Teams policies are granular. A meeting policy controls recording, transcription, and lobby settings separately. If one feature, such as transcription, still does not work, check the specific setting inside the policy. Open the policy in the Teams admin center and verify that the setting you expect is enabled. Also check if a more restrictive policy is applied through a group assignment.

Group Policy Overrides Your Direct Assignment

When a group policy has a higher priority than a direct assignment, the group policy wins. To fix this, either change the priority of the group policy or remove the user from that group. In the Teams admin center, go to the policy type, open the group policy, and select Manage groups. Remove the user from the group. Then reassign the direct policy.

Direct Policy vs Group Policy vs Global Policy: What Changes for the User

Item	Direct Policy	Group Policy	Global Policy
Priority	Highest	Middle	Lowest
Assignment method	Per user in the Teams admin center or PowerShell	Assigned to a group, applies to all members	Applies to all users with no explicit assignment
Propagation time	Minutes, but can take up to 24 hours	Same as direct	Same as direct
Best for	One-off exceptions for a single user	Consistent settings for a department or role	Baseline settings for the whole organization

You can now verify the effective policy for any user, assign a policy directly to override group settings, and use PowerShell to force an immediate update. If the problem persists, clear the Teams cache or check the group membership. For advanced control, use PowerShell to script policy assignments for multiple users at once.