Move networking resources to new resource group or subscription
This article describes how to move virtual networks and other networking resources to a new resource group or Azure subscription.
During the move, your networking resources will operate without interruption.
If you want to move networking resources to a new region, see Tutorial: Move Azure VMs across regions.
Any resource, including a VPN Gateway, that is associated with a public IP Standard SKU address can't be moved across subscriptions. For virtual machines, you can disassociate the public IP address before moving across subscriptions.
When moving a resource, you must also move its dependent resources (for example - public IP addresses, virtual network gateways, all associated connection resources). Local network gateways can be in a different resource group.
To move a virtual machine with a network interface card to a new subscription, you must move all dependent resources. Move the virtual network for the network interface card, all other network interface cards for the virtual network, and the VPN gateways.
For more information, see Scenario for move across subscriptions.
Peered virtual network
To move a peered virtual network, you must first disable the virtual network peering. Once disabled, you can move the virtual network. After the move, reenable the virtual network peering.
You cannot move VPN Gateways across subscriptions if they are of Basic SKU. Basic SKU is only meant for test environment usage and doesn't support resource move operation.
You can't move a virtual network to a different subscription if the virtual network contains a subnet with resource navigation links. For example, if an Azure Cache for Redis resource is deployed into a subnet, that subnet has a resource navigation link.
The following private-link resources support move:
All other private-link resources don't support move.
For commands to move resources, see Move resources to new resource group or subscription.