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-resource-group-and-subscription.md
+67-67Lines changed: 67 additions & 67 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,94 +36,94 @@ Some important steps precede moving a resource. You can avoid errors if you veri
36
36
37
37
1. The source and destination subscriptions must exist within the same [Microsoft Entra tenant](../../active-directory/develop/quickstart-create-new-tenant.md). Use the Azure CLI or PowerShell to check that both subscriptions have the same tenant ID.
38
38
39
-
# [Azure CLI](#tab/azure-cli)
40
-
41
-
```azurecli-interactive
42
-
az account show --subscription <your-source-subscription> --query tenantId
43
-
az account show --subscription <your-destination-subscription> --query tenantId
If the tenant IDs for the source and destination subscriptions don't match, use the following methods to reconcile them:
56
-
57
-
-[Transfer billing ownership of an Azure subscription](../../cost-management-billing/manage/billing-subscription-transfer.md#transfer-billing-ownership-of-an-azure-subscription).
58
-
-[Associate or add an Azure subscription to your Microsoft Entra tenant](../../active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md).
39
+
# [Azure CLI](#tab/azure-cli)
40
+
41
+
```azurecli-interactive
42
+
az account show --subscription <your-source-subscription> --query tenantId
43
+
az account show --subscription <your-destination-subscription> --query tenantId
If the tenant IDs for the source and destination subscriptions don't match, use the following methods to reconcile them:
56
+
57
+
- [Transfer billing ownership of an Azure subscription](../../cost-management-billing/manage/billing-subscription-transfer.md#transfer-billing-ownership-of-an-azure-subscription).
58
+
- [Associate or add an Azure subscription to your Microsoft Entra tenant](../../active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md).
59
59
60
60
1. To move resources to or from a Cloud Solution Provider (CSP) partner, see [Transfer Azure subscriptions between subscribers and CSPs](../../cost-management-billing/manage/transfer-subscriptions-subscribers-csp.yml).
61
61
62
62
1. The resources you want to move must support the move operation. For a list of which resources support move operations, see [Azure resource types for move operations](move-support-resources.md).
63
63
64
64
1. Some services have specific limitations or requirements when moving resources. Check the following move guidance before moving resources within these services:
65
65
66
-
- If you're using Azure Stack Hub, you can't move resources between groups.
- To move an Azure subscription to a new management group, see [Move subscriptions](../../governance/management-groups/manage.md#move-management-groups-and-subscriptions).
66
+
- If you're using Azure Stack Hub, you can't move resources between groups.
- To move an Azure subscription to a new management group, see [Move subscriptions](../../governance/management-groups/manage.md#move-management-groups-and-subscriptions).
76
76
77
77
1. The destination subscription must be registered for the resource provider of the resource you're moving. If it's not, you receive an error stating that the **subscription isn't registered for a resource type**. You might see this error when moving a resource to a new subscription, but you didn't previously use the resource type in the subscription.
78
78
79
-
# [Azure CLI](#tab/azure-cli)
80
-
81
-
To get the registration status:
82
-
83
-
```azurecli-interactive
84
-
az account set -s <destination-subscription-name-or-id>
85
-
az provider list --query "[].{Provider:namespace, Status:registrationState}" --out table
1. Before starting a move operation, check the subscription quota for the subscription to which you're moving resources. Verify if you can request an increase in a quota that would cause a destination subscription to exceed its limit. For detailed guidance about limits and how to request an increase, see [Azure subscription and service limits, quotas, and constraints](../../azure-resource-manager/management/azure-subscription-service-limits.md).
112
112
113
113
1. The account moving the resources must have at least the following permissions:
114
114
115
-
- At the source resource group: **Microsoft.Resources/subscriptions/resourceGroups/moveResources/action**
116
-
- At the destination resource group: **Microsoft.Resources/subscriptions/resourceGroups/write**
115
+
- At the source resource group: **Microsoft.Resources/subscriptions/resourceGroups/moveResources/action**
116
+
- At the destination resource group: **Microsoft.Resources/subscriptions/resourceGroups/write**
117
117
118
118
1. If you move a resource with an active Azure role assignment (or its child resource with this same assignment), the role assignment doesn't move and becomes orphaned. You must create the role assignment again after the move. Although the system automatically removes the orphaned role assignment, we recommend that you remove it before the move.
119
119
120
-
To learn more about how to manage role assignments, see [List Azure role assignments](../../role-based-access-control/role-assignments-list-portal.yml#list-role-assignments-at-a-scope) and [Assign Azure roles](../../role-based-access-control/role-assignments-portal.yml).
120
+
To learn more about how to manage role assignments, see [List Azure role assignments](../../role-based-access-control/role-assignments-list-portal.yml#list-role-assignments-at-a-scope) and [Assign Azure roles](../../role-based-access-control/role-assignments-portal.yml).
121
121
122
122
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.
123
123
124
-
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.
125
-
126
-
For more information, see [Scenario for move across subscriptions](#scenario-for-moving-across-subscriptions).
124
+
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.
125
+
126
+
For more information, see [Scenario for move across subscriptions](#scenario-for-moving-across-subscriptions).
0 commit comments