M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions→ m365con.net

Blog · Mirko Peters

Teams Group Policy Assignment Not Applying: Why Members Still Get the Global Policy

By ·

You assigned a Teams policy to a group, but members keep the default policy? Check the effective policy with the right cmdlet, then direct assignments, rank, nested groups and policy type.

You created a custom Teams policy and assigned it to a security group. A day later, the members still have the default policy. Assigning the same policy to single users works. This is a recurring pattern in Microsoft Q&A threads, including one from January 2026 about a custom Audio Conferencing policy for about 200 licensed users. This article follows Microsoft's own rules for group policy assignment and uses the threads as the scenario. It is a troubleshooting guide, not an official Microsoft procedure. None of the threads below has a confirmed fix, so the value here is in the order of the checks.

Key points

  • Get-CsOnlineUser shows only direct policy assignments. A blank value there does not prove that a group assignment failed. Use Get-CsUserPolicyAssignment to see the effective policy.
  • A policy assigned directly to a user always beats a group assignment of the same type. Remove the direct assignment so the group policy can apply.
  • Group assignments reach only direct members of the group, not members of nested groups, and propagation runs in the background and can take 24 hours or more for large groups.
  • Not every policy type supports group assignment. Check the Learn lists before you build a design around it.

What the threads describe

  • January 2026: an administrator assigned a custom Audio Conferencing policy to a group of about 200 users. The activity log showed propagation as done, but meetings still showed only the default dial-in number. A moderator suggested checking for direct assignments, assigning per user, or contacting support. The administrator answered that users had no direct assignment and fell back to the Global policy, that a partner would have to contact Microsoft, and that per-user batch assignment was the workaround for now. Nothing was confirmed as the cause.
  • May 2024 (locked thread): a Compliance Recording policy assigned to a group with New-CsGroupPolicyAssignment and rank 1 never reached the members, although Get-CsGroupPolicyAssignment showed the assignment. The single answer talked about on-premises Active Directory and Windows Group Policy tools, which look unrelated to a Teams policy assignment made with PowerShell. No accepted answer.
  • August 2024: an administrator assigned an External Access policy to a group with a rank of 5, then checked the user with Get-CsOnlineUser | Select-Object ExternalAccessPolicy and saw a blank value. The moderator's answer, accepted by the asker, suggested checking the policy list, the group membership and waiting for replication.
  • A 2020 thread (older, but the same pattern): a custom meeting policy assigned to a security group did not reach members, who kept the Global (Org-wide default) meeting policy. The person who asked wrote that removing the Global policy from the users made them inherit the group's policy, and marked their own reply as the accepted answer. A responder had pointed to the Learn section on removing a directly assigned policy.

Step 1: Check the effective policy with the right cmdlet

Start here, because the most common check is the misleading one. The Microsoft reference for New-CsGroupPolicyAssignment says that Get-CsOnlineUser shows only direct assignments and does not show the effect of group policy assignments. A blank value there is therefore expected for a user who gets the policy from a group. This is consistent with the August 2024 thread, though that thread never states it.

Use Get-CsUserPolicyAssignment instead. The reference says it returns the effective policy for each policy type, whether direct or from a group:

``powershell Get-CsUserPolicyAssignment -Identity <user> -PolicyType TeamsMeetingPolicy | select -ExpandProperty PolicySource ``

The output lists an AssignmentType of Direct or Group, the policy name and, for groups, the group ID. Replace TeamsMeetingPolicy with the type you assigned. If the policy type does not appear at all, Microsoft says the user gets the tenant global default.

Step 2: Look for a direct assignment

Microsoft's page on assigning policies to users and groups is clear: a policy assigned directly to a user takes precedence over any policy of the same type assigned to a group, and you must remove the direct policy before the user can inherit from a group.

Typical sources of direct assignments are earlier per-user assignments, scripts, or batch operations. A batch assignment is also a direct assignment. This matters if you use the per-user workaround from the January 2026 thread: those users will keep that policy even after a group assignment is in place, until you remove it.

To remove a direct assignment:

``powershell Grant-CsTeamsMeetingPolicy -Identity <user> -PolicyName $null ``

Use the Grant- cmdlet that matches your policy type. Microsoft's page shows the -PolicyName $null pattern with other policy types (for example Grant-CsTeamsMeetingBroadcastPolicy), so check the cmdlet reference for yours. In the Teams admin center, open Users, then Manage users, select the user, open the Policies tab, select the policy and choose Remove. For many users, Microsoft shows Actions, Unassign policies in bulk, but warns that choosing a policy there removes all individually assigned users from that policy.

Step 3: Verify the group assignment and its rank

List what is assigned to the group, or all assignments of one type:

``powershell Get-CsGroupPolicyAssignment -GroupId <group-id> Get-CsGroupPolicyAssignment -PolicyType TeamsMeetingPolicy ``

If the user is in several groups that have a policy of the same type, the best rank wins. Microsoft says rank 1 is the highest, that a missing rank is treated as the lowest, and that the New-CsGroupPolicyAssignment reference treats a direct assignment like rank 0. So a group at rank 5 loses against a group at rank 1 that also contains the user. In the admin center, to change a rank you first remove the group assignment and add it again with the new rank.

The reference also says that New-CsGroupPolicyAssignment will be deprecated. Going forward, use the Grant-Cs...Policy cmdlet for your type with -Group and -Rank:

``powershell Grant-CsTeamsMeetingPolicy -Group <group-id> -PolicyName "<policy>" -Rank 1 ``

The Learn page on assigning policies shows this form. For the Audio Conferencing policy in the January 2026 thread, the Grant-CsTeamsAudioConferencingPolicy reference lists -Group and -Rank too.

Step 4: Check the group itself

Microsoft names several conditions:

  • Assignments are propagated only to users who are direct members. They are not propagated to members of nested groups.
  • Groups with HiddenGroupMembership enabled cannot be used. Class teams have this enabled by default.
  • The reference says a policy can be assigned to a Microsoft 365 group, a security group or a distribution list.
  • A policy type can be assigned to at most 64 groups across policy instances of that type. Microsoft recommends up to 50,000 users per group.

If users sit in a nested group, add them to the assigned group directly or assign the policy to the nested group as well.

Step 5: Check that the policy type supports groups

Microsoft's lists do not fully agree, so check both. The page on assigning policies says group assignment is not supported for the Teams App Permission policy, the Teams Upgrade policy and the Dialout policy. The New-CsGroupPolicyAssignment reference says that since May 2023 all policy types are supported except App Permission, Network Roaming, Emergency Call Routing, Voice Applications and Upgrade. The pages are not identical, and the cmdlet page may be the more current one for the PowerShell module. If your type appears on either list, plan for direct assignment or a different method.

Step 6: Wait, but know what you are waiting for

Microsoft says the policy is assigned to the group immediately, while passing it on to members is a background job whose length depends on the group size. The cmdlet reference says that for large groups it may take 24 hours or more. A moderator in the August 2024 thread talked about a few minutes, which fits only small groups. In the January 2026 thread, the policy was assigned on a Friday and the activity log showed propagation as complete by Monday, so waiting alone does not look like the cause there.

Re-check the effective policy of one test user after any change. Effective policies are recalculated when a user is added to or removed from the group, when a policy is unassigned from the group or when a direct assignment is removed.

What this does not solve

In the January 2026 case, the administrator had no direct assignments and still did not see the new dial-in numbers. Microsoft's pages do not explain that. Also, whether a specific meeting invitation shows the new numbers depends on more than the policy assignment, and I did not verify that. If Get-CsUserPolicyAssignment shows the group policy as effective for the user and the behavior is still wrong, the policy assignment is working and the question moves to the feature. Open a support case with the output of Get-CsUserPolicyAssignment, the group ID and the time of the assignment.

Quick checklist

  1. Run Get-CsUserPolicyAssignment for one affected user and read PolicySource.
  2. Remove direct assignments of the same policy type.
  3. Run Get-CsGroupPolicyAssignment and check the rank.
  4. Confirm the user is a direct member of the group.
  5. Confirm that the policy type supports group assignment.
  6. Allow time for large groups and re-check.

Related

Sources

Entities in this article

Microsoft Teams Microsoft Teams admin center PowerShell

Related articles

RSS