Skip to content

Commit a1002f2

Browse files
authored
Merge pull request #208051 from tfitzmac/0815saas
clarify Saas resource move support
2 parents a350e27 + f61ee90 commit a1002f2

File tree

2 files changed

+8
-1
lines changed

2 files changed

+8
-1
lines changed

articles/azure-resource-manager/management/move-resource-group-and-subscription.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Move resources to a new subscription or resource group
33
description: Use Azure Resource Manager to move resources to a new resource group or subscription.
44
ms.topic: conceptual
5-
ms.date: 11/30/2021
5+
ms.date: 08/15/2022
66
ms.custom: devx-track-azurecli, devx-track-azurepowershell
77
---
88

@@ -66,6 +66,8 @@ There are some important steps to do before moving a resource. By verifying thes
6666
* [Transfer ownership of an Azure subscription to another account](../../cost-management-billing/manage/billing-subscription-transfer.md)
6767
* [How to associate or add an Azure subscription to Azure Active Directory](../../active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md)
6868

69+
1. If you're attempting 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.md).
70+
6971
1. 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 see this error when moving a resource to a new subscription, but that subscription has never been used with that resource type.
7072

7173
For PowerShell, use the following commands to get the registration status:

articles/azure-resource-manager/management/move-support-resources.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ ms.date: 08/15/2022
99

1010
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.
1111

12+
Before starting your move operation, review the [checklist](./move-resource-group-and-subscription.md#checklist-before-moving-resources) to make sure you have satisfied prerequisites.
13+
1214
> [!IMPORTANT]
1315
> 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.
1416
@@ -1695,6 +1697,9 @@ Jump to a resource provider namespace:
16951697
16961698
## Microsoft.SaaS
16971699

1700+
> [!IMPORTANT]
1701+
> Marketplace offerings that are implemented through the Microsoft.Saas resource provider support resource group and subscription moves. These offerings are represented by the `resources` type below. For example, **SendGrid** is implemented through Microsoft.Saas and supports move operations. However, limitations defined in the [move requirements checklist](./move-resource-group-and-subscription.md#checklist-before-moving-resources) may limit the supported move scenarios. For example, you can't move the resources from a Cloud Solution Provider (CSP) partner.
1702+
16981703
> [!div class="mx-tableFixed"]
16991704
> | Resource type | Resource group | Subscription | Region move |
17001705
> | ------------- | ----------- | ---------- | ----------- |

0 commit comments

Comments
 (0)