您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

将资源移到新资源组或订阅中Move resources to new resource group or subscription

本文说明了如何将资源移动到新订阅,或移动到同一个订阅中的新资源组。This article shows you how to move resources to either a new subscription or a new resource group in the same subscription. 可以使用门户、PowerShell、Azure CLI 或 REST API 移动资源。You can use the portal, PowerShell, Azure CLI, or the REST API to move resource. 无需 Azure 支持人员的任何协助,即可使用本文中所述的移动操作。The move operations in this article are available to you without any assistance from Azure support.

在移动资源的过程中,源组和目标组都会锁定。When moving resources, both the source group and the target group are locked during the operation. 在完成移动之前,将阻止对资源组执行写入和删除操作。Write and delete operations are blocked on the resource groups until the move completes. 此锁意味着将无法添加、更新或删除资源组中的资源,但并不意味着资源已被冻结。This lock means you cannot add, update, or delete resources in the resource groups, but it does not mean the resources are frozen. 例如,如果将 SQL Server 及其数据库移动到新的资源组中,则使用该数据库的应用程序将不会遇到停机的情况。For example, if you move a SQL Server and its database to a new resource group, an application that uses the database experiences no downtime. 它仍可读取和写入到数据库。It can still read and write to the database.

不能更改该资源的位置。You cannot change the location of the resource. 移动资源仅能够将其移动到新的资源组。Moving a resource only moves it to a new resource group. 新的资源组可能有不同的位置,但这不会更改该资源的位置。The new resource group may have a different location, but that does not change the location of the resource.

备注

本文介绍如何在现有 Azure 帐户产品/服务中移动资源。This article describes how to move resources within an existing Azure account offering. 如果确实想要更改 Azure 帐户产品(如从即用即付升级到预付),同时继续使用现有资源,请参阅 Switch your Azure subscription to another offer(将 Azure 订阅切换到其他产品)。If you actually want to change your Azure account offering (such as upgrading from pay-as-you-go to pre-pay) while continuing to work with your existing resources, see Switch your Azure subscription to another offer.

移动资源前需查看的清单Checklist before moving resources

移动资源之前需执行的一些重要步骤。There are some important steps to perform before moving a resource. 验证这些条件可以避免错误。By verifying these conditions, you can avoid errors.

  1. 源订阅与目标订阅必须在同一个 Azure Active Directory 租户中。The source and destination subscriptions must exist within the same Azure Active Directory tenant. 若要检查这两个订阅是否具有相同的租户 ID,请使用 Azure PowerShell 或 Azure CLI。To check that both subscriptions have the same tenant ID, use Azure PowerShell or Azure CLI.

    对于 Azure PowerShell,请使用:For Azure PowerShell, use:

    (Get-AzureRmSubscription -SubscriptionName <your-source-subscription>).TenantId
    (Get-AzureRmSubscription -SubscriptionName <your-destination-subscription>).TenantId
    

    对于 Azure CLI,请使用:For Azure CLI, use:

    az account show --subscription <your-source-subscription> --query tenantId
    az account show --subscription <your-destination-subscription> --query tenantId
    

    如果源订阅和目标订阅的租户 ID 不相同,可使用以下方法协调租户 ID:If the tenant IDs for the source and destination subscriptions are not the same, use the following methods to reconcile the tenant IDs:

  2. 该服务必须支持移动资源的功能。The service must enable the ability to move resources. 本文列出了支持对资源进行移动的服务和不支持对资源进行移动的服务。This article lists which services enable moving resources and which services do not enable moving resources.

  3. 必须针对要移动的资源的资源提供程序注册目标订阅。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 encounter this problem when moving a resource to a new subscription, but that subscription has never been used with that resource type.

    对于 PowerShell,请使用以下命令来获取注册状态:For PowerShell, use the following commands to get the registration status:

    Set-AzureRmContext -Subscription <destination-subscription-name-or-id>
    Get-AzureRmResourceProvider -ListAvailable | Select-Object ProviderNamespace, RegistrationState
    

    若要注册资源提供程序,请使用:To register a resource provider, use:

    Register-AzureRmResourceProvider -ProviderNamespace Microsoft.Batch
    

    对于 Azure CLI,请使用以下命令来获取注册状态:For Azure CLI, use the following commands to get the registration status:

    az account set -s <destination-subscription-name-or-id>
    az provider list --query "[].{Provider:namespace, Status:registrationState}" --out table
    

    若要注册资源提供程序,请使用:To register a resource provider, use:

    az provider register --namespace Microsoft.Batch
    
  4. 移动资源的帐户至少需要具备下列权限:The account moving the resources must have at least the following permissions:

    • 源资源组上的 Microsoft.Resources/subscriptions/resourceGroups/moveResources/action 权限。Microsoft.Resources/subscriptions/resourceGroups/moveResources/action on the source resource group.
    • 目标资源组上的 Microsoft.Resources/subscriptions/resourceGroups/write 权限。Microsoft.Resources/subscriptions/resourceGroups/write on the destination resource group.

