Moving Azure Resources Across Subscriptions and Resource Groups

• Moving deployed Azure resources across subscriptions and resource groups may be required for reasons such as logical organization and billing accountability.
• The Azure portal and CLI, PowerShell, and REST APIs can be used to move resources of certain types across subscriptions and resource groups.
• Moving resources may require other changes, such as configuration, script, and code updates.

Moving deployed Azure resources across Azure subscriptions and resource groups (within an Azure account) is primarily a logical configuration change. However, solutions, scripts, and other processes that reference resources could require modifications after such moves.

(Moving resources across regions is discussed in “Moving Azure Resources Across Regions.”)

Why Move Resources Across Subscriptions and Resource Groups?

Azure deployments consist of provisioned resources such as VMs, databases, and Web Apps which are deployed logically in resource groups. A resource group exists within a subscription. (Neither subscriptions nor resource groups can be nested, so there is one level of each.) A subscription exists within an Azure account.