We use memberOf in some Entra dynamic membership rules. When will those rules stop updating, and what should we replace them with?
What should we do about Entra dynamic groups using memberOf?
Answers
Check the Microsoft message center for each tenant before planning around a single date. The reported deadline is November 3 for tenants without the qualifying license, while tenants with Entra ID Governance or higher reportedly have until March 31, 2027, with Microsoft planning a migration for those tenants. Verify the current notice and whether your tenant qualifies.
The concern is stale membership, not the groups being deleted. New users might miss licenses or access, and Conditional Access policies could continue using outdated group membership.
Reply to this answer
Start with an inventory. In Graph PowerShell, connect with Group.Read.All and AdministrativeUnit.Read.All, then retrieve dynamic groups and dynamic administrative units and filter their MembershipRule properties for memberOf. Include the IDs and full rules in the results so you can track each replacement.
Check access package auto-assignment policies separately. Microsoft documents a read-only export for policies using memberOf, which needs EntitlementManagement.Read.All. A group inventory alone won't catch those policies.
Reply to this answer
Where the membership really follows a user attribute, rewrite the rule around department, office, job title, or an extension attribute. Try the new rule in a test group before changing anything that controls production access.
For licensing, assigning directly to the source groups may be simpler. For a small group that rarely changes, assigned membership might be enough. Export the current members before changing the membership type.
Reply to this answer
If you need to keep deriving one group from others, scheduled automation is another option. Store the source and destination mappings, convert destinations to assigned membership, and have a runbook compare and update the members.
Build in safety checks. A failed source query or an unexpectedly empty result should not trigger a mass removal. This also adds an automation job to maintain, so it may be overkill for just a couple of groups.
Reply to this answer
Add your answer
Answers are reviewed before publication.
8h!wickerfuse_347:
Keep a record of the intended source groups and review the changes the job would make before letting it remove members.