2.3.1. Intune and Windows 365 Roles, Scope Tags, and Multi-Admin Approval
💡 First Principle: Delegated administration answers four separate questions, and Intune gives each its own control: what can you do (the role), who are you (the members), on which users and devices (scope groups), and which policies and objects can you see (scope tags). When an admin can see something they shouldn't, or can't act on something they should, find which of the four answers is wrong.
Intune role-based access control is an extension of Microsoft Entra RBAC, managed at Intune admin center > Tenant administration > Roles. Permissions combine a category (such as Device configuration or Remote tasks) with actions (Read, Create, Update, Delete and so on). Built-in roles can't be edited or deleted; when none fits, you create a custom role, or Duplicate a built-in one as a starting point.
| Built-in Intune role | What it's for | Notable limits |
|---|---|---|
| Help Desk Operator | Remote tasks on users and devices; can assign apps and policies | Includes wipe, retire, rotate BitLocker keys and Remote Help, but not Rotate Local Admin Password |
| Policy and Profile Manager | Compliance policies, configuration profiles, Apple enrollment, corporate device identifiers, security baselines | Includes enrollment time grouping permissions |
| Endpoint Security Manager | Security baselines, compliance, Conditional Access integration, Defender for Endpoint | Can rotate BitLocker keys and remote lock, but can't wipe or retire |
| Application Manager | Mobile and managed apps; reads device information and configuration profiles | — |
| Intune Role Administrator | Custom roles and built-in role assignments | The only Intune role that can assign permissions to administrators |
| Read Only Operator | Views users, devices, enrollment, configuration and apps | Can't make changes |
| School Administrator | Intune for Education groups; lock, restart and retire devices | — |
| Endpoint Privilege Manager / Endpoint Privilege Reader | Named for Endpoint Privilege Management | Covered with that feature in Phase 3 |
Microsoft Entra roles also reach into Intune, and they bypass Intune RBAC entirely. Global Administrator and Intune Administrator (called Intune Service Administrator in Graph and PowerShell) have read/write access to all Intune data regardless of scope tags; Microsoft advises against using either for daily administration. Global Reader is read-only. Security Administrator is read-only across Intune but has full rights in the Endpoint security node. The Conditional Access Administrator role has no Intune data access at all.
Role assignments. Roles are assigned to groups of admins, a role can have many assignments, and an admin can hold many. With multiple assignments, permissions are additive. Scope groups should avoid All users and All devices so a regional admin can't target the whole company; and if an admin excludes a group in a policy assignment, that group must be within their scope groups.
Scope tags decide which objects an admin can see. Every object that supports tags gets the Default tag until you add others. When an admin creates a policy, all of their scope tags are applied to it automatically, and they can assign only the tags they hold. Assigning a tag to a group of devices tags those devices automatically. A role assignment with no scope tag sees every object its permissions allow. Creating tags requires the Intune Administrator role. By default, permissions from several role assignments that share a category are merged across their scope tags, which can grant broader access than intended. A Scoped permissions setting (opt-in public preview since March 2026, at Tenant administration > Roles > Settings) keeps each assignment's permissions inside its own tags. Enabling it is one-way — it can't be undone — so run the Permissions Assessment Report first.
Windows 365 roles are assigned in the same Intune admin center. With a Windows 365 subscription, Cloud PC Administrator (read/write across Cloud PC features) and Cloud PC Reader (view only) appear; the Entra Windows 365 Administrator role manages Cloud PCs in both Enterprise and Business editions. Azure network connections also need Azure roles — Windows 365 Network Interface Contributor on the connection's resource group and Windows 365 Network User on the virtual network. Windows 365 scope groups don't evaluate nested groups, so put target users in the scope group directly.
Multi Admin Approval (MAA) adds a second signature. An access policy, created at Tenant administration > Multi Admin Approval > Access policies, protects one resource type, and any change to a protected resource waits for a different admin to approve it. The protected types now cover apps (app deployments, not app protection policies), compliance policies, configuration policies (settings catalog), device actions (wipe, retire, delete), role-based access control, Windows scripts and tenant configuration (device categories). Changes to the access policies themselves always need approval. Enforcement also catches app-only Microsoft Graph calls against protected resources.
The workflow: the requester adds a business justification, an approver approves or rejects with notes, and then the requester selects Complete to apply the change. A request not processed within 3 days becomes Expired — submit on a Monday morning, and if nobody acts by Thursday morning, the change must be requested again. Intune sends no notifications, so approvers check the Received requests page. Approvers must be direct members of the policy's single approver group (a security group), hold Read permission on the resource type, and that group must belong to at least one Intune role assignment.
⚠️ Exam Trap: An administrator can never approve their own Multi Admin Approval request — not even as a member of the approver group, and not even as a Global Administrator or Intune Administrator. If a scenario has only one admin who could approve, the configuration needs a second eligible approver, not a more powerful role.
Reflection Question: A regional help desk in Berlin must wipe and retire only German devices and see only German policies. Which parts of the role assignment deliver each requirement, and why would adding a "Germany" scope tag alone, without a suitable role, give them nothing?