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

有关平台支持的从经典部署模型到 Azure Resource Manager 的迁移的技术深入探讨Technical deep dive on platform-supported migration from classic to Azure Resource Manager

本文将深入探讨如何从 Azure 经典部署模型迁移到 Azure Resource Manager 部署模型。Let's take a deep-dive on migrating from the Azure classic deployment model to the Azure Resource Manager deployment model. 本文介绍资源和功能级别的资源,让用户了解 Azure 平台如何在两种部署模型之间迁移资源。We look at resources at a resource and feature level to help you understand how the Azure platform migrates resources between the two deployment models. 有关详细信息,请阅读服务通告文章:平台支持的从经典部署模型到 Azure Resource Manager 的 IaaS 资源迁移For more information, please read the service announcement article: Platform-supported migration of IaaS resources from classic to Azure Resource Manager.

将 IaaS 资源从经典部署模型迁移到 Azure 资源管理器Migrate IaaS resources from the classic deployment model to Azure Resource Manager

首先,必须了解在基础结构即服务 (IaaS) 资源上进行的数据平面操作和管理平面操作的差异。First, it's important to understand the difference between data-plane and management-plane operations on the infrastructure as a service (IaaS) resources.

  • “管理/控制平面”描述进入管理/控制平面或 API 来修改资源的调用。Management/control plane describes the calls that come into the management/control plane or the API for modifying resources. 例如,创建 VM、重启 VM 以及将虚拟网络更新成新子网等操作均可管理正在运行的资源。For example, operations like creating a VM, restarting a VM, and updating a virtual network with a new subnet manage the running resources. 它们并不直接影响到 VM 的连接。They don't directly affect connecting to the VMs.
  • “数据平面”(应用程序)描述应用程序本身的运行时,并涉及与不通过 Azure API 的实例的交互。Data plane (application) describes the runtime of the application itself, and involves interaction with instances that don’t go through the Azure API. 例如,访问网站或从运行中的 SQL Server 实例或 MongoDB 服务器拉取数据属于数据平面或应用程序交互。For example, accessing your website, or pulling data from a running SQL Server instance or a MongoDB server, are data plane or application interactions. 其他示例包括:从存储帐户复制 Blob,以及访问公共 IP 地址,以便使用远程桌面协议 (RDP) 或安全外壳 (SSH) 连接到虚拟机。Other examples include copying a blob from a storage account, and accessing a public IP address to use Remote Desktop Protocol (RDP) or Secure Shell (SSH) into the virtual machine. 这些操作可让应用程序继续跨计算、网络和存储运行。These operations keep the application running across compute, networking, and storage.

经典部署模型和资源管理器堆栈之间的数据平面是相同的。The data plane is the same between the classic deployment model and Resource Manager stacks. 区别在于,在迁移过程中,Microsoft 会将资源的表示方式从经典部署模型转换为资源管理器堆栈中的相应模型。The difference is that during the migration process, Microsoft translates the representation of the resources from the classic deployment model to that in the Resource Manager stack. 因此,需在资源管理器堆栈中使用新的工具、API 和 SDK 来管理资源。As a result, you need to use new tools, APIs, and SDKs to manage your resources in the Resource Manager stack.

显示管理/控制平面和数据平面之间差异的图

备注

在某些迁移方案中,Azure 平台会停止、释放和重新启动虚拟机。In some migration scenarios, the Azure platform stops, deallocates, and restarts your virtual machines. 这会导致短暂的数据平面停机。This causes a brief data-plane downtime.

迁移体验The migration experience

