We have a new portal - please go here.

Move Azure resources to new Azure resource group or subscription

This topic shows you how to move resources to either a new subscription or a new resource group in the same subscription. You can use the portal, PowerShell, Azure CLI, or the REST API to move resource. The move operations in this topic are available to you without any assistance from Azure support.

Typically, you move resources when you decide that:

  • For billing purposes, a resource needs to live in a different subscription.
  • A resource no longer shares the same lifecycle as the resources it was previously grouped with. You want to move it to a new resource group so you can manage that resource separately from the other resources.

When moving resources, both the source group and the target group are locked during the operation. Write and delete operations are blocked on the groups until the move completes.

You cannot change the location of the resource. Moving a resource only moves it to a new resource group. The new resource group may have a different location, but that does not change the location of the resource.


This article describes how to move resources within an existing Azure account offering. If you actually want to change your Azure account offering (such as upgrading from pay-as-you-go to pre-pay) while continuing to work with your existing resources, see Switch your Azure subscription to another offer.

Checklist before moving resources

There are some important steps to perform before moving a resource. By verifying these conditions, you can avoid errors.

  1. The service must enable the ability to move resources. See the list below for information about which services enable moving resources.
  2. The source and destination subscriptions must exist within the same Active Directory tenant. To move to a new tenant, call support.
  3. The destination subscription must be registered for the resource provider of the resource being moved. If not, you receive an error stating that the subscription is not registered for a resource type. You might encounter this problem when moving a resource to a new subscription, but that subscription has never been used with that resource type. To learn how to check the registration status and register resource providers, see Resource providers and types.
  4. If you are moving App Service app, you have reviewed App Service limitations.
  5. If you are moving resources associated with Recovery Services, you have reviewed the Recovery Services limitations
  6. If you are moving resources deployed through classic model, you have reviewed Classic deployment limitations.

When to call support

You can move most resources through the self-service operations shown in this topic. Use the self-service operations to:

Call support when you need to:

  • Move your resources to a new Azure account (and Active Directory tenant).
  • Move classic resources but are having trouble with the limitations.

Services that enable move

For now, the services that enable moving to both a new resource group and subscription are:

  • API Management
  • App Service apps (web apps) - see App Service limitations
  • Automation
  • Batch
  • Bing Maps
  • BizTalk Services
  • CDN
  • Cloud Services - see Classic deployment limitations
  • Cognitive Services
  • Container Service
  • Content Moderator
  • Data Catalog
  • Data Factory
  • Data Lake Analytics
  • Data Lake Store
  • DevTest Lab
  • DNS
  • DocumentDB
  • Event Hubs
  • HDInsight clusters
  • IoT Hubs
  • Key Vault
  • Load Balancers
  • Logic Apps
  • Machine Learning
  • Media Services
  • Mobile Engagement
  • Notification Hubs
  • Operational Insights
  • Operations Management
  • Power BI
  • Redis Cache
  • Scheduler
  • Search
  • Server Management
  • Service Bus
  • Service Fabric
  • Storage
  • Storage (classic) - see Classic deployment limitations
  • Stream Analytics
  • SQL Database server - The database and server must reside in the same resource group. When you move a SQL server, all of its databases are also moved.
  • Traffic Manager
  • Virtual Machines - however, does not support move to a new subscription when its certificates are stored in a Key Vault
  • Virtual Machines (classic) - see Classic deployment limitations
  • Virtual Networks

Services that do not enable move

The services that currently do not enable moving a resource are:

  • AD Hybrid Health Service
  • Application Gateway
  • Application Insights
  • Express Route
  • Dynamics LCS
  • Recovery Services vault - also do not move the Compute, Network, and Storage resources associated with the Recovery Services vault, see Recovery Services limitations.
  • Security
  • Virtual Machines with certificate stored in Key Vault
  • Virtual Machines Scale Sets
  • Virtual Networks (classic) - see Classic deployment limitations
  • VPN Gateway

App Service limitations

When working with App Service apps, you cannot move only an App Service plan. To move App Service apps, your options are:

  • Move the App Service plan and all other App Service resources in that resource group to a new resource group that does not already have App Service resources. This requirement means you must move even the App Service resources that are not associated with the App Service plan.
  • Move the apps to a different resource group, but keep all App Service plans in the original resource group.

If your original resource group also includes an Application Insights resource, you cannot move that resource because Application Insights does not currently enable the move operation. If you include the Application Insights resource when moving App Service apps, the entire move operation fails. However, the Application Insights and App Service plan do not need to reside in the same resource group as the app for the app to function correctly.

For example, if your resource group contains:

  • web-awhich is associated with plan-a and app-insights-a
  • web-bwhich is associated with plan-b and app-insights-b

Your options are:

  • Move web-aplan-aweb-b, and plan-b
  • Move web-aand web-b
  • Move web-a
  • Move web-b

All other combinations involve either moving a resource type that can't move (Application Insights) or leaving behind a resource type that can't be left behind when moving an App Service plan (any type of App Service resource).

If your web app resides in a different resource group than its App Service plan but you want to move both to a new resource group, you must perform the move in two steps. For example:

  • web-aresides in web-group
  • plan-aresides in plan-group
  • You want web-aand plan-a to reside in combined-group

To accomplish this move, perform two separate move operations in the following sequence:

  1. Move the web-ato plan-group
  2. Move web-aand plan-a to combined-group.

You can move an App Service Certificate to a new resource group or subscription without any issues. However, if your web app includes an SSL certificate that you purchased externally and uploaded to the app, you must delete the certificate before moving the web app. For example, you can perform the following steps:

  1. Delete the uploaded certificate from the web app
  2. Move the web app
  3. Upload the certificate to the web app

