This article lists whether an Azure resource type supports the move operation. It also provides information about special conditions to consider when moving a resource.
Before starting your move operation, review the checklist to make sure you have satisfied prerequisites. Moving resources across Microsoft Entra tenants isn't supported.
Important
In most cases, a child resource can't be moved independently from its parent resource. Child resources have a resource type in the format of <resource-provider-namespace>/<parent-resource>/<child-resource>. For example, Microsoft.ServiceBus/namespaces/queues is a child resource of Microsoft.ServiceBus/namespaces. When you move the parent resource, the child resource is automatically moved with it. If you don't see a child resource in this article, you can assume it is moved with the parent resource. If the parent resource doesn't support move, the child resource can't be moved.
Microsoft.AAD
Resource type
Resource group
Subscription
Region move
domainservices
No
No
No
microsoft.aadiam
Resource type
Resource group
Subscription
Region move
diagnosticsettings
No
No
No
diagnosticsettingscategories
No
No
No
privatelinkforazuread
Yes
Yes
No
tenants
Yes
Yes
No
Microsoft.Advisor
Resource type
Resource group
Subscription
Region move
configurations
No
No
No
generaterecommendations
No
No
No
metadata
No
No
No
recommendations
No
No
No
suppressions
No
No
No
Microsoft.AlertsManagement
Resource type
Resource group
Subscription
Region move
alertprocessingrules
No
Yes
No
alerts
No
No
No
alertslist
No
No
No
alertsmetadata
No
No
No
alertssummary
No
No
No
alertssummarylist
No
No
No
smartdetectoralertrules
Yes
Yes
No
smartgroups
No
No
No
Microsoft.AnalysisServices
Resource type
Resource group
Subscription
Region move
servers
Yes
Yes
No
Microsoft.ApiManagement
Important
An API Management service that is set to the Consumption SKU can't be moved.
Runbooks must exist in the same resource group as the Automation Account.
The movement of System assigned managed identity, and User-assigned managed identity takes place automatically with the Automation account. For information, see Move your Azure Automation account to another subscription.
Batch accounts can't be moved directly from one region to another, but you can use a template to export a template, modify it, and deploy the template to the new region.
If the Azure Cache for Redis instance is configured with a virtual network, the instance can't be moved to a different subscription. See Networking move limitations.
Resource type
Resource group
Subscription
Region move
redis
Yes
Yes
No
redisenterprise
No
No
No
Microsoft.Capacity
Resource type
Resource group
Subscription
Region move
appliedreservations
No
No
No
calculateexchange
No
No
No
calculateprice
No
No
No
calculatepurchaseprice
No
No
No
catalogs
No
No
No
commercialreservationorders
No
No
No
exchange
No
No
No
reservationorders
No
No
No
reservations
No
No
No
resources
No
No
No
validatereservationorder
No
No
No
Microsoft.Cdn
Resource type
Resource group
Subscription
Region move
cdnwebapplicationfirewallmanagedrulesets
No
No
No
cdnwebapplicationfirewallpolicies
Yes
Yes
No
edgenodes
No
No
No
profiles
Yes
Yes
No
profiles / endpoints
Yes
Yes
No
Note
The self-service on moving CDN resource across subscriptions is not supported in Azure China currently.
When you try to move CDN configuration files or profiles/endpoints across subscriptions in Azure China, Please contact Azure support or submit the request on Azure Support Site for help.
Microsoft.ClassicCompute
Important
See Classic deployment move guidance. Classic deployment resources can be moved across subscriptions with an operation specific to that scenario.
Resource type
Resource group
Subscription
Region move
capabilities
No
No
No
domainnames
Yes
No
No
quotas
No
No
No
resourcetypes
No
No
No
validatesubscriptionmoveavailability
No
No
No
virtualmachines
Yes
Yes
No
Microsoft.ClassicInfrastructureMigrate
Important
See Classic deployment move guidance. Classic deployment resources can be moved across subscriptions with an operation specific to that scenario.
Resource type
Resource group
Subscription
Region move
classicinfrastructureresources
No
No
No
Microsoft.ClassicNetwork
Important
See Classic deployment move guidance. Classic deployment resources can be moved across subscriptions with an operation specific to that scenario.
Resource type
Resource group
Subscription
Region move
capabilities
No
No
No
expressroutecrossconnections
No
No
No
expressroutecrossconnections / peerings
No
No
No
gatewaysupporteddevices
No
No
No
networksecuritygroups
No
No
No
quotas
No
No
No
reservedips
No
No
No
virtualnetworks
No
No
No
Microsoft.ClassicStorage
Important
See Classic deployment move guidance. Classic deployment resources can be moved across subscriptions with an operation specific to that scenario.
Resource type
Resource group
Subscription
Region move
disks
No
No
No
images
No
No
No
osimages
No
No
No
osplatformimages
No
No
No
publicimages
No
No
No
quotas
No
No
No
storageaccounts
Yes
No
Yes
vmimages
No
No
No
Microsoft.ClassicSubscription
Important
See Classic deployment move guidance. Classic deployment resources can be moved across subscriptions with an operation specific to that scenario.
You can move HDInsight clusters to a new subscription or resource group. However, you can't move across subscriptions the networking resources linked to the HDInsight cluster (such as the virtual network, NIC, or load balancer). In addition, you can't move to a new resource group a NIC that is attached to a virtual machine for the cluster.
When moving an HDInsight cluster to a new subscription, first move other resources (like the storage account). Then, move the HDInsight cluster by itself.
Moving or renaming any Application Insights resource changes the resource ID. When the ID changes for a workspace-based resource, data sent for the prior ID is accessible only by querying the underlying Log Analytics workspace. The data will not be accessible from within the renamed or moved Application Insights resource.
A database and server must be in the same resource group. When you move a SQL server, all its databases are also moved. This behavior applies to Azure SQL Database and Azure Synapse Analytics databases.
Resource type
Resource group
Subscription
Region move
instancepools
No
No
No
locations
Yes
Yes
No
managedinstances
No
No
Yes
Learn more about moving managed instances across regions.