Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.1.5. Administrative Units

💡 First Principle: A role answers what an admin can do; an administrative unit answers to whom. Scoping a role to an AU lets you delegate real authority over part of the organization without delegating authority over all of it.

An administrative unit (AU) is a Microsoft Entra container for users, groups or devices. You assign a role scoped to the AU — say, Helpdesk Administrator over the "France" AU — and that admin can reset passwords for members of the AU and nobody else. AUs are how regional IT teams, subsidiaries or schools within a district manage their own people inside a single tenant. Membership can be assigned or dynamic (a rule such as user.country -eq "FR").

Licensing: creating AUs is free. Each admin with a role scoped to an AU needs Microsoft Entra ID P1. Members need only Free licenses, unless they're added by dynamic membership rules, which need P1.

Restricted management administrative units (RMAUs) turn the scope around. Instead of granting extra rights, they protect the objects inside: tenant-scoped admins — Global Administrators included — can't modify member objects unless they also hold a role scoped to that RMAU. Use them for accounts that must not be touched by the broader IT team, such as executives' accounts or break-glass accounts. Details that show up in questions:

  • Global Administrators can still create or delete the RMAU, change its membership and assign roles scoped to it — the protection applies to the members, not the unit.
  • Group owners can't manage a protected group on ownership alone.
  • License assignment and usage-location updates are still allowed without an RMAU-scoped role.
  • Members of an RMAU can't be governed with PIM or access reviews.
  • Restricted management can be chosen only when the AU is created — it can't be switched on or off later.

⚠️ Exam Trap: If the requirement is "even Global Administrators must not be able to reset the CEO's password unless specifically delegated," the answer is a restricted management administrative unit, created as restricted from the start. An ordinary AU doesn't block tenant-wide admins; it only scopes the admins you assign to it.

Reflection Question: You created an AU for your executive team last month and now want it to block tenant-wide admins. What do you have to do, and why can't you simply change a setting on the existing AU?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned