L18. Administrative Units and Delegated Administration
Course outlineLesson 18 of 18
Implement administrative units for the SC-300: create AUs to scope admin role assignments, configure dynamic membership rules for AUs, understand restricted management administrative units, and design a delegated administration model for large enterprises.
What Are Administrative Units?
Administrative units (AUs) are containers in Entra ID that restrict the scope of admin role assignments to a defined subset of users, groups, or devices. Without AUs, admin roles apply tenant-wide. With AUs, you can grant someone the User Administrator role but only for users in a specific department or region. Licensing: Creating AUs is available with Entra ID Free. AU-scoped administrators and dynamic user membership require Entra ID P1 (P2 also covers these requirements). Each unique user in dynamic AUs must be covered by P1; device members do not require licenses.
Why Use Administrative Units?
In large enterprises, different teams manage different populations of users:
- Regional IT: Manages users in their geographic region
- Department admins: Manages users in their department
- Help desk tiers: Different teams handle different user populations
AUs enable this delegation without granting tenant-wide admin privileges.
Creating Administrative Units
AUs can contain:
- Users
- Groups
- Devices
Membership Types
| Type | Description | License |
|---|---|---|
| Assigned | Members manually added by admin | Free to create; P1 for AU-scoped admins |
| Dynamic User | Users automatically added based on attribute rules | Free to create; P1 per matched user; P1 for AU-scoped admins |
| Dynamic Device | Devices automatically added based on attribute rules | Free to create; no license for device members; P1 for AU-scoped admins |
(user.department -eq "Engineering") -and (user.country -eq "US")
Exam tip: Dynamic AU membership requires Entra ID P1, not P2-only (P2 also satisfies the requirement). Creating any administrative unit, assigned or dynamic, is available with Entra ID Free; it's AU-scoped admin assignments and per-user dynamic membership that need P1. Cover each unique dynamic user member with P1; device members do not need licenses.
Scoping Role Assignments
After creating an AU, you assign admin roles scoped to that AU:
- Navigate to the AU
- Select Roles and administrators
- Assign a role (e.g., User Administrator) to a user or group
- The assignment applies only to objects within that AU
- Authentication Administrator
- Groups Administrator
- Helpdesk Administrator
- License Administrator
- Password Administrator
- User Administrator
Restricted Management Administrative Units
Restricted management AUs provide enhanced protection for sensitive accounts:
- Only admins explicitly assigned to the restricted AU can manage its members
- Tenant-level admins (including Global Administrators) cannot manage objects in a restricted AU unless they are specifically assigned a role on that AU
- This protects sensitive accounts (like executives) from being modified by broadly-scoped administrators
Design Patterns
Geographic Delegation
Create AUs by region (US, EU, APAC) with dynamic membership based on thecountry attribute. Assign regional IT staff as User Administrators scoped to their region's AU.
Departmental Delegation
Create AUs by department with dynamic membership based on thedepartment attribute. Assign department managers as Helpdesk Administrators scoped to their department's AU.
Tier-Based Help Desk
Create AUs by support tier. Tier 1 helpdesk can reset passwords for standard users (AU1). Tier 2 can manage users in privileged groups (AU2). Neither tier has tenant-wide access.Limitations
- AUs do not support nesting (an AU cannot contain another AU)
- AUs do not appear in the Azure portal resource hierarchy
- A user, group, or device can be a member of multiple AUs simultaneously
- AUs are for Entra ID role scoping only: they do not affect Azure RBAC (subscription/resource roles)
- ✓AUs restrict the scope of admin role assignments to a defined subset of users, groups, or devices
- ✓Creating AUs is Free; AU-scoped administrators and dynamic user membership require P1 (P2 also covers it); device members need no license
- ✓Restricted management AUs prevent even Global Administrators from managing members unless explicitly assigned
- ✓AUs scope Entra ID directory roles only: they have no effect on Azure resource RBAC
- ✓Not all roles support AU scoping: Global Administrator and Security Administrator are always tenant-wide
- ✓A user can be a member of multiple AUs simultaneously; AUs cannot be nested
1. What is unique about restricted management administrative units?
2. A regional IT team needs to manage user accounts only in their country. What should you configure?
3. Which of these Entra ID roles can be scoped to an administrative unit?