I recently migrated a VM from classic to resource manager and changed the subscription to be able to attach it to a certain virtual network.

I need to switch the VM back to the other subscription while keeping it attached to the v-net. In the portal it returns errors when trying to move the VM or the resource group it's in. The errors are from the virtual network,etc being in a different subscription.

I was wondering if anyone knew any workarounds using powershell, etc.

  • 1
    Azure support responded to my ticket and clarified that you cannot have a VM attached to a V-Net on different subscriptions.
    – Eric L
    Jul 24, 2017 at 13:32

3 Answers 3


If i understand what you exactly mean, the solution to your problem is, first to delete VM (NOT THE STORAGE) and then to deploy VM on your VNET. If you mean something else please send more details about the error.


Regrettably, a virtual machine alone cannot be moved to a different subscription as the machine needs a network available in the subscription where it is. However, you can copy underlying the disks of the virtual machine to the destination subscription and create the same VM with the copied disks in a new network available in the destination subscription. -Azure Support

  • 2
    You COULD peer vnets between different subscriptions, if all you are trying to do is keep network connectivity between those machines. Setup the VM on a vnet in subscription a and peer the vnet with vnet in sub b.
    – CtrlDot
    Jul 24, 2017 at 20:11

It is obvious that a virtual machine cannot exists without a network. My answer was based on a previous ticket, on Ms Support. Did you solve your problem or not ? If you don't then give more details, to help you..

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.