You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Move Azure App Service resources across resource groups or subscriptions
3
3
description: Use Azure Resource Manager to move App Service resources to a new resource group or subscription.
4
4
ms.topic: conceptual
5
5
ms.custom: devx-track-arm-template
6
-
ms.date: 09/13/2024
6
+
ms.date: 02/11/2025
7
7
---
8
8
9
9
# Move App Service resources to a new resource group or subscription
@@ -18,20 +18,20 @@ You can move App Service resources to a new resource group or subscription but y
18
18
19
19
When you move an app across subscriptions, the following guidance applies:
20
20
21
-
- Moving a resource to a new resource group or subscription is a metadata change that shouldn't affect anything about how the resource functions. For example, the inbound IP address for an app service doesn't change when moving the app service.
21
+
- Moving a resource to a new resource group or subscription is a metadata change that doesn't affect how the resource functions. For example, the inbound IP address for an app service doesn't change when you move the app service.
22
22
- The destination resource group must not have any existing App Service resources. App Service resources include:
23
23
- Web apps
24
24
- App Service plans
25
25
- Uploaded or imported TLS/SSL certificates
26
26
- App Service Environments
27
-
-All App Service resources in the resource group must be moved together.
28
-
-App Service Environments can't be moved to a new resource group or subscription.
27
+
-You must move all App Service resources in the resource group together.
28
+
-You can't move App Service Environments to a new resource group or subscription.
29
29
- You can move an app and plan hosted on an App Service Environment to a new subscription without moving the App Service Environment. The app and plan that you move are always associated with your initial App Service Environment. You can't move an app/plan to a different App Service Environment.
30
-
- If you need to move an app and plan to a new App Service Environment, you'll need to recreate these resources in your new App Service Environment. Consider using the [backup and restore feature](../../../app-service/manage-backup.md) as way of recreating your resources in a different App Service Environment.
31
-
-Apps with private endpoints cannot be moved. Delete the private endpoint(s) and recreate it after the move.
32
-
-Apps with virtual network integration can't be moved. Remove the virtual network integration and reconnect it after the move.
33
-
-App Service resources can only be moved from the resource group in which they were originally created. If an App Service resource is no longer in its original resource group, move it back to its original resource group. Then, move the resource across subscriptions. For help with finding the original resource group, see the next section.
34
-
- When you move an app to a different resource group or subscription, the location of the app remains the same, but its policy is changed. For example, consider a case where your app runs in `Subscription1` (Central US) and has `Policy1` and `Subscription2` (UK South) that has `Policy2`. If you move your app to Subscription2, the location of the app remains the same (Central US); however, it falls under the new policy `Policy2`.
30
+
- If you need to move an app and plan to a new App Service Environment, you must recreate these resources in your new App Service Environment. To recreate your resources in a different App Service Environment, consider using the [backup and restore feature](../../../app-service/manage-backup.md).
31
+
-You can't move apps with private endpoints. To move the app, delete the private endpoints and recreate them after the move.
32
+
-You can't move apps with virtual network integration. To move the app, remove the virtual network integration and reconnect it after the move.
33
+
-You can only move App Service resources from the resource group where you originally created them. If an App Service resource isn't in its original resource group, move it back to its original resource group. Then, move the resource across subscriptions. For help with finding the original resource group, see the next section.
34
+
- When you move an app to a different resource group or subscription, the location of the app remains the same, but its policy changes. For example, consider a case where your app runs in `Subscription1` (Central US) and has `Policy1` and `Subscription2` (UK South) that has `Policy2`. If you move your app to Subscription2, the location of the app remains the same (Central US); however, it falls under the new policy `Policy2`.
35
35
36
36
## Find original resource group
37
37
@@ -53,19 +53,19 @@ You see the recommended actions to take before moving the resources. The informa
53
53
54
54
## Move hidden resource types in portal
55
55
56
-
When using the portal to move your App Service resources, you may see an error indicating that you haven't moved all of the resources. If you see this error, check if there are resource types that the portal didn't display. Select **Show hidden types**. Then, select all of the resources to move.
56
+
When you use the portal to move your App Service resources, you might see an error indicating that you didn't move all of the resources. If you see this error, check if there are resource types that the portal didn't display. Select **Show hidden types**. Then, select all of the resources to move.
57
57
58
58
:::image type="content" source="./media/app-service-move-limitations/show-hidden-types.png" alt-text="Screenshot of the Show Hidden Types option in the portal when moving App Service resources.":::
59
59
60
60
## Move with free managed certificates
61
61
62
62
You can't move a free App Service managed certificate. Instead, delete the managed certificate and recreate it after moving the web app. To get instructions for deleting the certificate, use the **Migration Operations** tool.
63
63
64
-
If your free App Service managed certificate gets created in an unexpected resource group, try moving the app service plan back to its original resource group. Then, recreate the free managed certificate. This issue will be fixed.
64
+
If your free App Service managed certificate gets created in an unexpected resource group, try moving the app service plan back to its original resource group. Then, recreate the free managed certificate. This change fixes the issue.
65
65
66
66
## Move support
67
67
68
-
To determine which App Service resources can be moved, see move support status for:
68
+
To determine which App Service resources you can move, see move support status for:
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/move-limitations/classic-model-move-limitations.md
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Move Azure classic deployment resources
3
3
description: Use Azure Resource Manager to move classic deployment resources to a new resource group or subscription.
4
4
ms.topic: conceptual
5
-
ms.date: 06/20/2024
5
+
ms.date: 02/11/2025
6
6
ms.custom: devx-track-arm-template
7
7
---
8
8
@@ -12,26 +12,26 @@ The steps to move resources deployed through the classic model differ based on w
12
12
13
13
## Move in the same subscription
14
14
15
-
When moving resources from one resource group to another resource group within the same subscription, the following restrictions apply:
15
+
When you move resources from one resource group to another resource group within the same subscription, the following restrictions apply:
16
16
17
-
-Virtual networks (classic) can't be moved.
18
-
-Virtual machines (classic) must be moved with the cloud service.
19
-
-Cloud service can only be moved when the move includes all its virtual machines.
20
-
-Only one cloud service can be moved at a time.
21
-
-Only one storage account (classic) can be moved at a time.
22
-
-Storage account (classic) can't be moved in the same operation with a virtual machine or a cloud service.
17
+
-You can't move virtual networks (classic).
18
+
-You must move virtual machines (classic) with the cloud service.
19
+
-You can only move the cloud service when the move includes all its virtual machines.
20
+
-You can only move one cloud service at a time.
21
+
-You can only move one storage account (classic) at a time.
22
+
-You can't move storage account (classic) in the same operation with a virtual machine or a cloud service.
23
23
24
-
To move classic resources to a new resource group within the same subscription, use the [standard move operations](../move-resource-group-and-subscription.md) through the portal, Azure PowerShell, Azure CLI, or REST API. You use the same operations as you use for moving Resource Manager resources.
24
+
To move classic resources to a new resource group within the same subscription, use the [standard move operations](../move-resource-group-and-subscription.md) through the portal, Azure PowerShell, Azure CLI, or REST API. Use the same operations as you use for moving Resource Manager resources.
25
25
26
26
## Move across subscriptions
27
27
28
-
When moving classic cloud services to a new subscription, the following restrictions apply:
28
+
When you move classic cloud services to a new subscription, the following restrictions apply:
29
29
30
30
- The source and target subscriptions need to be under the same Microsoft Entra tenant.
31
-
- Cloud Service Provider (CSP) subscriptions do not support migrating classic cloud services.
31
+
- Cloud Service Provider (CSP) subscriptions don't support migrating classic cloud services.
32
32
- All classic resources in the subscription must be moved in the same operation.
33
33
- The target subscription must not have any other classic resources.
34
-
-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.
34
+
-You can only request the move 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.
35
35
36
36
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:
37
37
@@ -76,7 +76,7 @@ To move classic resources to a new subscription, use the REST operations that ar
76
76
```
77
77
78
78
The response is in the same format as the source subscription validation.
79
-
1.If both subscriptions pass validation, move all classic resources from one subscription to another subscription with the following operation:
79
+
1.Move all classic resources that pass validation from one subscription to another subscription. Use the following operation:
80
80
81
81
```HTTP
82
82
POST https://management.azure.com/subscriptions/{subscription-id}/providers/Microsoft.ClassicCompute/moveSubscriptionResources?api-version=2016-04-01
@@ -90,27 +90,27 @@ To move classic resources to a new subscription, use the REST operations that ar
90
90
}
91
91
```
92
92
93
-
The operation may run for several minutes.
93
+
The operation might run for several minutes.
94
94
95
95
## Possible error messages in the source subscription validation stage
96
96
97
97
### "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}_"
98
98
99
-
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.
99
+
This message means there's a classic cloud service that's ongoing migrating to the cloud service (extended support). You should abort this ARM migration operation and then retry validation.
100
100
101
101
### "Source subscription _{subscription ID}_ is empty"
102
102
103
-
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.
103
+
The source subscription can't be empty, disabled, deleted, or currently undergoing migration. During the migration period, write operations aren't allowed on resources within the subscription.
104
104
105
105
### "Source subscription contains application(s) which doesn't support migration: _{application name}_"
106
106
107
107
### "Source subscription contains following cloud service(s) which doesn't support migration: _{cloud service name}_"
108
108
109
-
The resources mentioned in the error message cannot be migrated, so users should delete these resources before triggering the migration.
109
+
You can't migrate the resources mentioned in the error message, so delete these resources before triggering the migration.
110
110
111
111
### More information
112
112
113
-
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.
113
+
The domain name and the public IP are still the same as before migration. Under normal circumstances, there's no downtime for the cloud service during the migration.
description: Use Azure Resource Manager to move Cloud Services (extended support) deployment resources to a new resource group or subscription.
4
4
ms.topic: conceptual
5
-
ms.date: 06/20/2024
5
+
ms.date: 02/11/2025
6
6
ms.custom: hirshah, devx-track-arm-template
7
7
---
8
8
@@ -12,24 +12,24 @@ The steps to move resources deployed through the Cloud Services (extended suppor
12
12
13
13
## Move in the same subscription
14
14
15
-
When moving Cloud Services (extended support) resources from one resource group to another resource group within the same subscription, the following restrictions apply:
15
+
When you move Cloud Services (extended support) resources from one resource group to another resource group within the same subscription, the following restrictions apply:
16
16
17
-
- Cloud Service must not be in manual mode
18
-
- Cloud Service must not be VIP Swappable
19
-
- Cloud Service must not have any pending operations
20
-
- Cloud Service must not be in migration
21
-
- Cloud Service must not be in failed state
22
-
- Ensure the Cloud Service has an unexpired SAS blob URI pointing to the cloud service package
17
+
- Cloud Service must not be in manual mode.
18
+
- Cloud Service must not be VIP Swappable.
19
+
- Cloud Service must not have any pending operations.
20
+
- Cloud Service must not be in migration.
21
+
- Cloud Service must not be in failed state.
22
+
- Ensure the Cloud Service has an unexpired SAS blob URI pointing to the cloud service package.
23
23
24
24
> [!NOTE]
25
-
> Cloud Services and associated networking resources (for example, PublicIPs and network security groups) can be move independently. Load balancers must always exist in the same resource group
25
+
> You can move Cloud Services and associated networking resources (for example, PublicIPs and network security groups) independently. However, load balancers must always exist in the same resource group.
26
26
27
-
To move classic resources to a new resource group within the same subscription, use the [standard move operations](../move-resource-group-and-subscription.md) through the portal, Azure PowerShell, Azure CLI, or REST API. You use the same operations as you use for moving Resource Manager resources.
27
+
To move classic resources to a new resource group within the same subscription, use the [standard move operations](../move-resource-group-and-subscription.md) through the portal, Azure PowerShell, Azure CLI, or REST API. Use the same operations for moving Resource Manager resources.
28
28
29
29
## Move across subscriptions
30
30
31
-
When moving Cloud Services (extended support) deployments to a new subscription, the following restrictions apply:
31
+
When you move Cloud Services (extended support) deployments to a new subscription, the following restrictions apply:
32
32
33
-
-When performing a cross subscription move, all associated cloud service resources such key vault and network resources must move together.
34
-
- If faced with a Move Resource operation error saying that the cloud service can't be moved because of a prior failed operation, create a ticket to resolve the issue.
33
+
-For cross-subscription moves, you must move all associated cloud service resources, such as key vault and network resources.
34
+
- If you encounter a Move Resource operation error that states the cloud service can't be moved because of a prior failed operation, create a ticket to resolve the issue.
35
35
- Cloud Service must not have any cross-subscription references.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/move-limitations/networking-move-limitations.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Move Azure Networking resources to new subscription or resource group
3
3
description: Use Azure Resource Manager to move virtual networks and other networking resources to a new resource group or subscription.
4
4
ms.topic: conceptual
5
5
ms.custom: devx-track-arm-template
6
-
ms.date: 06/20/2024
6
+
ms.date: 02/11/2025
7
7
---
8
8
9
9
# Move networking resources to new resource group or subscription
@@ -16,13 +16,13 @@ If you want to move networking resources to a new region, see [Tutorial: Move Az
16
16
17
17
## Dependent resources
18
18
19
-
When moving a resource, you must also move its dependent networking resources. However, any resource that is associated with a **Standard SKU** public IP address can't be moved across subscriptions.
19
+
When you move a resource, you must also move its dependent networking resources. However, you can't move across subscriptions any resource associated with a **Standard SKU** public IP address.
20
20
21
21
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, and all other network interface cards for the virtual network. If a virtual machine is associated with a **Standard SKU** public IP address, [disassociate the public IP address](../../../virtual-network/ip-services/remove-public-ip-address-vm.md) before moving across subscriptions.
22
22
23
23
If you move the virtual network for an AKS cluster, the AKS cluster stops working. The local network gateways can be in a different resource group.
24
24
25
-
For more information, see [Scenario for move across subscriptions](../move-resource-group-and-subscription.md#scenario-for-move-across-subscriptions).
25
+
For more information, see [Scenario for move across subscriptions](../move-resource-group-and-subscription.md#scenario-for-moving-across-subscriptions).
26
26
27
27
## Peered virtual network
28
28
@@ -49,7 +49,7 @@ The following [private-link resources](../../../private-link/private-endpoint-ov
49
49
All other private-link resources don't support move.
50
50
51
51
> [!NOTE]
52
-
> A private endpoint should be in succeeded state prior to attempting to move the resource.
52
+
> A private endpoint should be in succeeded state before you attempt to move the resource.
@@ -120,9 +120,9 @@ Some important steps precede moving a resource. You can avoid errors if you veri
120
120
121
121
1. **For a move across subscriptions, the resource and its dependent resources must be located in the same resource group and they must be moved together.** For example, a virtual machine with managed disks requires you to move the virtual machine, managed disks, and other dependent resources together.
122
122
123
-
If you're moving a resource to a new subscription, check if the resource has any dependent resources and if they're located in the same resource group. If the resources aren't in the same resource group, check if you can combine them into the same resource group. If you can, use one move operation across resource groups to consolidate all the resources into the same resource group.
123
+
If you're moving a resource to a new subscription, check if the resource has any dependent resources and if they're located in the same resource group. If the resources aren't in the same resource group, check if you can combine them into the same resource group. If you can, use one move operation across resource groups to consolidate all the resources into the same resource group.
124
124
125
-
To learn more, see [Scenario for move across subscriptions](#scenario-for-move-across-subscriptions).
125
+
For more information, see [Scenario for move across subscriptions](#scenario-for-moving-across-subscriptions).
0 commit comments