何时致电支持人员When to call support

可以通过本文中所述的自助服务操作移动大部分资源。You can move most resources through the self-service operations shown in this article. 使用自助服务操作可以:Use the self-service operations to:

有以下需要时,请联系支持人员Contact support when you need to:

  • 将资源移到新的 Azure 帐户(和 Azure Active Directory 租户),并且对于上一部分中的说明需要帮助。Move your resources to a new Azure account (and Azure Active Directory tenant) and you need help with the instructions in the preceding section.
  • 移动经典资源时遇到限制方面的问题。Move classic resources but are having trouble with the limitations.

可以移动的服务Services that can be moved

支持同时移动到新资源组和订阅的服务包括:The services that enable moving to both a new resource group and subscription are:

  • API 管理API Management
  • 应用服务应用(Web 应用)- 请参阅应用服务限制App Service apps (web apps) - see App Service limitations
  • 应用服务证书App Service Certificates
  • Application InsightsApplication Insights
  • 自动化Automation
  • Azure Cosmos DBAzure Cosmos DB
  • BatchBatch
  • 必应地图Bing Maps
  • CDNCDN
  • 云服务 - 请参阅经典部署限制Cloud Services - see Classic deployment limitations
  • 认知服务Cognitive Services
  • 内容审查器Content Moderator
  • 数据目录Data Catalog
  • 数据工厂Data Factory
  • 数据湖分析Data Lake Analytics
  • Data Lake StoreData Lake Store
  • DNSDNS
  • 事件中心Event Hubs
  • HDInsight 群集 - 请参阅 HDInsight 限制HDInsight clusters - see HDInsight limitations
  • IoT 中心IoT Hubs
  • Key VaultKey Vault
  • 负载均衡器 - 请参阅负载均衡器限制Load Balancers - see Load Balancer limitations
  • 逻辑应用Logic Apps
  • 机器学习 - 机器学习工作室 Web 服务可以移动到同一订阅中的资源组,但不能移动到不同订阅中。Machine Learning - Machine Learning Studio web services can be moved to a resource group in the same subscription, but not a different subscription. 其他机器学习资源可以跨订阅进行移动。Other Machine Learning resources can be moved across subscriptions.
  • 媒体服务Media Services
  • Mobile EngagementMobile Engagement
  • 通知中心Notification Hubs
  • 操作见解Operational Insights
  • 操作管理Operations Management
  • Power BIPower BI
  • 公共 IP - 请参阅公共 IP 限制Public IP - see Public IP limitations
  • Redis 缓存Redis Cache
  • 计划程序Scheduler
  • 搜索Search
  • 服务器管理Server Management
  • 服务总线Service Bus
  • Service FabricService Fabric
  • 存储Storage
  • 存储(经典)- 请参阅经典部署限制Storage (classic) - see Classic deployment limitations
  • 流分析 - 当流分析作业处于运行状态时,则无法进行移动。Stream Analytics - Stream Analytics jobs cannot be moved when in running state.
  • SQL 数据库服务器 - 数据库和服务器必须位于同一个资源组中。SQL Database server - database and server must reside in the same resource group. 当移动 SQL 服务器时,其所有数据库也会一起移动。When you move a SQL server, all its databases are also moved.
  • 流量管理器Traffic Manager
  • 虚拟机 - 包含托管磁盘的 VM 无法移动。Virtual Machines - VMs with managed disks cannot be moved. 请参阅虚拟机限制See Virtual Machines limitations
  • 虚拟机(经典)- 请参阅经典部署限制Virtual Machines (classic) - see Classic deployment limitations
  • 虚拟机规模集 - 请参阅虚拟机限制Virtual Machine Scale Sets - see Virtual Machines limitations
  • 虚拟网络 - 请参阅虚拟网络限制Virtual Networks - see Virtual Networks limitations
  • VPN 网关VPN Gateway

