Help with switching a vm to another existing virtual network

Question

Help with switching a vm to another existing virtual network

HOlly Boyer 26

I have a vm that we created in Azure, with a virtual network that only has the default subnet (10.0.0.0/24). I want to change it to a subnet that we created after we created this vm that is on another vnet. How do i move this vm to the other virtual network with an already existing subnet so that i can change the private ip address to the 10.50.5.x that we created in the new vnet?

Accepted answer

3 additional answers

Your answer

Answer 1

Jackson Martins 10,606 MVP Volunteer Moderator

Hi @HOlly Boyer
Sorry,
It's not possible to change VNET from VM; you can recreate it by deleting the VM but keeping the disks and creating the VM with the new Subnet using an existing disk

Get in touch if you need more help with this issue.

--please don't forget to "Accept the answer" if the reply is helpful--

Jackson Martins 10,606 Reputation points MVP Volunteer Moderator

2022-08-01T17:19:16.363+00:00

reference: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm
HOlly Boyer 26 Reputation points

2022-08-01T18:08:16.073+00:00

I kept coming to that answer in my searching as well but was hoping there was another answer. Thank you for confirming!

Answer 2

Dale Alexander 5

I disagree with the official answer. You can shutdown the VM...add a new network interface within the new vnet, removing the old interface and reboot. This is a possible option.

Jackson Martins 10,606 Reputation points MVP Volunteer Moderator

2023-02-14T08:48:34.4533333+00:00

unfortunately not!

You can only attach interface on the same current vnet, and you cannot detach all interfaces because machine must always have at least one network interface attached
Holly M B 5 Reputation points

2023-02-14T13:07:36.9033333+00:00

@Jackson Martins Yes, I can confirm that, i wasn't able to detach all of them, had to have at least one. It was grayed out.
Jackson Martins 10,606 Reputation points MVP Volunteer Moderator

2023-02-14T13:18:55.2466667+00:00

Yes,

This prevents making the network change by changing the NICs, unfortunately, to change the network, just doing the process I mentioned above (in the accepted answer)
Holly M B 5 Reputation points

2023-02-14T13:22:44.66+00:00

@Jackson Martins Yep we decided to just leave the VM on the original IP address instead for now Maybe one day we will change it with your method above. Thank you for your help.
Edmond Korbi 0 Reputation points

2023-02-23T16:06:16.47+00:00

You can move a NIC between Subnets on the same VNET, but you can not change the VNET on a NIC.

Same way, you can add a secondary to a VM, and this new NIC can be connected to a different Subnet within the same VNET, but you can not add a NIC connected to a Subnet on a different VNET
Jabulani Motloung 191 Reputation points

2023-11-10T13:27:46.5+00:00

@Dale Alexander is correct.

Answer 3

Erick 1

This is still just awful. Azure puts an unnecessary gate on requiring a VM have a NIC attached. This is 100% not necessary. I should be able to detach a NIC from a VM even when that VM has no other NIC attached.

Mike Howard 6 Reputation points

2023-01-30T21:43:50.49+00:00

Or do the virtual equivalent of unplugging a network cable from a switch and plugging it into a different switch. If I have another virtual network in the same region, why in the world can I not just switch the vnic to that vnet? Having to tear down a machine and redeploy seems silly.

Answer 4

Dale Alexander 5

I don't think the answer is correct.

If you shutdown the vm...and add a new network interface within the the new virtual network, removing the old network afterwards and restarting the VM, you can move the VM to a new network space. Maybe I'm wrong, but i've done the above without issue.

Jackson Martins 10,606 Reputation points MVP Volunteer Moderator

2023-02-14T08:45:38.43+00:00

Hi!

it is not possible to do that

to attach network interface your new NIC must exist in the same virtual network with the network interface currently attached to the VM

And you can't detach it, because a virtual machine must always have at least one network interface attached to it.
Nidhi 0 Reputation points

2023-11-13T22:00:42.21+00:00

This solution helps if you want to create a new interface on the same vnet. However, if you want to move the VM to a different vnet, this does not help as per my understanding.

This may help: https://medium.com/@mason.mcgerry/how-to-move-an-azure-vm-to-another-vnet-6ac3def4097

Share via

Help with switching a vm to another existing virtual network

3 additional answers

Your answer