Move Azure virtual Machine to another Vnet

Question

Move Azure virtual Machine to another Vnet

Allan Guerreiro 0

Hello,

I need to change the Vnet from one existing virtual machine, but Azure doesn't have a way to do it.

I built a script to clone the disk of the machine and deploy the machine again on the new network.
Ok, my script works fine.

But the problem is that all information on the Operating system is now missing.
User's image

How can I update that information?

anashetty 2,480 Reputation points Microsoft External Staff

2025-03-12T10:20:53.2433333+00:00

Hi Allan Guerreiro,

Moving an Azure Virtual Machine to a different Virtual Network requires recreating the VM, as Azure doesn't support direct VNet changes for existing VMs. The recommended approach involves deleting the VM while retaining its disks and then creating a new VM using these disks in the desired VNet or else If you prefer not to delete the existing VM, you can create a snapshot of the OS disk and use it to deploy a new VM in the desired VNet.Please look into this similar thread: https://learn.microsoft.com/en-us/answers/questions/959032/move-vms-to-another-vnet-in-same-region

For your reference: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm

If the script-based approach is causing issues, consider using Azure Backup to back up the VM and restore it to the new VNet. This method ensures that the OS state is preserved.
For your reference: Backup an Azure VM, Restore an Azure VM

If you have any further queries, please do let me know. If the information is helpful, please click on Upvote to let us know.
Allan Guerreiro 0 Reputation points

2025-03-12T11:40:50.3+00:00

@anashetty Thank you.

But, the problem is, even with Azure Backup to back up the VM and restore it to the new Vnet.

The operating system on the Azure portal is missing. How can I updated these information?
anashetty 2,480 Reputation points Microsoft External Staff

2025-03-13T05:46:45.0766667+00:00

Hi Allan Guerreiro,

Thanks for sharing information. Could you please let us know, are you able to connect to the VM.
Allan Guerreiro 0 Reputation points

2025-03-13T18:20:00.75+00:00

Yeah, I am

1 answer

Your answer

anashetty 2,480 Reputation points Microsoft External Staff

2025-03-12T10:20:53.2433333+00:00

Hi Allan Guerreiro,

Moving an Azure Virtual Machine to a different Virtual Network requires recreating the VM, as Azure doesn't support direct VNet changes for existing VMs. The recommended approach involves deleting the VM while retaining its disks and then creating a new VM using these disks in the desired VNet or else If you prefer not to delete the existing VM, you can create a snapshot of the OS disk and use it to deploy a new VM in the desired VNet.Please look into this similar thread: https://learn.microsoft.com/en-us/answers/questions/959032/move-vms-to-another-vnet-in-same-region

For your reference: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm

If the script-based approach is causing issues, consider using Azure Backup to back up the VM and restore it to the new VNet. This method ensures that the OS state is preserved.
For your reference: Backup an Azure VM, Restore an Azure VM

If you have any further queries, please do let me know. If the information is helpful, please click on Upvote to let us know.
Allan Guerreiro 0 Reputation points

2025-03-12T11:40:50.3+00:00

@anashetty Thank you.

But, the problem is, even with Azure Backup to back up the VM and restore it to the new Vnet.

The operating system on the Azure portal is missing. How can I updated these information?
anashetty 2,480 Reputation points Microsoft External Staff

2025-03-13T05:46:45.0766667+00:00

Hi Allan Guerreiro,

Thanks for sharing information. Could you please let us know, are you able to connect to the VM.
Allan Guerreiro 0 Reputation points

2025-03-13T18:20:00.75+00:00

Yeah, I am

Answer 1

Hi Allan Guerreiro,

Make sure you are taking a snapshot of the OS disk and then creating VM with set OS disk command:

Example:
Taking Snapshot:

# --- Parameters ---
$resourceGroupName = "<Your Resource Group Name>"
$vmName = "<Your VM Name>"
$snapshotName = "<Desired Snapshot Name>"
$location = "<Your Azure Region>" # e.g., "eastus"
# --- Get the VM and OS Disk ID ---
$vm = Get-AzVM -ResourceGroupName $resourceGroupName -Name $vmName
$osDiskId = $vm.StorageProfile.OsDisk.ManagedDisk.Id
# --- Create the Snapshot Configuration ---
$snapshotConfig = New-AzSnapshotConfig `
    -SourceUri $osDiskId `
    -CreateOption Copy `
    -Location $location
# --- Create the Snapshot ---
New-AzSnapshot `
    -Snapshot $snapshotConfig `
    -SnapshotName $snapshotName `
    -ResourceGroupName $resourceGroupName

Create a managed disk from snapshot:
https://learn.microsoft.com/en-us/azure/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-snapshot#sample-script

Create a VM from managed disk:
https://learn.microsoft.com/en-us/previous-versions/azure/virtual-machines/scripts/virtual-machines-powershell-sample-create-vm-from-managed-os-disks?toc=%2Fpowershell%2Fmodule%2Ftoc.json#sample-script

Regards,
Sarthak.

Allan Guerreiro 0 Reputation points

2025-03-13T18:19:30.4+00:00

I used your script to take the snapshot, but I am still missing the information after the machine creation.

Share via

Move Azure virtual Machine to another Vnet

1 answer

Your answer