How to restore and keep Azure VM backups updated across subscriptions in different tenants?

There is no native/built-in solution to accomplish this. You can restore across subscriptions - but not tenants.

Details at

https://learn.microsoft.com/en-us/azure/backup/backup-azure-arm-restore-vms#restore-options

You could come up with a workaround - e.g. something similar to what's described at https://www.red-gate.com/simple-talk/blogs/move-disks-or-virtual-machines-between-tenants-on-azure/

1. Create a snapshot from each disk
2. From each snapshot, export it to VHD in a storage account.
3. Use AZCOPY to copy the VHDs to a storage on the different tenant
4. On the marketplace, create a new managed disk and select the option to create it from the VHD
5. Repeat the step 4 for each VHD
6. Open the managed disk which contains the operating system
7. Use the option to create a virtual machine from the disk
8. Attach the additional managed disks

This can potentially run on schedule - in order to address your automation needs

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Hi @Vanesa Arias Arenas

Solution1:

Using tools like AzCopy or relying solely on snapshots will not provide live synchronization—they only create point-in-time copies and are not suitable for real-time disaster recovery data will not in in sync from primary tenant to secondary tenant this won't work for your scenario

Solution2:

To ensure high availability and business continuity, enable replication for your virtual machines. This guarantees that data is continuously synchronized between the primary and secondary regions. In the event of a failover, you can quickly boot up the VM in the secondary region with the latest replicated data, minimizing downtime.

Replication is always active, ensuring near real-time sync.

With continuous sync enabled, the replicated data is written to disks in the target region. If an issue occurs with the primary VM, you can initiate a failover and launch the replicated VM using the most recent data.

Treat the VM like a physical server and use Disaster Recovery (such as Azure Site Recovery) to enable replication between the source and target tenants or regions.

Very Important:

Azure backup won't support direct backup from cross tenantPlease let me know if you face any challenge here, I can help you to resolve this issue further

Please provide your valuable comments

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.