Recovery Services limitations

Move is not enabled for Storage, Network, or Compute resources used to set up disaster recovery with Azure Site Recovery.

For example, suppose you have set up replication of your on-premises machines to a storage account (Storage1) and want the protected machine to come up after failover to Azure as a virtual machine (VM1) attached to a virtual network (Network1). You cannot move any of these Azure resources - Storage1, VM1, and Network1 - across resource groups within the same subscription or across subscriptions.

Classic deployment limitations

The options for moving resources deployed through the classic model differ based on whether you are moving the resources within a subscription or to a new subscription.

Same subscription

When moving resources from one resource group to another resource group within the same subscription, the following restrictions apply:

  • Virtual networks (classic) cannot be moved.
  • Virtual machines (classic) must be moved with the cloud service.
  • Cloud service can only be moved when the move includes all its virtual machines.
  • Only one cloud service can be moved at a time.
  • Only one storage account (classic) can be moved at a time.
  • Storage account (classic) cannot be moved in the same operation with a virtual machine or a cloud service.

To move classic resources to a new resource group within the same subscription, use the standard move operations through the portalAzure PowerShellAzure CLI, or REST API. You use the same operations as you use for moving Resource Manager resources.

New subscription

When moving resources to a new subscription, the following restrictions apply:

  • All classic resources in the subscription must be moved in the same operation.
  • The target subscription must not contain any other classic resources.
  • The move can only be requested through a separate REST API for classic moves. The standard Resource Manager move commands do not work when moving classic resources to a new subscription.

To move classic resources to a new subscription, you must use REST operations that are specific to classic resources. Perform the following steps to move classic resources to a new subscription.

  1. Check if the source subscription can participate in a cross-subscription move. Use the following operation:


 POST https://management.azure.com/subscriptions/{sourceSubscriptionId}/providers/Microsoft.ClassicCompute/validateSubscriptionMoveAvailability?api-version=2016-04-01

In the request body, include:



   "role": "source"


The response for the validation operation is in the following format:



   "status": "{status}",

   "reasons": [





  1. Check if the destination subscription can participate in a cross-subscription move. Use the following operation:


 POST https://management.azure.com/subscriptions/{destinationSubscriptionId}/providers/Microsoft.ClassicCompute/validateSubscriptionMoveAvailability?api-version=2016-04-01

In the request body, include:



   "role": "target"


The response is in the same format as the source subscription validation.

  1. If both subscriptions pass validation, move all classic resources from one subscription to another subscription with the following operation:


 POST https://management.azure.com/subscriptions/{subscription-id}/providers/Microsoft.ClassicCompute/moveSubscriptionResources?api-version=2016-04-01

In the request body, include:



   "target": "/subscriptions/{target-subscription-id}"


The operation may run for several minutes.

Use portal

To move resources to a new resource group in the same subscription, select the resource group containing those resources, and then select the Move button.

Or, to move resources to a new subscription, select the resource group containing those resources, and then select the edit subscription icon.

Select the resources to move and the destination resource group. Acknowledge that you need to update scripts for these resources and select OK. If you selected the edit subscription icon in the previous step, you must also select the destination subscription.

In Notifications, you see that the move operation is running.

When it has completed, you are notified of the result.

Use PowerShell

To move existing resources to another resource group or subscription, use the Move-AzureRmResource command.

The first example shows how to move one resource to a new resource group.


$resource = Get-AzureRmResource -ResourceName ExampleApp -ResourceGroupName OldRG

Move-AzureRmResource -DestinationResourceGroupName NewRG -ResourceId $resource.ResourceId

The second example shows how to move multiple resources to a new resource group.


$webapp = Get-AzureRmResource -ResourceGroupName OldRG -ResourceName ExampleSite

$plan = Get-AzureRmResource -ResourceGroupName OldRG -ResourceName ExamplePlan

Move-AzureRmResource -DestinationResourceGroupName NewRG -ResourceId $webapp.ResourceId, $plan.ResourceId

To move to a new subscription, include a value for the DestinationSubscriptionId parameter.

You are asked to confirm that you want to move the specified resources.



Are you sure you want to move these resources to the resource group

'/subscriptions/{guid}/resourceGroups/newRG' the resources:




[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): y



Use Azure CLI

To move existing resources to another resource group or subscription, use the azure resource movecommand. You need to provide the resource ids of the resources to move. You can get resource ids with the following command:


azure resource list -g sourceGroup --json

Which returns the following format:




    "id": "/subscriptions/{guid}/resourceGroups/sourceGroup/providers/Microsoft.Storage/storageAccounts/storagedemo",

    "name": "storagedemo",

    "type": "Microsoft.Storage/storageAccounts",

    "location": "southcentralus",

    "tags": {},

    "kind": "Storage",

    "sku": {

      "name": "Standard_RAGRS",

      "tier": "Standard"




The following example shows how to move a storage account to a new resource group. In the -iparameter, provide a comma-separated list of the resource id's to move.


azure resource move -i "/subscriptions/{guid}/resourceGroups/sourceGroup/providers/Microsoft.Storage/storageAccounts/storagedemo" -d "destinationGroup"

You are asked to confirm that you want to move the specified resource.


To move existing resources to another resource group or subscription, run:


POST https://management.azure.com/subscriptions/{source-subscription-id}/resourcegroups/{source-resource-group-name}/moveResources?api-version={api-version}

In the request body, you specify the target resource group and the resources to move. For more information about the move REST operation, see Move resources.

Next steps