无法移动的服务Services that cannot be moved

目前不可移动资源的服务包括:The services that currently do not enable moving a resource are:

  • AD 域服务AD Domain Services
  • AD 混合运行状况服务AD Hybrid Health Service
  • 应用程序网关Application Gateway
  • BizTalk 服务BizTalk Services
  • 容器服务Container Service
  • Express RouteExpress Route
  • 开发测试实验室 - 支持移动到同一订阅中的新资源组,但不支持跨订阅移动。DevTest Labs - move to new resource group in same subscription is enabled, but cross subscription move is not enabled.
  • Dynamics LCSDynamics LCS
  • 负载均衡器 - 请参阅负载均衡器限制Load Balancers - see Load Balancer limitations
  • 托管应用程序Managed Applications
  • 托管磁盘 - 请参阅虚拟机限制Managed Disks - see Virtual Machines limitations
  • 公共 IP - 请参阅公共 IP 限制Public IP - see Public IP limitations
  • 恢复服务保管库 - 此外,也不可以移动与恢复服务保管库关联的计算、网络和存储资源,请参阅恢复服务限制Recovery Services vault - also do not move the Compute, Network, and Storage resources associated with the Recovery Services vault, see Recovery Services limitations.
  • 安全Security
  • StorSimple 设备管理器StorSimple Device Manager
  • 虚拟网络(经典)- 请参阅经典部署限制Virtual Networks (classic) - see Classic deployment limitations

虚拟机限制Virtual Machines limitations

托管磁盘不支持移动。Managed disks do not support move. 此限制意味着,多个相关资源也无法移动。This restriction means that several related resources cannot be moved too. 无法移动:You cannot move:

  • 托管磁盘Managed disks
  • 包含托管磁盘的虚拟机Virtual machines with the managed disks
  • 基于托管磁盘创建的映像Images created from managed disks
  • 基于托管磁盘创建的快照Snapshots created from managed disks
  • 包含托管磁盘的虚拟机的可用性集Availability sets with virtual machines with managed disks

无法资源组或订阅之间移动基于附加了计划的 Marketplace 资源创建的虚拟机。Virtual machines created from Marketplace resources with plans attached cannot be moved across resource groups or subscriptions. 在当前订阅中取消预配虚拟机,并在新的订阅中重新部署虚拟机。Deprovision the virtual machine in the current subscription, and deploy again in the new subscription.

证书存储在 Key Vault 中的虚拟机可以移动到同一订阅中的新资源组,但无法跨订阅进行移动。Virtual Machines with certificate stored in Key Vault can be moved to a new resource group in the same subscription, but not across subscriptions.

虚拟网络限制Virtual Networks limitations

移动虚拟网络时,还必须移动其从属资源。When moving a virtual network, you must also move its dependent resources. 例如,必须随虚拟网络一起移动网关。For example, you must move gateways with the virtual network.

