Move virtual Machines to a new Subscription Within the same Tenant

Jaganljpmail 1 Reputation point
2021-09-20T18:25:22.96+00:00

Hello,

We have existing VM's in a Subscription, created another Subscription within the same Tenant and want to move Virtual machines and its resources to the New Subscription created. Tried using Azure Resource mover to move VM resources to the New Subscription Resource group in validation fails pointing to the Nics of the VMs and fails to go to next step.

let us know if this is a known issue with moving VM resources to a New Subscription within the same Tenant.

Thanks,

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,113 questions
Azure Resource Mover
Azure Resource Mover
An Azure service used for moving multiple resources between Azure regions.
200 questions
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Andreas Baumgarten 96,281 Reputation points MVP
    2021-09-20T19:30:37.39+00:00

    Hi @Jaganljpmail ,

    moving a VM with NIC should be possible to move between subscriptions.
    Is the NIC linked to a Public IP?
    There is a limitation with moving Public IPs between subscriptions:

    • Public IPs with Basic SKU could be moved between subscriptions
    • Public IPs with Standard SKU can't be moved between subscriptions

    Here you can find details which resource types supporting the move operation: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-support-resources

    ----------

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards
    Andreas Baumgarten

    1 person found this answer helpful.

  2. Jaganljpmail 1 Reputation point
    2021-09-21T15:36:42.827+00:00

    Hello @Andreas Baumgarten ,

    No the Nic linked to a private IP,

    Thanks,


  3. Andreas Baumgarten 96,281 Reputation points MVP
    2021-09-21T19:01:15+00:00

    Hi @Jaganljpmail ,

    it looks like you are not moving the vNet together with your VM?

    Than there is no option to move the VM with the Azure Resource Mover this way.

    But there is an option:

    • Delete the VM (VM only! Not the disk!)
    • Move the disk to the other subscription
    • Create a new VM in the other subscription using the existing (moved) disk

    Second option: You can use Azure Site Recovery to "move" the VM between the subscriptions.
    https://azure.microsoft.com/en-us/blog/cross-subscription-dr/

    ----------

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards
    Andreas Baumgarten


  4. Andreas Baumgarten 96,281 Reputation points MVP
    2021-09-22T13:48:01.027+00:00

    Hi @Jaganljpmail ,

    if you delete the VM and not the disk everything is stored on the disk. If you move the disk to another subscription the content of the disk will be the same. You won't loose any content of the disk when disk is moved from subscription A to B.

    Regarding Azure Site Recovery maybe this will help: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-common-questions#how-do-i-get-started-with-azure-vm-disaster-recovery

    ----------

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards
    Andreas Baumgarten


  5. Andreas Baumgarten 96,281 Reputation points MVP
    2021-09-23T04:45:32.757+00:00

    Hi @Jaganljpmail ,

    • Delete original VM object and leave other objects in place i.e nic, os disk
    • Move disk to the other subscription
    • In Azure Portal navigate to the disk (in the new subscription) and select Create VM
    • Create VM, may use original vm name or can we change it? - ** use the original name**
    • From Network select the target network and subnet

    You can try this first if you are not sure how and if this will work:

    • Create a new small VM just for testing
    • Follow the steps and verify if everything is working as expected
    • Delete the test VM

    Before moving the "productive VM" -> Backup VM!

    ----------

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards
    Andreas Baumgarten

    0 comments No comments