开始迁移之前:Before you start the migration:

  • 确保要迁移的资源未使用任何不受支持的功能或配置。Ensure that the resources that you want to migrate don't use any unsupported features or configurations. 通常平台会检测到这些问题并生成错误。Usually the platform detects these issues and generates an error.
  • 如果有不在虚拟网络中的 VM,平台会在准备操作期间停止这些 VM 并解除其分配。If you have VMs that are not in a virtual network, they are stopped and deallocated as part of the prepare operation. 如果不想丢失公共 IP 地址,可考虑先保留 IP 地址再触发准备操作。If you don't want to lose the public IP address, consider reserving the IP address before triggering the prepare operation. 如果 VM 位于虚拟网络中,则不会将其停止和解除分配。If the VMs are in a virtual network, they are not stopped and deallocated.
  • 规划在非工作时间迁移,以便应对迁移期间可能发生的任何意外失败。Plan your migration during non-business hours to accommodate for any unexpected failures that might happen during migration.
  • 使用 PowerShell、命令行接口 (CLI) 命令或 REST API 下载当前的 VM 配置,以便能够在完成准备步骤之后轻松进行验证。Download the current configuration of your VMs by using PowerShell, command-line interface (CLI) commands, or REST APIs to make it easier for validation after the prepare step is complete.
  • 先更新用于处理资源管理器部署模型的自动化和操作化脚本,再开始迁移。Update your automation and operationalization scripts to handle the Resource Manager deployment model, before you start the migration. 也可以选择在资源处于准备就绪状态时执行 GET 操作。You can optionally do GET operations when the resources are in the prepared state.
  • 在迁移完成之后,评估经典部署模型中 IaaS 资源上配置的基于角色的访问控制 (RBAC) 策略并准备好计划。Evaluate the Role-Based Access Control (RBAC) policies that are configured on the IaaS resources in the classic deployment model, and plan for after the migration is complete.

迁移工作流如下所示:The migration workflow is as follows:

显示迁移工作流的图

备注

以下部分描述的操作全都是幂等的。The operations described in the following sections are all idempotent. 如果遇到功能不受支持或配置错误以外的问题,请重试准备、中止或提交操作。If you have a problem other than an unsupported feature or a configuration error, retry the prepare, abort, or commit operation. Azure 会再次尝试此操作。Azure tries the action again.

验证Validate

验证操作是迁移过程中的第一个步骤。The validate operation is the first step in the migration process. 此步骤的目的是分析要在经典部署模型中迁移的资源的状态。The goal of this step is to analyze the state of the resources you want to migrate in the classic deployment model. 操作会评估资源能否进行迁移(成功或失败)。The operation evaluates whether the resources are capable of migration (success or failure).

可选择需要进行迁移验证的虚拟网络或云服务(如果不在虚拟网络中)。You select the virtual network or a cloud service (if it’s not in a virtual network) that you want to validate for migration. 如果资源不能迁移,Azure 会列出原因。If the resource is not capable of migration, Azure lists the reasons why.

不在验证操作中进行的检查Checks not done in the validate operation

验证操作仅分析经典部署模型中资源的状态。The validate operation only analyzes the state of the resources in the classic deployment model. 它可以查看因经典部署模型中配置的不同而导致的所有失败方案和不支持的方案。It can check for all failures and unsupported scenarios due to various configurations in the classic deployment model. 它不能检查 Azure 资源管理器堆栈对迁移过程中的资源造成的所有问题。It is not possible to check for all issues that the Azure Resource Manager stack might impose on the resources during migration. 仅当资源在下一步的迁移过程(准备操作)中进行转换时,才会检查是否存在这些问题。These issues are only checked when the resources undergo transformation in the next step of migration (the prepare operation). 下表列出了不在验证操作中检查的所有问题:The following table lists all the issues not checked in the validate operation:

不在验证操作中进行的网络检查Networking checks not in the validate operation
虚拟网络同时具有 ER 和 VPN 网关A virtual network having both ER and VPN gateways.
虚拟网关连接处于断开状态。A virtual network gateway connection in a disconnected state.
所有 ER 线路都预先迁移到 Azure 资源管理器堆栈。All ER circuits are pre-migrated to Azure Resource Manager stack.
Azure 资源管理器配额检查网络资源。Azure Resource Manager quota checks for networking resources. 例如:静态公共 IP、动态公共 IP、负载均衡器、网络安全组、路由表、网络接口。For example: static public IP, dynamic public IPs, load balancer, network security groups, route tables, and network interfaces.
在整个部署和虚拟网络中,所有负载均衡器规则都有效。All load balancer rules are valid across deployment and the virtual network.
同一 VNET 中处于“已停止-已取消分配”状态的 VM 之间存在专用 IP 冲突。Conflicting private IPs between stop-deallocated VMs in the same virtual network.

准备Prepare

准备操作是迁移过程中的第二个步骤。The prepare operation is the second step in the migration process. 此步骤的目的是模拟将 IaaS 资源从经典部署模型资源转换为资源管理器资源的过程。The goal of this step is to simulate the transformation of the IaaS resources from the classic deployment model to Resource Manager resources. 此外,准备操作还以并排方式让此转换过程直观可见。Further, the prepare operation presents this side-by-side for you to visualize.

