You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-arm-restore-vms.md
+55-20Lines changed: 55 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -330,34 +330,69 @@ For more information, see [Back up and restore Active Directory domain controlle
330
330
331
331
Managed identities eliminate the need for the user to maintain the credentials. Managed identities provide an identity for applications to use when connecting to resources that support Microsoft Entra authentication.
332
332
333
-
Azure Backup offers the flexibility to restore the managed Azure VM with [managed identities](../active-directory/managed-identities-azure-resources/overview.md). You can choose to select [system-managed identities](../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types) or user-managed identities as shown in the figure below. This is introduced as one of the input parameters in the [**Restore configuration** blade](#create-a-vm) of Azure VM. Managed identities used as one of the input parameters is only used for accessing the storage accounts, which are used as staging location during restore and not for any other Azure resource controlling. These managed identities have to be associated to the vault.
333
+
Azure Backup offers the flexibility to restore the managed Azure VM with [managed identities](../active-directory/managed-identities-azure-resources/overview.md). You can choose to select [system-managed identities](../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types) or user-managed identities as shown in the figure below. This is introduced as one of the input parameters in the [**Restore configuration** blade](#create-a-vm) of Azure VM. Managed identities are used for accessing the storage accounts and automated cleanup of any resources created during restore process in case of restore failures. These managed identities have to be associated to the vault.
334
334
335
335
:::image type="content" source="./media/backup-azure-arm-restore-vms/select-system-managed-identities-or-user-managed-identities.png" alt-text="Screenshot for choice to select system-managed identities or user-managed identities.":::
336
336
337
-
If you choose to select system-assigned or user-assigned managed identities, check for the below actions for managed identity on the target staging Storage Account.
337
+
If you choose to select system-assigned or user-assigned managed identities, check for the below actions for managed identity on the target staging Storage Account and Resource Group.
Or, add the role assignment on the staging location (Storage Account) to have [Storage account Backup Contributor](./blob-backup-configure-manage.md#grant-permissions-to-the-backup-vault-on-storage-accounts)and [Storage Blob data Contributor](../role-based-access-control/built-in-roles.md#storage-blob-data-contributor) for the successful restore operation.
395
+
Or, add the **VM restore operator** role assignment on the staging location (Storage Account) and target Resource Group for the successful restore operation.
361
396
362
397
:::image type="content" source="./media/backup-azure-arm-restore-vms/add-role-assignment-on-staging-location.png" alt-text="Screenshot for adding the role assignment on the staging location.":::
Copy file name to clipboardExpand all lines: articles/role-based-access-control/built-in-roles/compute.md
+114Lines changed: 114 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1856,6 +1856,120 @@ View Virtual Machines in the portal and login as a regular user.
1856
1856
}
1857
1857
```
1858
1858
1859
+
## Virtual Machine Operator
1860
+
1861
+
This role is for providing necessary permissions on the staging storage account and target resource group during VM restore operations using Azure Backup.
1862
+
1863
+
> [!div class="mx-tableFixed"]
1864
+
> | Actions | Description |
1865
+
> | --- | --- |
1866
+
> | Microsoft.Authorization/*/read | Read access to all authorization resources |
1867
+
> | Microsoft.Compute/disks/read | Read access to compute disks |
1868
+
> | Microsoft.Compute/disks/write | Write access to compute disks |
1869
+
> | Microsoft.Compute/disks/delete | Delete access to compute disks |
1870
+
> | Microsoft.Compute/disks/beginGetAccess/action | Begin get access action on compute disks |
1871
+
> | Microsoft.Compute/disks/endGetAccess/action | End get access action on compute disks |
1872
+
> | Microsoft.Compute/locations/diskOperations/read | Read access to disk operations in a location |
1873
+
> | Microsoft.Compute/virtualMachines/read | Read access to virtual machines |
1874
+
> | Microsoft.Compute/virtualMachines/write | Write access to virtual machines |
1875
+
> | Microsoft.Compute/virtualMachines/delete | Delete access to virtual machines |
0 commit comments