Skip to content

Commit b78f256

Browse files
authored
Merge pull request MicrosoftDocs#8606 from bjwhalen/patch-79
Update New-CsGroupPolicyAssignment.md
2 parents 4e7111e + c2768ca commit b78f256

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

teams/teams-ps/teams/New-CsGroupPolicyAssignment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The group policy assignment rank is set at the time a policy is assigned to a gr
2828

2929
Once a group policy assignment is created, the policy assignment will be propagated to the members of the group, including users that are added to the group after the assignment was created. Propagation time of the initial policy assignments to members of the group varies based on the number of users in the group. Propagation time for subsequent group membership changes also varies based on the number of users being added or removed from the group. For large groups, propagation to all members may take 24 hours or more. When using group policy assignment, the recommended maximum group membership size is 50,000 users per group.
3030

31-
> [!NOTES]
31+
> [!NOTE]
3232
> - Group policy assignment support is available only for the following policy types:
3333
TeamsAppSetupPolicy (App Setup policies), TeamsCallingPolicy (Calling policies), TeamsCallParkPolicy (Call park policies), TeamsChannelsPolicy, TeamsComplianceRecordingPolicy, TenantDialPlan, TeamsEducationAssignmentsAppPolicy, TeamsMeetingBroadcastPolicy (Live Events policies), TeamsMeetingPolicy (Meeting policies), TeamsMessagingPolicy (Messaging policies), TeamsShiftsPolicy, TeamsUpdateManagementPolicy.
3434
> - A given policy type can be assigned to at most 64 groups, across policy instances for that type.

0 commit comments

Comments
 (0)