Entra memberOf retirement: start your access migration before 3 November

Your groups may remain visible while the access controls relying on their membership fall behind organisational change. With the deadline near, start discovery, dependency mapping and validation now.
On 3 November 2026, Microsoft ends support for the memberOf preview operator. Configurations still using it will stop updating, leaving memberships and assignments frozen in their last known state. [1]
The immediate risk is access drift: the people who should receive a licence, policy or application access may no longer match those who do.
A replacement rule is not enough. You must identify its dependencies, confirm it preserves the intended access decision and prove it works.
What is actually changing?
Affected configurations are Dynamic Membership Groups, Dynamic Administrative Units and Entitlement Management auto-assignment policies using memberOf. Not every Dynamic Group or membership relationship is affected. [1]
A rule such as:
user.memberof -any (group.objectId -in ['<source-group-id>'])populates a target group from a source group’s direct user members. The device equivalent uses device.memberof. Administrators must identify these patterns. [1]
Attribute-based rules are a possible migration path, but “member of this group” and “belongs to this department” are not automatically equivalent. The business must confirm the intended access decision. [2]
For access package auto-assignment, affected policies enter quarantine and stop processing until memberOf is removed from the rule. If no equivalent supported rule exists, plan another assignment method before removing the policy. [3]
The failure may be quiet
If an employee moves from Finance to Operations but a downstream group no longer updates, they may retain Finance application access that should have been removed.
The same issue can affect new starters, licensing, Teams and SharePoint access, and administrative scope. [1, 5]
Conditional Access needs special attention. Group exclusions override inclusions within a policy, so a stale exclusion can preserve an expired exception. [4] The policy remains enabled, but its targeting relies on stale group membership.
Impact depends on the wider control design. Assess the resulting access decision, not the group as if it were the entire security boundary.
Why the remaining time may be insufficient
The number of affected groups is a poor measure of migration effort.
One group may drive several applications, licences and Conditional Access policies. Others may rely on source groups owned by different teams. User and device groups may need different replacements.
The work can expand when those assumptions become visible:
The intended membership has never been documented.
The proposed attribute is missing or inconsistent.
Nobody owns the source group’s access decisions.
An application consumes membership differently from another service.
A change needs business approval and a controlled release window.
These are assessment questions, not universal facts. They show why waiting until the final week leaves little room for resolving dependencies and validating changes.
Choose a replacement that preserves the access decision
Use a supported dynamic rule when reliable attributes reflect real eligibility. First check who can modify them, including in connected source directories. Attribute-based membership is only as secure as those write permissions. [2]
Attributes controlling sensitive access need a trusted source, restricted write access and an accountable owner. Otherwise, the migration can introduce a new path for access manipulation.
Assigned membership may also fit. Converting an existing group preserves its identity and references; creating a new group requires updating those references. [6] Neither option defines how future membership changes will be maintained.
For assigned membership, define approval, removal, role-change handling and detection of missed updates. If automated, specify permissions, failure handling and reconciliation. A successful job does not prove access is correct.
Before using nested groups, verify how each consuming service handles them. One replacement may not fit every dependency.
A practical migration sequence
Begin with read-only discovery. Search group, administrative unit and auto-assignment rules, then record affected objects and owners.
Before making changes, build a dependency register covering purpose, source groups, current membership, intended eligibility, downstream assignments and the proposed replacement. Treat current membership as evidence, not proof of correctness.
Prioritise configurations by their security and business impact, including Conditional Access exclusions, sensitive application access, licensing and administrative scope.
Pilot with a small, representative population. Test a new starter, a role change, removal of eligibility and, where relevant, a device entering and leaving scope.
Validate in each consuming service. Confirm expected access, licensing, policy targeting or administrative scope after processing, including timely removal.
Migrate in controlled batches. Keep before-and-after evidence, a recovery plan and a named owner, then monitor later changes as well as the initial result.
What Nimbus Cyber recommends
Start with a verified impact assessment and prioritised change plan. Let the evidence determine the implementation path.
Nimbus Cyber connects Identity Governance decisions to the controls that enforce them: who should have access, why, and what happens when eligibility changes.
If you have not identified where memberOf is used, start now. The deadline leaves little room to discover dependencies during implementation.
For support with discovery, replacement design and access validation, contact Nimbus Cyber.
Thanks to TheCyberSec.gr for highlighting this retirement in its weekly Microsoft 365 security update and bringing it to our attention.
Sources
Technical details reviewed on 11 October 2026. Confirm the announcement in your tenant’s Message Center before scheduling changes.
Microsoft Learn — memberOf preview retirement and migration guidance
Microsoft Learn — Dynamic Membership rules and attribute security considerations
Microsoft Learn — Access package auto-assignment policies and memberOf retirement
Microsoft Learn — Conditional Access user and group assignments
MC1488834 — Message Center announcement reproduced in the community archive



Comments