Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 09:15 UTC Customize Public modeDiscuss ChangeIntel on Discord

Understand and manage dynamic group processing

This page's changes and edits · All guidance changes

Microsoft's edit ·

updating wording

Microsoft's commit message in MicrosoftDocs/entra-docs · commit e551b9c · +8 −8 lines · also on GitHub

⋯ 12 unchanged lines
1313
1414 # Understanding and Managing Dynamic Group Processing in Microsoft Entra ID
1515
16 −Dynamic membership groups in Microsoft Entra are a powerful tool for automating group membership. Changes to membership typically process within a few hours. However, under certain conditions, customers may experience delays in membership updates and processing may take more than 24 hours. Understanding the underlying causes can help admins optimize their configurations and avoid unnecessary processing bottlenecks.
16 +Dynamic membership groups in Microsoft Entra are a powerful tool that allow administrators to automate group membership management. Changes to membership typically process within a few hours. However, under certain conditions, customers can experience delays in membership updates. Processing can take more than 24 hours. Understanding the underlying causes can help admins optimize their configurations and avoid unnecessary processing bottlenecks.
1717
1818 ## How Dynamic Group Processing Works
1919
⋯ 7 unchanged lines
2727
2828 - **Number of object changes**: A high volume of user or device changes can create a long processing queue, extending the time taken to complete processing. Some examples include: changes to extension attributes, device additions or removals, and bulk user updates.
2929
30 −- **Rule configuration**: Certain rule configurations can impact processing time. For instance, the choice of inefficient operators like Match, Contains or MemberOf can increase processing time. Rule complexity is also a contributing factor.
30 +- **Rule configuration**: Certain rule configurations can impact processing time. For instance, the choice of inefficient operators like Match, Contains, or MemberOf can increase processing time. Rule complexity is also a contributing factor.
3131
3232 ## Best Practices to manage dynamic membership groups in your tenant
3333
⋯ 5 unchanged lines
3939
4040 ### **Pause non-essential groups**:
4141
42 −If you anticipate making a large number of changes to group membership (for example – changes to more than 500 groups or making over 20,000 membership changes), pause non-essential groups to improve processing performance.
42 +If you anticipate making a large number of changes to group membership (for example – changes to more than 500 groups or making over 20,000 membership changes), pause nonessential groups to improve processing performance.
4343
4444 #### When to Pause Group Processing:
4545
4646 - Planned large-scale updates: If you anticipate making a large number of changes to group membership (for example – changes to more than 500 groups or making over 20,000 membership changes).
4747
48 −- Unexpected delays: if you notice that group membership has not changed/ you encounter unexpected delays.
48 +- Unexpected delays: if you notice that group membership hasn't changed/ you encounter unexpected delays.
4949
5050 #### How to Pause/resume:
5151
5252 - Use the Pause All Groups script to temporarily halt processing and allow the service to recover before resuming.
5353
54 −- Do not un-pause the groups immediately. We recommend waiting a minimum of 24 hours to allow group processing to catch up and then look at your audit logs to see if they have returned to baseline. If necessary, un-pause groups in phases rather than all at once.
54 +- Don't unpause the groups immediately. We recommend waiting a minimum of 24 hours to allow group processing to catch up and then look at your audit logs to see if they are back to baseline. If necessary, unpause groups in phases rather than all at once.
5555
5656 ### Optimizing Rule Efficiency
5757
58 −- **Avoid the use of the Match operator** in rules as much as possible. Instead use the StartsWith, Equals or EndsWith operators.
58 +- **Avoid the use of the Match operator** in rules as much as possible. Instead use the StartsWith, Equals, or EndsWith operators.
5959
6060 - **Avoid Contains**: Similar to the use of Match, avoid the use of Contains operator in rules as much as possible as it can lead to increased processing time.
6161
6262 - **Use fewer OR operators**: Instead, use the -in operator to group them into a single criterion to make the rules easier to evaluate.
6363
64 −- **Minimize use of MemberOf at this time**: [```memberOf```](groups-dynamic-rule-member-of.md), which is currently in preview, can introduce additional complexity, particularly if a tenant has a large number of groups or frequent updates. Avoid using this operator if possible as it comes with bugs and limitations. The recommendation is to delete existing MemberOf groups in your tenant: Learn More
64 +- **Minimize use of MemberOf at this time**: [```memberOf```](groups-dynamic-rule-member-of.md), which is currently in preview, can introduce more complexity, particularly if a tenant has a large number of groups or frequent updates. Avoid using this operator if possible as it comes with bugs and limitations. The recommendation is to delete existing MemberOf groups in your tenant: Learn More
6565
6666 >[!NOTE]
6767 > Learn more about creating efficient rules here: [](groups-dynamic-rule-more-efficient.md)
⋯ 2 unchanged lines
7070
7171 ## Additional Troubleshooting Resources
7272
73 −Delays in dynamic group processing primarily happen due to high volumes of changes and large numbers of groups. By following best practices—such as optimizing rule efficiency, monitoring changes, and pausing non-essential groups when needed—IT administrators can improve processing performance and avoid unnecessary delays.
73 +Delays in dynamic group processing primarily happen due to high volumes of changes and large numbers of groups. By following best practices—such as optimizing rule efficiency, monitoring changes, and pausing nonessential groups when needed—IT administrators can improve processing performance and avoid unnecessary delays.
7474
7575 >[!NOTE]
7676 > Review detailed information on pausing group processing in [Troubleshoot dynamic group processing](/troubleshoot/entra/entra-id/dir-dmns-obj/troubleshoot-dynamic-groups.md)

Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy today 06:21 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 09:15 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current