若要移动对等的虚拟网络,必须首先禁用虚拟网络对等互连。To move a peered virtual network, you must first disable the virtual network peering. 在禁用后,可以移动虚拟网络。Once disabled, you can move the virtual network. 在移动后,重新启用虚拟网络对等互连。After the move, reenable the virtual network peering.

如果虚拟网络的任何子网包含资源导航链接,则无法将虚拟网络移动到其他订阅。You cannot move a virtual network to a different subscription if the virtual network contains a subnet with resource navigation links. 例如,如果 Redis 缓存资源部署到某个子网,则该子网具有资源导航链接。For example, if a Redis Cache resource is deployed into a subnet, that subnet has a resource navigation link.

应用服务限制App Service limitations

移动通过经典模型部署的资源时,其选项各不相同,具体取决于是在订阅内移动资源,还是将应用服务资源移到新的订阅。The limitations for moving App Service resources differ based on whether you are moving the resources within a subscription or to a new subscription.

这些部分中所述的限制适用于已上传的证书,不适用于应用服务证书。The limitations described in these sections apply to uploaded certificates, not App Service Certificates. 可将应用服务证书移动到新的资源组或订阅,且不会存在任何限制。You can move App Service Certificates to a new resource group or subscription without limitations. 如果你有多个使用相同应用服务证书的 Web 应用,请先移动所有这些 Web 应用,然后再移动证书。If you have multiple web apps that use the same App Service Certificate, first move all the web apps, then move the certificate.

在同一订阅中移动Moving within the same subscription

在同一订阅中_移动 Web 应用时,无法移动已上传的 SSL 证书。When moving a Web App _within the same subscription, you cannot move the uploaded SSL certificates. 不过,可以将 Web 应用移动到新的资源组而不移动其已上传的 SSL 证书,并且,应用的 SSL 功能仍然可以工作。However, you can move a Web App to the new resource group without moving its uploaded SSL certificate, and your app's SSL functionality still works.

如果希望随 Web 应用移动 SSL 证书,请执行以下步骤:If you want to move the SSL certificate with the Web App, follow these steps:

  1. 从 Web 应用中删除已上传的证书Delete the uploaded certificate from the Web App.
  2. 移动 Web 应用。Move the Web App.
  3. 将证书上传到移动后的 Web 应用。Upload the certificate to the moved Web App.

跨订阅移动Moving across subscriptions

在订阅之间_移动 Web 应用时存在以下限制:When moving a Web App _across subscriptions, the following limitations apply:

  • 目标资源组中不能有任何现有的应用服务资源。The destination resource group must not have any existing App Service resources. 应用服务资源包括:App Service resources include:
    • Web 应用Web Apps
    • 应用服务计划App Service plans
    • 上传或导入的 SSL 证书Uploaded or imported SSL certificates
    • 应用服务环境App Service Environments
  • 资源组中的所有应用服务资源必须一起移动。All App Service resources in the resource group must be moved together.
  • 只能从最初创建应用服务资源的资源组中移动它们。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, it must be moved back to that original resource group first, and then it can be moved across subscriptions.

经典部署限制Classic deployment limitations

移动通过经典模型部署的资源时,其选项各不相同,具体取决于是在订阅内移动资源,还是将资源移到新的订阅。The options for moving resources deployed through the classic model differ based on whether you are moving the resources within a subscription or to a new subscription.

相同的订阅Same subscription

在同一订阅内将资源从一个资源组移到另一个资源组时存在以下限制:When moving resources from one resource group to another resource group within the same subscription, the following restrictions apply:

  • 不能移动虚拟网络(经典)。Virtual networks (classic) cannot 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) cannot be moved in the same operation with a virtual machine or a cloud service.

要将经典资源移到同一订阅内的新资源组,请通过门户Azure PowerShellAzure CLIREST API 使用标准移动操作。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. 使用的操作应与移动 Resource Manager 资源时所用的操作相同。You use the same operations as you use for moving Resource Manager resources.

