Entra ID Launches New MemberOf Operator for Dynamic Membership Groups

New Implementation for memberOf Operator Comes with New Licensing Requirements

In August 2026, Microsoft announced the retirement of the memberOf operator for Entra dynamic group membership rules. The operator allowed the membership of a dynamic group to be calculated based on the membership of between one to fifty other groups. After four years of the feature remaining in preview, Microsoft apparently just couldn’t get the memberOf operator to work reliably, especially in large tenants, and retired the feature in early November 2026.

Microsoft likes to keep announcements for its Ignite conference, and this year’s event is no different with news of “memberOf Next” to replace the old operator, together with a new Transitive Reports To operator, designed to allow Entra ID to support a dynamic group based on “one manager, and the group includes that manager’s direct reports, their reports, and so on down the reporting hierarchy, up to 99 levels below the manager.” Both capabilities are now in public preview and can be used with dynamic groups and dynamic administrative units.

A New Processing Architecture

To solve the performance and reliability issues of the previous implementation, the new capabilities leverage “a new processing architecture designed for large tenants.” A tenant can now support up to 1,000 dynamic membership groups which use either the replacement memberOf operator or the new Transitive Reports To operator. This is an increase from 500 under the previous implementation.

The kicker is that Microsoft has changed the license requirement from Entra P1 to Entra ID Governance. Microsoft explains this by saying, “MemberOf Next and Transitive Reports To are built for governance scenarios in large tenants and run on dedicated processing. That’s why they’re part of Microsoft Entra ID Governance.”

The tenant must calculate the number of user accounts that come within the scope of memberOf processing and make sure that they have the appropriate number of Entra ID Governance licenses. Administrators who maintain dynamic membership groups that use memberOf must also have Entra ID Governance licenses. There’s a bunch of different ways to license Entra ID Governance, but the net outcome is that tenants will pay more for this capability unless they’re already using Entra ID Governance. To be fair, this is a common scenario among the large tenant audience that Microsoft is targeting.

Migrating from Older MemberOf Dynamic Groups

According to the documentation, tenants who haven’t removed old dynamic membership groups that use the memberOf operator can simply move to the new model by updating the group dynamicMembershipPriority property to be “Standard.” In other words, no change is required to the membership rule. If the dynamicMembershipPriority property is not updated, processing fails because Entra ID regards the group as using the old and now-deprecated implementation.

Because this is a new property, any existing groups that use memberOf will have a null value. Here’s what you might see after connecting a Microsoft Graph PowerShell SDK interactive session, signing-in with an account that has the Entra Groups administrator role (or better):

Connect-MgGraph -Scopes Group.ReadWrite.All
[array]$Groups = Get-MgGroup -All -Filter "groupTypes/any(c:c eq 'DynamicMembership')" -Property Id, DisplayName, MembershipRule, dynamicMembershipPriority | Where-Object { $_.MembershipRule -match 'memberOf'}

$Groups | Format-Table DisplayName, Id, dynamicMembershipPriority

DisplayName       Id                                   dynamicMembershipPriority
-----------       --                                   -------------------------
System Innovation 5c011293-7cc7-41c4-a0fc-3e3bb98db834

To migrate these groups to use the new memberOf, connect a Microsoft Graph PowerShell SDK session and sign-in with an account that has an Entra role such as Groups Administrator. Then run:

$RequestBody = @{ dynamicMembershipPriority = "Standard" }
Foreach ($Group in $Groups) {
   $Uri = "https://graph.microsoft.com/beta/groups/$($group.Id)"
   Invoke-MgGraphRequest -Method PATCH -Uri $Uri -Body $RequestBody
}

This code will fail unless your tenant has been upgraded with the new feature. Once an existing group is moved to MemberOf Next, or a new group using MemberOf Next or Transitive Reports To is created with Standard priority, Entra ID calculates its initial membership. Thereafter, Entra ID processes membership twice a day. Tenants cannot change the processing schedule, so if you use these dynamic membership groups for purposes such as group-based licensing, remember that changes won’t be reflected until the next processing run.

The dynamicMembershipPriority property for dynamic administrative units which use the memberOf operator must also be updated to Standard before Entra will compute the membership of these objects.

You might wonder how this magic happens. Well, memberOf remains the name of the operator in code. “MemberOf Next” is simply a marketing name. By keeping the same operator name, Microsoft makes it easier to upgrade dynamic membership groups.

Two Big Issues

It’s good that Microsoft has discovered a way to make dynamic membership groups based on other groups work as they should. Four years of preview for the previous iteration speaks to sustained effort or disinterest. I can’t figure out which it was. But introducing a replacement feature in this way is simply not good enough.

Given that Microsoft announced MemberOf Next only two weeks after the old memberOf preview stopped processing, it’s difficult to believe that the replacement processing architecture wasn’t already well advanced when Microsoft announced the retirement in August. They must also have known how easy it would be to move old dynamic membership groups to use the new processing architecture.

It would have caused a lot less angst for customers if they had revealed those facts at the time. Any work that customers might have done to follow Microsoft’s advice and replace the processing performed by the old memberOf groups was wasted, unless they decide not to pay Microsoft for the additional licenses required by MemberOf Next.

Charging customers more for the replacement also strikes a bum note after last week’s extraordinary Exchange Online outage. Whatever the merits of moving the capability into Entra ID Governance, customers who spent time removing or replacing memberOf rules after Microsoft’s August retirement announcement might reasonably wonder why they weren’t told that a replacement was coming.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.