Understand and manage dynamic group processing
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 61ed281 · +3 −3 lines · also on GitHub
⋯ 1 unchanged line
22
title: Understand and manage dynamic group processing in Microsoft Entra ID
33
description: Learn how dynamic group management works.
44
ms.topic: concept-article
5
−ms.date: 04/08/2025
5
+ms.date: 11/16/2026
66
ms.reviewer: mbhargava
77
ai-usage: ai-assisted
88
---
⋯ 19 unchanged lines
2828
2929
- **Number of object changes**: A high volume of user or device changes can create a long processing queue and extend the processing time. Examples include changes to extension attributes, device additions or removals, and bulk user updates.
3030
31
−- **Rule configuration**: Certain rule configurations can affect 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.
31
+- **Rule configuration**: Certain rule configurations can affect processing time. For instance, the choice of inefficient operators like `Match` or `Contains` can increase processing time. Rule complexity is also a contributing factor.
3232
3333
> [!NOTE]
3434
> Stale devices and inactive user accounts can remain in scope for dynamic membership rules and can be added to groups when they satisfy the rule conditions. Review and clean up [stale devices](/entra/identity/devices/manage-stale-devices) and [inactive users](/entra/identity/monitoring-health/howto-manage-inactive-user-accounts) so your dynamic groups include only the objects you intend to manage.
⋯ 25 unchanged lines
6060
6161
- Use fewer `-or` operators. Instead, use the `-in` operator to group rules into a single criterion. Grouping rules makes them easier to evaluate.
6262
63
−- Avoid the use of the [`memberOf`](groups-dynamic-rule-member-of.md) operator if possible. It's currently in preview, and it comes with bugs and limitations. It can also introduce more complexity, particularly if a tenant has a large number of groups or frequent updates. The recommendation is to delete existing `memberOf` groups in your tenant.
63
+- The earlier [`memberOf` preview](groups-dynamic-rule-member-of.md) was deprecated because it could slow dynamic membership processing for the tenant. MemberOf Next uses separate processing on a twice-daily schedule. For requirements and migration guidance, see [Move existing MemberOf groups to MemberOf Next](groups-dynamic-rule-advanced.md#move-existing-memberof-groups-to-memberof-next).
6464
6565
For more help with optimizing dynamic group processing, review [Create simpler, more efficient rules for dynamic membership groups in Microsoft Entra ID](groups-dynamic-rule-more-efficient.md).
6666
⋯ 8 unchanged lines
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 18 Nov 10:22 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.