新订阅New subscription

将资源移到新订阅时存在以下限制:When moving resources to a new subscription, the following restrictions apply:

  • 必须在同一操作中移动订阅中的所有经典资源。All classic resources in the subscription must be moved in the same operation.
  • 目标订阅不得包含任何其他经典资源。The target subscription must not contain any other classic resources.
  • 只能通过独立的适用于经典移动的 REST API 来请求移动。The move can only be requested through a separate REST API for classic moves. 将经典资源移到新订阅时,不能使用标准的 Resource Manager 移动命令。The standard Resource Manager move commands do not work when moving classic resources to a new subscription.

要将经典资源移动到新订阅,请使用特定于经典资源的 REST 操作。To move classic resources to a new subscription, use the REST operations that are specific to classic resources. 若要使用 REST,请执行以下步骤:To use REST, perform the following steps:

  1. 检查源订阅是否可以参与跨订阅移动。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"
     ]
    }
    
  2. 检查目标订阅是否可以参与跨订阅移动。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.

  3. 如果两个订阅都通过了验证,可使用以下操作将所有经典资源从一个订阅移到另一个订阅: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.

恢复服务限制Recovery Services limitations

移动不支持用于使用 Azure Site Recovery 设置灾难恢复的“存储”、“网络”或“计算”资源。Move is not enabled for Storage, Network, or Compute resources used to set up disaster recovery with Azure Site Recovery.

例如,假设已设置将本地计算机复制到存储帐户 (Storage1),并且想要受保护的计算机在故障转移到 Azure 之后显示为连接到虚拟网络 (Network1) 的虚拟机 (VM1)。For example, suppose you have set up replication of your on-premises machines to a storage account (Storage1) and want the protected machine to come up after failover to Azure as a virtual machine (VM1) attached to a virtual network (Network1). 不能在同一订阅中的资源组之间或在订阅之间移动这些 Azure 资源 - Storage1、VM1 和 Network1。You cannot move any of these Azure resources - Storage1, VM1, and Network1 - across resource groups within the same subscription or across subscriptions.

若要在资源组之间移动在 Azure 备份中注册的 VM:To move a VM enrolled in Azure backup between resource groups:

  1. 暂时停止备份并保留备份数据Temporarily stop backup and retain backup data
  2. 将 VM 移至目标资源组Move the VM to the target resource group
  3. 在相同/新保管库中对其进行重新保护,用户可以从在移动操作之前创建的可用还原点进行还原。Reprotect it under the same/new vault Users can restore from the available restore points created before the move operation. 如果用户跨订阅移动备份 VM,则步骤 1 和步骤 2 保持相同。If the user moves the backed-up VM across subscriptions, step 1 and step 2 remain the same. 在步骤 3 中,用户需要在目标订阅中存在/创建的新保管库下保护 VM。In step 3, user needs to protect the VM under a new vault present/ created in the target subscription. 恢复服务保管库不支持跨订阅备份。Recovery Services vault does not support cross subscription backups.

HDInsight 限制HDInsight limitations

可以将 HDInsight 群集移到新的订阅或资源组。You can move HDInsight clusters to a new subscription or resource group. 但是,无法在订阅之间移动链接到 HDInsight 群集的网络资源(例如虚拟网络、网卡或负载均衡器)。However, you cannot move across subscriptions the networking resources linked to the HDInsight cluster (such as the virtual network, NIC, or load balancer). 此外,无法将连接到群集的虚拟机的网卡移到新的资源组。In addition, you cannot move to a new resource group a NIC that is attached to a virtual machine for the cluster.

将 HDInsight 群集移到新的订阅时,首先移动其他资源(如存储帐户)。When moving an HDInsight cluster to a new subscription, first move other resources (like the storage account). 然后移动 HDInsight 群集本身。Then, move the HDInsight cluster by itself.