备注

不会在这一步修改经典部署模型中的资源。Your resources in the classic deployment model are not modified during this step. 若要尝试迁移,这是可以运行的安全步骤。It's a safe step to run if you're trying out migration.

可选择需要进行迁移准备的虚拟网络或云服务(如果不是虚拟网络)。You select the virtual network or the cloud service (if it’s not a virtual network) that you want to prepare for migration.

  • 如果资源无法迁移,Azure 会停止迁移过程,并列出准备操作失败的原因。If the resource is not capable of migration, Azure stops the migration process and lists the reason why the prepare operation failed.
  • 如果资源可迁移,Azure 会锁定进行迁移的资源的管理平面操作。If the resource is capable of migration, Azure locks down the management-plane operations for the resources under migration. 例如,无法将数据磁盘添加到进行迁移的 VM。For example, you are not able to add a data disk to a VM under migration.

然后,Azure 就会开始将迁移中资源的元数据从经典部署模型迁移到资源管理器模型。Azure then starts the migration of metadata from the classic deployment model to Resource Manager for the migrating resources.

准备操作完成之后,可以选择在经典部署模型和资源管理器模型中将资源可视化。After the prepare operation is complete, you have the option of visualizing the resources in both the classic deployment model and Resource Manager. 对于经典部署模型中的每项云服务,Azure 平台都会创建模式为 cloud-service-name>-Migrated 的资源组名称。For every cloud service in the classic deployment model, the Azure platform creates a resource group name that has the pattern cloud-service-name>-Migrated.

备注

不能选择针对已迁移资源(即标有“-Migrated”字样的资源)创建的资源组的名称。It is not possible to select the name of a resource group created for migrated resources (that is, "-Migrated"). 但是,可以在迁移完成后,使用 Azure 资源管理器的移动功能将资源移至所需的任何资源组。After migration is complete, however, you can use the move feature of Azure Resource Manager to move resources to any resource group you want. 有关详细信息,请参阅将资源移到新资源组或订阅For more information, see Move resources to new resource group or subscription.

下面的两个屏幕截图显示了准备操作成功后的结果。The following two screenshots show the result after a succesful prepare operation. 第一个屏幕截图显示包含原始云服务的资源组。The first one shows a resource group that contains the original cloud service. 第二个屏幕截图显示包含 Azure 资源管理器等效资源的新“-Migrated”资源组。The second one shows the new "-Migrated" resource group that contains the equivalent Azure Resource Manager resources.

显示原始云服务的屏幕截图

显示准备操作中的 Azure 资源管理器资源的屏幕截图

下面是在完成准备阶段以后,在幕后查看资源的情形。Here is a behind-the-scenes look at your resources after the completion of the prepare phase. 请注意,数据平面中的资源是相同的。Note that the resource in the data plane is the same. 它同时在管理平面(经典部署模型)和控制平面(资源管理器)中呈现。It's represented in both the management plane (classic deployment model) and the control plane (Resource Manager).

准备阶段图

备注

不属于经典部署模型中的虚拟网络的 VM 在此迁移阶段停止和解除分配。VMs that are not in a virtual network in the classic deployment model are stopped and deallocated in this phase of migration.

检查(手动或通过脚本)Check (manual or scripted)

在检查步骤中,可以选择使用前面下载的配置来验证迁移是否正常。In the check step, you have the option to use the configuration that you downloaded earlier to validate that the migration looks correct. 也可以登录到门户并抽查属性和资源,来验证元数据迁移是否正常。Alternatively, you can sign in to the portal, and spot check the properties and resources to validate that metadata migration looks good.

如果迁移的是虚拟网络,大多数虚拟机配置不会重新启动。If you are migrating a virtual network, most configuration of virtual machines is not restarted. 对于这些 VM 上的应用程序,可以验证应用程序是否仍在运行。For applications on those VMs, you can validate that the application is still running.

可以测试监视和操作脚本,以查看 VM 是否按预期运行,以及更新后的脚本是否正常运行。You can test your monitoring and operational scripts to see if the VMs are working as expected, and if your updated scripts work correctly. 仅当资源处于准备就绪状态时,才支持 GET 操作。Only GET operations are supported when the resources are in the prepared state.

可以慢慢考虑是否要提交迁移,因为系统对此并没有时间限制。There is no set window of time before which you need to commit the migration. 可以在此状态下停留任何时间。You can take as much time as you want in this state. 但是,这些资源的管理平面会遭到锁定,直到中止或提交为止。However, the management plane is locked for these resources until you either abort or commit.

如果发现任何问题,始终可以中止迁移,并返回到经典部署模型。If you see any issues, you can always abort the migration and go back to the classic deployment model. 在你返回后,Azure 会打开资源的管理平面操作,使你可以继续在经典部署模型中对这些 VM 执行正常操作。After you go back, Azure opens the management-plane operations on the resources, so that you can resume normal operations on those VMs in the classic deployment model.

中止Abort

这是可选步骤,用于还原对经典部署模型所做的更改,并停止迁移。This is an optional step if you want to revert your changes to the classic deployment model and stop the migration. 对于资源,此操作会删除资源管理器元数据(在准备步骤中创建)。This operation deletes the Resource Manager metadata (created in the prepare step) for your resources.

中止步骤图

备注

触发提交操作后,就无法执行此操作。This operation can't be done after you have triggered the commit operation.

提交Commit

完成验证之后,就可以提交迁移。After you finish the validation, you can commit the migration. 资源不再出现在经典部署模型中,只在资源管理器部署模型中提供。Resources do not appear anymore in the classic deployment model, and are available only in the Resource Manager deployment model. 只能在新门户中管理迁移的资源。The migrated resources can be managed only in the new portal.

备注

这是幂等操作。This is an idempotent operation. 如果失败,请重试操作。If it fails, retry the operation. 如果仍失败,请创建支持票证,或在 VM 论坛上创建标记为“ClassicIaaSMigration”的论坛帖子。If it continues to fail, create a support ticket or create a forum post with a "ClassicIaaSMigration" tag on our VM forum.

提交步骤图

迁移流程图Migration flowchart

下面是一个流程图,说明了如何进行迁移:Here is a flowchart that shows how to proceed with migration:

显示迁移步骤的屏幕截图

从经典部署模型资源转换为资源管理器资源Translation of the classic deployment model to Resource Manager resources

可以在下表中找到资源的经典部署模型与资源管理器表示形式。You can find the classic deployment model and Resource Manager representations of the resources in the following table. 目前不支持其他功能和资源。Other features and resources are not currently supported.

经典表示形式Classic representation Resource Manager 表示形式Resource Manager representation 说明Notes
云服务名称Cloud service name DNS 名称DNS name 在迁移期间,会以命名模式 <cloudservicename>-migrated 为每个云服务创建新的资源组。During migration, a new resource group is created for every cloud service with the naming pattern <cloudservicename>-migrated. 此资源组包含用户的所有资源。This resource group contains all your resources. 云服务名称会成为与公共 IP 地址关联的 DNS 名称。The cloud service name becomes a DNS name that is associated with the public IP address.
虚拟机Virtual machine 虚拟机Virtual machine VM 特定属性将原封不动地进行迁移。VM-specific properties are migrated unchanged. 某些 osProfile 信息(例如计算机名称)不会存储在经典部署模型中,因此迁移后会保留空白。Certain osProfile information, like computer name, is not stored in the classic deployment model, and remains empty after migration.
附加到 VM 的磁盘资源Disk resources attached to VM 附加到 VM 的隐式磁盘Implicit disks attached to VM 在 Resource Manager 部署模型中,磁盘不会建模为顶级资源。Disks are not modeled as top-level resources in the Resource Manager deployment model. 这些磁盘将作为 VM 下的隐式磁盘进行迁移。They are migrated as implicit disks under the VM. 目前只支持附加到 VM 的磁盘。Only disks that are attached to a VM are currently supported. 资源管理器 VM 现在可以使用经典部署模型中的存储帐户轻松地迁移磁盘,不需任何更新。Resource Manager VMs can now use storage accounts in the classic deployment model, which allows the disks to be easily migrated without any updates.
VM 扩展VM extensions VM 扩展VM extensions 除 XML 扩展以外的所有资源扩展都会从经典部署模型中迁移。All the resource extensions, except XML extensions, are migrated from the classic deployment model.
虚拟机证书Virtual machine certificates Azure 密钥保管库中的证书 Certificates in Azure Key Vault 如果云服务包含服务证书,迁移会为每个云服务创建新的 Azure Key Vault,并将证书移到该 Key Vault。If a cloud service contains service certificates, the migration creates a new Azure key vault per cloud service, and moves the certificates into the key vault. VM 将更新为引用该密钥保管库中的证书。The VMs are updated to reference the certificates from the key vault.

