You can restore an Azure Virtual Machine and its associated managed disks to the same tenant/subscription/region or across different Microsoft Entra tenants, regions and subscriptions.
Depending on your recovery objective, you can perform one of the following:
Azure VM Disk Data Restore: Use Data Restore to select specific data disks to restore into the virtual machine. You can select a specific data disk when restoring your Azure VM. The restored VM will include the disks selected for restore and the OS disk. For more information, see Restore Azure VM Disk Data.
Restore files and folders: With the File Level Restore functionality, you can restore specific files and folders from Azure disk backups. Recover files and folders to a custom storage container within your chosen Region and Storage Account. For more information, see File Level Restore for Azure VM.
Full VM Restore: Rebuild the entire virtual machine. This option allows you to fully customize the target environment. For more information, see Restore Full Azure VM.
Azure VM restore readiness prechecks
To ensure a successful recovery, Druva performs automated prechecks before the Azure VM restore is triggered. This validation identifies resource mismatches and configuration gaps, such as regional availability or networking conflicts, allowing administrators to remediate blockers upfront and guarantee a seamless restore process. For detailed readiness checks and error resolutions, see Azure VM Restore Readiness Prechecks.
Restore considerations
You can configure the restore parameters such as region, Vnet, subnet, and so on. Tags defined during manual or auto configuration of the backups will be pre-populated by default.
By default Druva will change the VM and the disk name so that the restore does not fail.
A single job is initiated when restoring a VM and any associated disk IDs.
Restoring an Azure VM in-place is currently not supported. All recovery operations create a separate, newly restored virtual machine instance to safeguard existing operational workloads.
With Azure Disk Encryption (ADE) or Customer-Managed Key (CMK) encryption, you will not be able to perform cross-tenant or cross-subscription restore. The restore operation must be performed within the same tenant and subscription where the backup was created.
Restore tags
You may define additional tags when restoring a virtual machine or its associated disks. You can also remove an existing Azure tag from your management console. Removing tags added from your management console will only remove these from your Enterprise Workloads console and will not impact your Azure environment.
📝 Note
Backup tags defined at the time of configuring the virtual machine for backup will be automatically inherited by the restored VM.
You can define additional tags but ensure that the key remains distinct. You can choose to overwrite an existing Azure tag, in which case the new additional tag will replace the existing one.