Understand and manage dynamic group processing
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 56cea96 · +5 −1 lines · also on GitHub
⋯ 3 unchanged lines
44
ms.topic: concept-article
55
ms.date: 04/08/2025
66
ms.reviewer: mbhargava
7
+ai-usage: ai-assisted
78
---
89
910
# Understand and manage dynamic group processing in Microsoft Entra ID
⋯ 17 unchanged lines
2728
2829
- **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.
2930
30
−- **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`, `Contains`, or `memberOf` can increase processing time. Rule complexity is also a contributing factor.
32
+
33
+> [!NOTE]
34
+> 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.
3135
3236
## Best practices for dynamic membership groups in your tenant
3337
⋯ 37 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 today 06:21 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.