Microsoft has recently extended the Multi-Admin Approval feature to cover some of the most impactful remote device actions available to administrators: Wipe, Retire, and Delete. This update introduces a dual-control workflow, often called a “four-eyes” principle, ensuring that no single administrator can unilaterally execute device reset actions.
This feature was previously only available for app, role and script deployments, but its extension to device lifecycle actions addresses key actions that could remove a device from Intune management.
While enabling multi-admin approval can directly mitigate the risk of accidental device actions or malicious device deletion, it does add a level of friction to what is generally a standard operational process. The feature enforces a mandatory peer review process, aligning with Zero Trust principles that demand explicit verification for critical operations, regardless of the user’s privilege level. However, it does introduce a potentially frustrating pause in the workflow and for high frequency environments, that may not be palatable.
How to Configure MAA for Device Actions
Setting up an access policy to protect device actions is a straightforward process within the Intune admin centre. Before you begin, ensure you have a dedicated Microsoft Entra security group containing the users who will act as approvers; all members must be eligible for the Intune Administrator role.
Sign in to the Microsoft Intune admin center.
Navigate to Tenant administration > Multi Admin Approval.
Select the Access policies tab and click + Create.
On the Basics page, provide a descriptive Name for the policy, such as “MAA for Device Wipe”.
From the Policy type dropdown menu, select the new Device actions for wipe, delete or retire and click Next.
On the Approvers page, click + Add groups and select the security group you designated for approvals and click Next.
On the Review + Create page, enter a business justification and click Submit for approval.
- A second Intune administrator must now log into the Intune admin center and approve the policy creation.
Understanding the Device Actions
A key consideration for designing your multi-admin approvals is ensuring you are only adding additional friction to the admin process where it is necessary. To understand where it is necessary, you should understand exactly how each device reset action impacts the device.
| Action | Primary Use Case | Impact on Data & Settings | MDM Management Status |
|---|---|---|---|
| Retire | Removing company data from BYOD devices when an employee leaves or the device is no longer used for work. | Removes company-managed apps, settings, and data. The user's personal data is left untouched. | The device is unenrolled from Intune management after it next checks in to receive the command. |
| Wipe | Resetting a corporate-owned device to its factory settings before giving it to a new user, or if the device has been lost or stolen. | Restores the device to its factory default state, removing all data (company and personal), apps, and settings. | The device is fully unenrolled from Intune management. |
| Delete | Immediately removing stale, duplicate, or obsolete device records from the Intune console. | Removes the device record from Intune instantly. It also sends a Retire command to the device, which will be processed if the device is online. |
The device object is immediately removed from the Intune portal, regardless of device status. |
Once it’s understood which actions are most critical, you can plan your multi-admin approach accordingly. In my opinion, this is only suitable for larger organisations with multiple Intune administrators working in highly secure environments; it simply isn’t practical for smaller businesses with limited IT resources.
A good example is an organisation that operates a completely air-gapped backup environment, the sole purpose of which is to resume business operations following a catastrophic failure in the primary environment.

