Migrate your IaaS resources to Azure Resource Manager by March 1, 2023

Applies to: ✔️ Linux VMs ✔️ Windows VMs

In 2014, we launched infrastructure as a service (IaaS) on Azure Resource Manager. We've been enhancing capabilities ever since. Because Azure Resource Manager now has full IaaS capabilities and other advancements, we deprecated the management of IaaS virtual machines (VMs) through Azure Service Manager (ASM) on February 28, 2020. This functionality will be fully retired on March 1, 2023.

Today, about 90 percent of the IaaS VMs are using Azure Resource Manager. If you use IaaS resources through ASM, start planning your migration now. Complete it by March 1, 2023, to take advantage of Azure Resource Manager.

VMs created using the classic deployment model will follow the Modern Lifecycle Policy for retirement.

How does this affect me?

  • As of February 28, 2020, customers who didn't utilize IaaS VMs through ASM in the month of February 2020 can no longer create VMs (classic).
  • On March 1, 2023, customers will no longer be able to start IaaS VMs by using ASM. Any that are still running or allocated will be stopped and deallocated.
  • On March 1, 2023, subscriptions that are not migrated to Azure Resource Manager will be informed regarding timelines for deleting any remaining VMs (classic).

This retirement does not affect the following Azure services and functionality:

  • Storage accounts not used by VMs (classic)
  • Virtual networks not used by VMs (classic)
  • Other classic resources

Azure Cloud Services (classic) retirement was announced in August 2021 here

What resources are available for this migration?

  • Microsoft Q&A: Microsoft and community support for migration.

  • Azure Migration Support: Dedicated support team for technical assistance during migration. Customers without technical support can use free support capability provided specifically for this migration.

  • Microsoft Fast Track: Fast track can assist eligible customers with planning & execution for this migration. Nominate yourself for DC Migration Program.

  • If your company/organization has partnered with Microsoft or works with Microsoft representatives (like cloud solution architects (CSAs) or technical account managers (TAMs)), please work with them for additional resources for migration.

What actions should I take?

Start planning your migration to Azure Resource Manager, today.

  1. Make a list of all affected VMs:

    • The VMs of type virtual machines (classic) on the Azure portal's VM pane are all the affected VMs within the subscription.
    • You can also query Azure Resource Graph by using the portal or PowerShell to view the list of all flagged VMs (classic) and related information for the selected subscriptions.
    • On February 8 and September 2, 2020, we sent out emails with subject "Start planning your IaaS VM migration to Azure Resource Manager" to subscription owners. The email provides a list of all subscriptions and VMs (classic) VMs in it. Please use them to build this list.
  2. Learn more about migrating your Linux and Windows VMs (classic) to Azure Resource Manager. For more information, see Frequently asked questions about classic to Azure Resource Manager migration.

  3. We recommend starting the planning by using the platform support migration tool to migrate your existing VMs with three easy steps: validate, prepare, and commit. The tool is designed to migrate your VMs within minimal to no downtime.

    • The first step, validate, has no impact on your existing deployment and provides a list of all unsupported scenarios for migration.
    • Go through the list of workarounds to fix your deployment and make it ready for migration.
    • Ideally after all validation errors are fixed, you should not encounter any issues during the prepare and commit steps. After the commit is successful, your deployment is live migrated to Azure Resource Manager and can then be managed through new APIs exposed by Azure Resource Manager.

    If the migration tool is not suitable for your migration, you can explore other compute offerings for the migration. Because there are many Azure compute offerings, and they're different from one another, we can't provide a platform-supported migration path to them.

  4. For technical questions, issues, and help with adding subscriptions to the allowlist, contact support.

  5. Complete the migration as soon as possible to prevent business impact and to take advantage of the improved performance, security, and new features of Azure Resource Manager.