ASR Modrnised, replicating VMs from one tenant to another.

Hello Venelin Ustabashiev, It looks like you're trying to understand why Azure Site Recovery (ASR) doesn’t allow Azure VMs to be treated as physical machines during cross-tenant migrations, especially in scenarios where subscription transfer isn’t feasible.

Here’s the gist: ASR focuses primarily on protecting and replicating workloads from a primary site to a secondary location, which is typically within the same tenant. When you migrate VMs across tenants, you're dealing with different Azure Stack or Azure accounts, which complicates how ASR can handle replication since each tenant's infrastructure needs explicit permissions and configurations.

Azure's architecture requires clear isolation for tenants, and treating VMs as physical machines in this scenario would undermine that isolation. Additionally, ASR relies on specific configurations for VMs that are tied to the tenant's unique settings, making it impractical to replicate or treat the VMs the same way across different tenant boundaries.

If you’re looking to migrate VMs between tenants, one approach involves using Azure Storage Explorer to manually copy VM disks and create new VMs in the target tenant. This method allows you to maintain the configurations as closely as possible.

Here’s a quick step-by-step to migrate VMs:

1. Prepare the source environment: Shut down the VMs.
2. Use Azure Storage Explorer: Access the source tenant’s storage account.
3. Copy VM disks: Use the copy function for the desired disks.
4. Transfer disks: Connect to the target tenant’s storage account and paste the disks.
5. Create new VMs: Use the copied disks to set up new VMs in the target tenant, ensuring similar configurations.

References:

• Backup and data recovery for Azure Stack with the Infrastructure Backup Service
• Replicate Azure Stack VMs to Azure
• Comprehensive Guide to Migrating Virtual Machines Across Tenants
• Azure VM Migration Guide