请勿删除该 Key Vault。Do not delete the key vault. 这可能导致 VM 进入故障状态。This can cause the VM to go into a failed state.
WinRM 配置WinRM configuration osProfile 下的 WinRM 配置WinRM configuration under osProfile Windows 远程管理配置在迁移过程中会原封不动地进行转移。Windows Remote Management configuration is moved unchanged, as part of the migration.
可用性集属性Availability-set property 可用性集资源Availability-set resource 可用性集规范是经典部署模型中 VM 上的属性。Availability-set specification is a property on the VM in the classic deployment model. 在迁移过程中,可用性集将成为顶级资源。Availability sets become a top-level resource as part of the migration. 以下配置不受支持:每个云服务包含多个可用性集,或者在一个云服务中有一个或多个可用性集以及不在任何可用性集中的 VM。The following configurations are not supported: multiple availability sets per cloud service, or one or more availability sets along with VMs that are not in any availability set in a cloud service.
VM 上的网络配置Network configuration on a VM 主网络接口Primary network interface 在迁移后,VM 上的网络配置会表示为主网络接口资源。Network configuration on a VM is represented as the primary network interface resource after migration. 对于不在虚拟网络中的 VM,内部 IP 地址在迁移期间会更改。For VMs that are not in a virtual network, the internal IP address changes during migration.
VM 上的多个网络接口Multiple network interfaces on a VM 网络接口Network interfaces 如果 VM 有多个关联的网络接口,则在迁移过程中,每个网络接口以及所有属性都会成为顶级资源。If a VM has multiple network interfaces associated with it, each network interface becomes a top-level resource as part of the migration, along with all the properties.
负载均衡的终结点集Load-balanced endpoint set 负载均衡器Load balancer 在经典部署模型中,平台已经为每个云服务分配一个隐式负载均衡器。In the classic deployment model, the platform assigned an implicit load balancer for every cloud service. 在迁移期间,将创建新的负载均衡器资源,负载均衡终结点集将成为负载均衡器规则。During migration, a new load-balancer resource is created, and the load-balancing endpoint set becomes load-balancer rules.
入站 NAT 规则Inbound NAT rules 入站 NAT 规则Inbound NAT rules 在迁移期间,VM 上定义的输入终结点将转换成负载均衡器下的入站网络地址转换规则。Input endpoints defined on the VM are converted to inbound network address translation rules under the load balancer during the migration.
VIP 地址VIP address 具有 DNS 名称的公共 IP 地址Public IP address with DNS name 虚拟 IP 地址会变成公共 IP 地址并与负载均衡器关联。The virtual IP address becomes a public IP address, and is associated with the load balancer. 虚拟机 IP 仅在已向其分配了输入终结点的情况下才能迁移。A virtual IP can only be migrated if there is an input endpoint assigned to it.
虚拟网络Virtual network 虚拟网络Virtual network 虚拟网络将连同其所有属性一起迁移到 Resource Manager 部署模型。The virtual network is migrated, with all its properties, to the Resource Manager deployment model. 将创建名为 -migrated 的新资源组。A new resource group is created with the name -migrated.
保留 IPReserved IPs 具有静态分配方法的公共 IP 地址Public IP address with static allocation method 与负载均衡器关联的保留 IP 会在迁移云服务或虚拟机的过程中一起迁移。Reserved IPs associated with the load balancer are migrated, along with the migration of the cloud service or the virtual machine. 目前不支持进行未关联的保留 IP 迁移。Unassociated reserved IP migration is not currently supported.
每个 VM 的公共 IP 地址Public IP address per VM 具有动态分配方法的公共 IP 地址Public IP address with dynamic allocation method 与 VM 关联的公共 IP 地址将转换为公共 IP 地址资源,分配方法将设置为静态。The public IP address associated with the VM is converted as a public IP address resource, with the allocation method set to static.
NSGNSGs NSGNSGs 在迁移到 Resource Manager 部署模型的过程中,将克隆与子网关联的网络安全组。Network security groups associated with a subnet are cloned as part of the migration to the Resource Manager deployment model. 在迁移期间不会删除经典部署模型中的 NSG。The NSG in the classic deployment model is not removed during the migration. 但是,当迁移正在进行时,会阻止 NSG 的管理平面操作。However, the management-plane operations for the NSG are blocked when the migration is in progress.
DNS 服务器DNS servers DNS 服务器DNS servers 与虚拟网络或 VM 关联的 DNS 服务器会在迁移相应资源的过程中连同所有属性一起迁移。DNS servers associated with a virtual network or the VM are migrated as part of the corresponding resource migration, along with all the properties.
UDRUDRs UDRUDRs 在迁移到 Resource Manager 部署模型的过程中,将克隆与子网关联的用户定义路由。User-defined routes associated with a subnet are cloned as part of the migration to the Resource Manager deployment model. 在迁移期间不会删除经典部署模型中的 UDR。The UDR in the classic deployment model is not removed during the migration. 但是,当迁移正在进行时,会阻止 UDR 的管理平面操作。The management-plane operations for the UDR are blocked when the migration is in progress.
VM 网络配置中的 IP 转发属性IP forwarding property on a VM's network configuration NIC 中的 IP 转发属性IP forwarding property on the NIC VM 上的 IP 转发属性在迁移期间将转换为网络接口上的属性。The IP forwarding property on a VM is converted to a property on the network interface during the migration.
具有多个 IP 的负载均衡器Load balancer with multiple IPs 具有多个公共 IP 资源的负载均衡器Load balancer with multiple public IP resources 与负载均衡器关联的每个公共 IP 都会转换为公共 IP 资源,并在迁移后与负载均衡器关联。Every public IP associated with the load balancer is converted to a public IP resource, and associated with the load balancer after migration.
VM 上的内部 DNS 名称Internal DNS names on the VM NIC 上的内部 DNS 名称Internal DNS names on the NIC 在迁移期间,VM 的内部 DNS 后缀将迁移到 NIC 上名为“InternalDomainNameSuffix”的只读属性。During migration, the internal DNS suffixes for the VMs are migrated to a read-only property named “InternalDomainNameSuffix” on the NIC. 在迁移后,该后缀会保持不变,并且 VM 解决方案会继续像以前一样正常工作。The suffix remains unchanged after migration, and VM resolution should continue to work as previously.
虚拟网络网关Virtual network gateway 虚拟网络网关Virtual network gateway 虚拟网关属性会原封不动地进行迁移。Virtual network gateway properties are migrated unchanged. 与网关关联的 VIP 也不会更改。The VIP associated with the gateway does not change either.
本地网络站点Local network site 本地网络网关Local network gateway 本地网络站点属性将原封不动地迁移到名为“本地网关”的新资源。Local network site properties are migrated unchanged to a new resource called a local network gateway. 这表示本地地址前缀和远程网关 IP。This represents on-premises address prefixes and the remote gateway IP.
连接引用Connections references 连接Connection 网络配置中网关和本地网络站点之间的连接引用由名为“连接”的新资源表示。Connectivity references between the gateway and the local network site in network configuration is represented by a new resource called Connection. 网络配置文件中连接引用的所有属性会原封不动地复制到“连接”资源。All properties of connectivity reference in network configuration files are copied unchanged to the Connection resource. 创建两个到本地网络站点(代表虚拟网络)的 IPsec 隧道即可在经典部署模型中的虚拟网络之间进行连接。Connectivity between virtual networks in the classic deployment model is achieved by creating two IPsec tunnels to local network sites representing the virtual networks. 无需本地网关,即可将此连接转换为资源管理器模型中的“虚拟网络到虚拟网络”连接类型。This is transformed to the virtual-network-to-virtual-network connection type in the Resource Manager model, without requiring local network gateways.

自动化与工具在迁移之后的变化Changes to your automation and tooling after migration

在将资源从经典部署模型迁移到资源管理器部署模型的过程中,必须更新现有的自动化或工具,确保其在迁移之后仍可继续运行。As part of migrating your resources from the classic deployment model to the Resource Manager deployment model, you must update your existing automation or tooling to ensure that it continues to work after the migration.

后续步骤Next steps