搜索限制Search limitations

不能同时移动置于不同区域中的多个搜索资源。You cannot move multiple Search resources placed in different regions all at once. 在这种情况下,需要分别移动它们。In such a case, you need to move them separately.

负载均衡器限制Load Balancer limitations

可以移动基本 SKU 负载均衡器。Basic SKU Load Balancer can be moved. 不能移动标准 SKU 负载均衡器。Standard SKU Load Balancer cannot be moved.

公共 IP 限制Public IP limitations

可以移动基本 SKU 公共 IP。Basic SKU Public IP can be moved. 不能移动标准 SKU 公共 IP。Standard SKU Public IP cannot be moved.

使用门户Use portal

要移动资源,请选择包含这些资源的资源组,并选择“移动”按钮。To move resources, select the resource group containing those resources, and then select the Move button.

移动资源

选择是要将资源移到新资源组还是新订阅。Select whether you are moving the resources to a new resource group or a new subscription.

选择要移动的资源和目标资源组。Select the resources to move and the destination resource group. 确认需要更新这些资源的脚本,选择“确定”。Acknowledge that you need to update scripts for these resources and select OK. 如果在上一步中已选择“编辑订阅”图标,则还必须选择目标订阅。If you selected the edit subscription icon in the previous step, you must also select the destination subscription.

选择目标

在“通知”中,可以看到移动操作正在运行。In Notifications, you see that the move operation is running.

显示移动状态

操作完成后,会获得结果通知。When it has completed, you are notified of the result.

显示移动结果

使用 PowerShellUse PowerShell

要将现有资源移到另一个资源组或订阅,请使用 Move-AzureRmResource 命令。To move existing resources to another resource group or subscription, use the Move-AzureRmResource command. 下面的示例演示了如何将多个资源移动到新的资源组。The following example shows how to move multiple resources to a new resource group.

$webapp = Get-AzureRmResource -ResourceGroupName OldRG -ResourceName ExampleSite
$plan = Get-AzureRmResource -ResourceGroupName OldRG -ResourceName ExamplePlan
Move-AzureRmResource -DestinationResourceGroupName NewRG -ResourceId $webapp.ResourceId, $plan.ResourceId

若要移到新订阅,请包含 DestinationSubscriptionId 参数的值。To move to a new subscription, include a value for the DestinationSubscriptionId parameter.

使用 Azure CLIUse Azure CLI

若要将现有资源移动到另一个资源组或订阅,请使用 az resource move 命令。To move existing resources to another resource group or subscription, use the az resource move command. 提供要移动的资源的资源 ID。Provide the resource IDs of the resources to move. 下面的示例演示了如何将多个资源移动到新的资源组。The following example shows how to move multiple resources to a new resource group. --ids 参数中,提供要移动的资源 ID 的空格分隔列表。In the --ids parameter, provide a space-separated list of the resource IDs to move.

webapp=$(az resource show -g OldRG -n ExampleSite --resource-type "Microsoft.Web/sites" --query id --output tsv)
plan=$(az resource show -g OldRG -n ExamplePlan --resource-type "Microsoft.Web/serverfarms" --query id --output tsv)
az resource move --destination-group newgroup --ids $webapp $plan

若要移到新订阅,请提供 --destination-subscription-id 参数。To move to a new subscription, provide the --destination-subscription-id parameter.

使用 REST APIUse REST API

要将现有资源移到另一个资源组或订阅中,请运行:To move existing resources to another resource group or subscription, run:

POST https://management.azure.com/subscriptions/{source-subscription-id}/resourcegroups/{source-resource-group-name}/moveResources?api-version={api-version}

在请求正文中,指定目标资源组和要移动的资源。In the request body, you specify the target resource group and the resources to move. 有关移动 REST 操作的详细信息,请参阅移动资源For more information about the move REST operation, see Move resources.

后续步骤Next steps