If I move a Resource group that has a currently peered vNet to a new Subscription will the peering break?

Rob McNees 221 Reputation points
2024-03-29T16:43:52.68+00:00

One can move resource groups to new Subscriptions via this procedure: https://learn.microsoft.com/en-us/azure/load-testing/how-to-move-between-resource-groups-subscriptions#move-across-resource-groups-or-subscriptions

I have a live vNet in the DR Region where i'm conducting Test Failovers to so I can bring up the "ASR'd" VM up in DR Region (Named "primary-server-test") so that I can RDP into the server and validate information without affecting production primary server.

I would like to use this "vnet-asr-testing" for all "Test Failovers in Central US region. Since resource group and vNet are bound to a Subscription, I see that you can only Test Failover to vNets with same Subscription as Primary server, so I need to move to other Subscriptions that have ASR VMs in them to test.

So, when I move the resource group to a new Subscription, will the peered vNet inside of the resource group break, or will it still work. See attachment for context: MicrosoftQuestion.jpg

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
636 questions
0 comments No comments
{count} votes

Accepted answer
  1. Monalla-MSFT 11,801 Reputation points
    2024-03-29T17:46:14.7833333+00:00

    @Rob McNees - Thanks for reaching out to us.

    Moving a resource group to a new subscription should not break the peered virtual network inside the resource group. However, it is always a good idea to double-check the peering connection after the move to ensure that everything is working as expected.

    1. Ensure to move all dependent resources along with the virtual network, including all subnets, network security groups, and peering connections.
    2. If the virtual network is peered with another virtual network in a different subscription, you will need to update the peering connection to use the new subscription ID.
    3. If the virtual network is peered with a virtual network in the same subscription, the peering connection should continue to work without any changes.

    In your case, since you are moving the entire resource group to a new subscription, you should not need to update the peering connection.

    Here is a link to the doc that explains how to move resources between resource groups and subscriptions: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription

    Hope this helps. and please feel free to reach out if you have any further questions.


    Please don't forget to "Accept as Answer" and click "Yes" if the above response if helpful, so it can be beneficial to the community.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful