Move guidance for classic deployment model resources

Artikkeli
06/20/2024

The steps to move resources deployed through the classic model differ based on whether you're moving the resources within a subscription or to a new subscription.

Move in the same subscription

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

Virtual networks (classic) can't 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) can't 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 portal, Azure PowerShell, Azure CLI, or REST API. You use the same operations as you use for moving Resource Manager resources.

Move across subscriptions

When moving classic cloud services to a new subscription, the following restrictions apply:

The source and target subscriptions need to be under the same Microsoft Entra tenant.
Cloud Service Provider (CSP) subscriptions do not support migrating classic cloud services.
All classic resources in the subscription must be moved in the same operation.
The target subscription must not have any other classic resources.
The move can only be requested through a separate REST API for classic moves. The standard Resource Manager move commands don't work when moving classic resources to a new subscription.

To move classic resources to a new subscription, use the REST operations that are specific to classic resources. To use REST, do the following steps:

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": [
   "reason1",
   "reason2"
 ]
}

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.

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.

Possible error messages in the source subscription validation stage

"Subscription migration for SubscriptionId {subscription ID} cannot continue as IaaS classic to ARM migration is in progress for the following deployment resource: xx in HostedService {classic-cloud-service-name}"

This message means there is a classic cloud service that is ongoing migrating to the cloud service (extended support). Users should abort this ARM migration operation and then retry validation.

"Source subscription {subscription ID} is empty"

The source subscription cannot be empty, disabled, deleted or currently undergoing migration. During the migration period, write operations are not allowed on resources within the subscription.

"Source subscription contains application(s) which doesn't support migration: {application name}"

"Source subscription contains following cloud service(s) which doesn't support migration: {cloud service name}"

The resources mentioned in the error message cannot be migrated, so users should delete these resources before triggering the migration.

More information

The domain name and the public IP are still the same as before migration. Under normal circumstances, there should be no downtime for the cloud service during the migration.

Next steps

If you have trouble moving classic resources, contact Support.

For commands to move resources, see Move resources to new resource group or subscription.

Jaa