Azure Backup: Multi-user authorization for Recovery Services vaults is now generally available
Published Jul 14 2022 11:42 AM 4,689 Views

Backup is often considered to be the last line of defense. Hence, it must be ensured that the backup data is always protected from any malicious actions. Multi-user authorization (MUA) for Azure Backup Recovery Services vaults can help you secure your backup data better by adding an additional layer of protection to critical operations on your Recovery Services vaults. A critical operation here can be described as an operation that could lead to loss of backup data, and hence, its misuse must be prevented.



For MUA, Azure Backup uses an Azure resource called the Resource Guard to ensure critical operations are performed only with applicable authorization. Therefore, to perform a critical operation successfully, you must have sufficient permissions on the associated Resource Guard as well. The following critical operations can be protected using MUA for Backup.




Disable soft delete


Disable MUA protection


Modify backup policy (reduced retention)

Optional: Can be excluded

Modify protection (reduced retention)

Optional: Can be excluded

Stop protection with delete data

Optional: Can be excluded

Change MARS security PIN

Optional: Can be excluded


MUA for Backup revolves around using 2 personas with clearly defined responsibilities in an organization to ensure no operations can be performed by an individual alone. Let's consider the following personas:

  • Backup admin: Owner of the Recovery Services vault and performs management operations on the vault. To begin with, the Backup admin must not have any permissions on the Resource Guard.
  • Security admin: Owner of the Resource Guard and serves as the gatekeeper of critical operations on the vault. Hence, the Security admin controls permissions that the Backup admin needs to perform critical operations on the vault.

To perform a critical operation that is protected by MUA, the Backup admin must first obtain the right set of permissions on the Resource Guard.


Using MUA for Recovery Services vaults

Described below is a typical scenario for configuring and using MUA for Recovery Services vaults.

  1. The Backup admin creates the Recovery Services vault. They can also configure MUA on existing vaults.
  2. The Security admin creates the Resource Guard. The Resource Guard can be in a different subscription or a different tenant with respect to the Recovery Services vault. It must be ensured that the Backup admin does not have Contributor permissions on the Resource Guard.
  3. The Security admin grants the Reader role to the Backup Admin for the Resource Guard (or a relevant scope). The Backup admin requires the reader role to enable MUA on the vault.
  4. The Backup admin now navigates to the vault and configures it to be protected by MUA and provides the Resource Guard to be used.
  5. Now, if the Backup admin wants to perform a critical operation on the vault, they need to request access to the Resource Guard. The Backup admin can contact the Security admin for details on gaining access to perform such operations. They can do this using Privileged Identity Management (PIM) or other processes as mandated by the organization.
  6. The Security admin temporarily grants the Contributor role on the Resource Guard to the Backup admin to perform critical operations.
  7. Now, the Backup admin initiates the critical operation.
  8. The Azure Resource Manager checks if the Backup admin has sufficient permissions or not. Since the Backup admin now has Contributor role on the Resource Guard, the request is completed.
    • If the Backup admin did not have the required permissions/roles, the request would have failed.
  9. The security admin ensures that the privileges to perform critical operations are revoked after authorized actions are performed or after a defined duration. Using JIT tools Azure Active Directory Privileged Identity Management may be useful in ensuring this.




Refer to the documentation to know more about configuring and using multi-user authorization for Backup.

Version history
Last update:
‎Jul 14 2022 11:42 AM
Updated by: