Skip to content

Update dynamic group processing considerations#1986

Open
mbhargav9 wants to merge 2 commits into
MicrosoftDocs:mainfrom
mbhargav9:patch-3
Open

Update dynamic group processing considerations#1986
mbhargav9 wants to merge 2 commits into
MicrosoftDocs:mainfrom
mbhargav9:patch-3

Conversation

@mbhargav9
Copy link
Copy Markdown
Contributor

Added note about the impact of stale devices and users on dynamic group processing.

Added note about the impact of stale devices and users on dynamic group processing.
@prmerger-automator
Copy link
Copy Markdown
Contributor

@mbhargav9 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@v-dirichards
Copy link
Copy Markdown
Contributor

Hi @mbhargav9 - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!


@kenwith

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 6107044:

✅ Validation status: passed

File Status Preview URL Details
docs/identity/users/manage-dynamic-group.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds guidance to the dynamic group processing article to call out that inactive/stale objects can increase evaluation workload and delay dynamic membership updates.

Changes:

  • Adds a NOTE explaining that dynamic rules evaluate all users/devices, including inactive ones.
  • Links readers to stale device and inactive user cleanup guidance.

Comment thread docs/identity/users/manage-dynamic-group.md Outdated
- **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.

> [!NOTE]
> Dynamic group rules evaluate every user and device in your tenant, including objects that are inactive or no longer in use. Stale devices and stale users can inflate group membership and slow down dynamic membership group processing. Before usin dynamic membership groups clean-up [stale devices](/entra/identity/devices/manage-stale-devices) and [inactive users](/entra/identity/monitoring-health/howto-manage-inactive-user-accounts) so your group reflects only the objects you intend to manage.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 161d7fd:

✅ Validation status: passed

File Status Preview URL Details
docs/identity/users/manage-dynamic-group.md ✅Succeeded

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants