Retired VM Sizes Migration Guide

This migration guide is designed for users of Azure General Purpose virtual machines (VMs), which are scheduled for retirement. This guide helps you transition to the latest VM series, helping you minimize disruptions while optimizing cost and performance.

This guide covers:

  • Recommended replacement VM series
  • Detailed migration steps
  • Common questions and guidance on handling RIs.

By migrating to newer VM series, you gain access to improved price-performance ratios, broader regional availability, and the latest hardware capabilities.

Current VM Family Target VM Family(for China North 2 or China East 2 regions) Target VM Family(for China North 3 or China East 3 regions) Differences in Specification in Target VM*(for target VM family *v5)
D
Ds
Dv2
Dsv2		 Dsv3
Dsv4		 Dasv5
Dsv5		 Local Storage: Not Supported
Remote Storage Throughput: 3750 – up to 80000 IOPS / 82 – up to 2600 MBps
Disk Controller Type: SCSI
D
Ds
Dv2
Dsv2		 Ddsv3
Ddsv4		 Dadsv5
Ddsv5		 Local Storage: Supported - SCSI
Local Storage Throughput: 9000 – up to 450000 IOPS (RR) / 125 – up to 4000 (RR) MBps
Remote Storage Throughput: 3750 – up to 80000 IOPS / 82 – up to 2600 MBps
Disk Controller Type: SCSI

*Refers to the smallest VM size in the given target VM series. Full VM specifications are available on each target VM series' product sizes page.

Current VM Family Target VM Family (for China North 2 or China East 2 regions) Target VM Family (for China North 3 or China East 3 regions)
Av2/Amv2 Bsv2/Dsv4/Ddv4/Esv4 Av2 - Dsv5/Ddv5/Dasv5/Bsv2/Basv2
Amv2 - Esv5/Edv5/Easv5/Bsv2/Basv2
B Bsv2/Dsv4/Ddsv4 Bsv2/Basv2/Dlsv5/Dldsv5/
Dalsv5/Daldsv5
F Dv4/Ddv4 Dldsv5/Dlsv5/Ddv5/Dv5
Fs Dsv4/Ddsv4 Dldsv5/Dlsv5/Ddv5/Dv5
Fsv2 Dsv4/Ev4/Edsv4/Ddsv4 Dldsv5/Dlsv5/Ddvs5/Dsv5

*Refers to the smallest VM size in the given target VM series. Full VM specifications are available on each target VM series' product sizes page.

For optimal performance and experience, we recommend using the newer v5 VM series. This ensures you have access to the latest features such as Premium Storage, Accelerated Networking, and Nested Virtualization.

Use the Azure VM size documentation to help identify suitable VM sizes.

Migration Steps

Optional: For Reserved Instance (RI) customers only

  • Review your current reservations using the Azure Reservation Management page.
  • If applicable, exchange existing reservations for newer VM series or trade in your reservations for an Azure Savings Plan for compute.

Identify the Target VM Size

  • Evaluate your current VM's workload and performance requirements.
  • Select a comparable size from the above table that meets your CPU, memory, and storage needs.

Check and Request Quota Increases

  • Before resizing, verify that your subscription has sufficient quota for the target v5 VM series.
  • Request more quota through the Azure portal if needed.

Resize the Virtual Machine

You can resize your VM through the Azure portal, Azure CLI, or PowerShell. Follow these steps:

  1. Stop (deallocate) the VM.
  2. Resize the VM to your selected v5 series.
  3. Start the VM after resizing.

Refer to the full Azure VM resizing guide for more detailed instructions.

FAQ

Q: Which sizes are being retired?

To review retired sizes, see retired Azure VM sizes. View retired isolated sizes at Isolation for VMs in Azure.

VM Series 3 YR RI expiration date 1 YR RI expiration date Retirement Date
D 05/01/2025 05/01/2027 05/01/2028
Ds 05/01/2025 05/01/2027 05/01/2028
Dv2 05/01/2025 05/01/2027 05/01/2028
Dsv2 05/01/2025 05/01/2027 05/01/2028
Ls 05/01/2025 05/01/2027 05/01/2028
F 11/15/2025 11/15/2027 11/15/2028
Fs 11/15/2025 11/15/2027 11/15/2028
Fsv2 11/15/2025 11/15/2027 11/15/2028
Av2 11/15/2025 11/15/2027 11/15/2028
B-series 11/15/2025 11/15/2027 11/15/2028

Q: Why should I migrate my VM?

Migration is mandatory to avoid unexpected shutdown. Additionally, migration yields the following benefits:

  • Performance: Newer VM series offer better price-to-performance ratios.
  • Regional Availability: The v5 series has broader regional support across Azure data centers.
  • Future-proofing: Migrate ahead of the retirement schedule to avoid disruption.

Q: What will happen to my VM if I do not resize my VM to a target size within the retirement timeline?

After retirement, VMs using this size will be deallocated and stop incurring charges. The size is no longer supported or covered by an SLA; in‑memory and temporary disk data is lost, but managed disk data is preserved. To resume service, you may resize to a supported size and restart the VM.

Q: Can I recover my VM after it has been deallocated?

Yes, you can resize and restart your deallocated VM following the Azure VM resizing guide.

Q: Will VM migration disrupt pay-as-you-go or Savings Plan Pricing billing?

No. If you’re using pay-as-you-go or a savings plan, migrating to a newer VM type won't disrupt your current billing. The migration process remains seamless with no changes required in your subscription or payment plan.

Q: How can I migrate my VM if I am on Reserved Instances (RIs) with a retired VM?

If you have active Reserved Instances for D, Dv2, Dsv2, or L-series VMs, follow these steps:

Step 1: Review Current Reservations

Identify which RIs are expiring or will be affected by the VM retirement.

Step 2: Migrate and Manage Your RIs

Depending on your business needs, consider these options:

  1. Exchange Existing Reservations:

    • Swap current RIs for a new VM series without any penalties.

    • Refer to the RI Exchange Guide

  2. Trade-In for Savings Plan:

    • Convert your existing RIs into an Azure Savings Plan for compute.

    • This offers flexibility across VM families and regions.

    • Follow the Azure RI Trade-In Tutorial.

  3. Purchase New RIs:

    • Buy new reservations that align with your new v5 VM series.

    • Consider shorter terms (1-year) for flexibility.

  • Last updated on