Multi Admin Approval is enabled in Intune to require a second admin to approve sensitive tenant changes
ZTA.51015 is in Maester 3.0.0-preview and not in the stable 2.3.0 release yet. It will be in the next stable release. To use it now, install the preview:
Install-Module Maester -AllowPrerelease -ForceHow to get the preview, and go backUse the preview in GitHub Actions
MT.1096 (Ensure at least one Intune Multi Admin Approval policy is configured) checks the same setting. Running both reports it twice.
Overview
Section titled “Overview”When Intune Multi Admin Approval (MAA) is not configured, a single compromised administrator account is sufficient to push a malicious app to every managed device, deploy a hostile PowerShell script, wipe a fleet of corporate devices, alter compliance or configuration policies to weaken security, or grant additional privileged roles to an attacker-controlled account — all in one step, with no second pair of eyes. Threat actors who land on a privileged admin’s workstation, harvest a session token, phish an Intune Administrator, or exploit an unsupervised privileged session can execute these tenant-wide actions before any detective control has a chance to react. Multi Admin Approval inserts a mandatory second-administrator approval gate before high-impact changes take effect, ensuring that even a fully compromised single admin cannot deploy apps, run scripts, change compliance / configuration policies, perform mass device actions (wipe, retire, delete), modify role assignments, or alter device categories without an independent approver in a separate approver group consenting to the change. Without at least one MAA access policy in place with an approver group assigned, the entire Intune control surface is single-credential to compromise.
Remediation
Section titled “Remediation”- Use access policies to require admin approval for sensitive Intune actions
- Create an access policy
- Approve or reject a request for changes
- Role-based access control with Intune (least-privilege admin roles)
- Privileged Identity Management for just-in-time admin access
Run it
Section titled “Run it”The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:
Install-Module ZeroTrustAssessment -Scope CurrentUserConnect-MaesterInvoke-Maester -Pack ZTA -SkipBuiltInLeave out -SkipBuiltIn to run Maester’s own checks in the same run.
About this check
| Severity | High |
| Effort to fix | Medium |
| Impact on users | Low |
| Pillar | Devices |
| Category | Devices |
| Product | Intune |
| Feature | Tenant administration |
| Area | Privileged access |
| ATT&CK | T1072 Software Deployment Tools, T1078.004 Cloud Accounts |
| Licence | INTUNE_A |
| Tenant | Workforce |
Product, feature, area and ATT&CK are Maester’s: the assessment does not record them, so Maester keeps them in the pack’s taxonomy.json.
A Microsoft check, part of the Zero Trust Assessment pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, MIT licence.
About this check
- Severity
- High
- Effort to fix
- Medium
- Impact on users
- Low
- Product
- Intune
- Feature
- Tenant administration
- Area
- Privileged access
- Pack
- Microsoft Zero Trust Assessment