Move or migrate Azure virtual machines to another subscription and a different region

 To move or migrate Azure virtual machines (VMs) from one virtual network (VNET) to another subscription and a different region, you can follow these steps:

1. Preparation:
   - Ensure that you have the necessary permissions and access rights in both subscriptions.
   - Determine the target region and the new VNET where you want to move the VMs.
   - Check if the target region supports the VM size and features of the existing VMs.

2. Create a virtual network (VNET) in the target region:
   - In the target subscription, create a new VNET in the desired region.
   - Configure the appropriate address space, subnets, and any required network settings.

3. Prepare the virtual machines:
   - Stop or deallocate the VMs you want to move. This step is necessary to ensure data consistency during the migration process.
   - Take note of the VM configuration, including OS disk, data disks, network interfaces, IP addresses, and any custom settings.

4. Move the virtual machines:
   - There are different approaches you can take to move the VMs. Here are a few options:

     a. Azure Site Recovery (ASR): Use Azure Site Recovery to replicate the VMs from the source region to the target region. Once replication is complete, you can failover the VMs to the target region and reconfigure the network settings to use the new VNET.

     b. Azure PowerShell or Azure CLI: You can use Azure PowerShell or Azure CLI to export the VM configuration, including OS disk and data disks. Then, create new VMs in the target region using the exported configuration, specifying the new VNET and other desired settings. After creating the new VMs, you can copy data from the source VMs to the new VMs.

     c. Azure Resource Manager (ARM) Templates: Create an ARM template that defines the desired state of the VMs in the target region, including the new VNET. Deploy the ARM template to the target subscription, which will create the VMs with the specified configuration.

5. Validate and test:
   - Once the VMs are successfully moved to the new subscription and region, validate that they are functioning as expected.
   - Test the connectivity and functionality of the VMs to ensure that all applications and services are working correctly.

6. Clean up:
   - Once the migration is confirmed to be successful and the new VMs are functioning properly, you can delete the old VMs in the source subscription, if desired.

Remember to plan and test your migration strategy before moving production workloads to ensure minimal downtime and a smooth transition. Additionally, consult the official Azure documentation and relevant Azure migration guides for the most up-to-date and detailed instructions.