General Purpose Sizes Migration Guide

This migration guide is designed for users of Azure General Purpose virtual machines (VMs), which are scheduled for retirement. To ensure minimal disruption and to continue optimizing cost and performance, this guide helps you transition to the latest series VMs.

This document 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 Differences in Specification in Target VM*
D
Ds
Dv2
Dsv2
Dasv5
Dsv5
Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 82 MBps
Disk Controller Type: SCSI
D
Ds
Dv2
Dsv2
Dadsv5
Ddsv5
Local Storage: Supported - SCSI
Local Storage Throughput: 9000 IOPS / 125 MBps
Remote Storage Throughput: 3750 IOPS / 82 MBps
Disk Controller Type: SCSI
Ls Lsv3
Lasv3
Local Storage: Supported - NVMe
Remote Storage Throughput: 12800 IOPS / 200 MBps
Disk Controller Type: SCSI
Current VM Family Target VM Family (for China East 2 or China North 2) Target VM Family (for China North 3) Differences in Specification in Target VM*
Av2
These VMs are not offered in diskful sizes
Bsv2 N/A Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 85 MBps
Disk Controller Type: SCSI
Av2
These VMs are not offered in diskful sizes
Dv3
Ev3
N/A Local Storage: Not Supported
Remote Storage Throughput: 3000 IOPS / 46 MBps
Disk Controller Type: SCSI
Av2
These VMs are not offered in diskful sizes
Dsv4
Ddv4
Esv4
N/A Local Storage: Not Supported
Remote Storage Throughput: 3200 IOPS / 48 MBps
Disk Controller Type: SCSI
Av2
These VMs are not offered in diskful sizes
N/A Dsv5
Ddv5
Dasv5
Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 85 MBps
Disk Controller Type: SCSI
Amv2
These VMs are not offered in diskful sizes
N/A Esv5
Edv5
Easv5
Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 85 MBps
Disk Controller Type: SCSI
B Bsv2 N/A Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 85 MBps
Disk Controller Type: SCSI
B Dsv4
Ddsv4
N/A Local Storage: Not Supported
Remote Storage Throughput: 3200 IOPS / 48 MBps
Disk Controller Type: SCSI
B N/A Dlsv5
Dldsv5
Dalsv5
Daldsv5
Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 85 MBps
Disk Controller Type: SCSI
F Dv3
Ev3
Esv3
N/A Local Storage: Not Supported
Remote Storage Throughput: 3000 IOPS / 46 MBps
Disk Controller Type: SCSI
F Dv4
Ddv4
N/A Local Storage: Not Supported
Remote Storage Throughput: 3200 IOPS / 48 MBps
Disk Controller Type: SCSI
F N/A Dldsv5
Dlsv5
Ddv5
Dv5
Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 85 MBps
Disk Controller Type: SCSI
FS Dv3
Ev3
Esv3
N/A Local Storage: Not Supported
Remote Storage Throughput: 3000 IOPS / 46 MBps
Disk Controller Type: SCSI
FS Dsv4
Ddsv4
N/A Local Storage: Not Supported
Remote Storage Throughput: 3200 IOPS / 48 MBps
Disk Controller Type: SCSI
FS N/A Dldsv5
Dlsv5
Ddv5
Dv5
Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 85 MBps
Disk Controller Type: SCSI
Fsv2 Ev3 N/A Local Storage: Not Supported
Remote Storage Throughput: 3000 IOPS / 46 MBps
Disk Controller Type: SCSI
Fsv2 Dsv4
Ev4
Edsv4
Ddsv4
Ev4
N/A Local Storage: Not Supported
Remote Storage Throughput: 3200 IOPS / 48 MBps
Disk Controller Type: SCSI
Fsv2 N/A Dldsv5
Dlsv5
Ddv5
Dv5
Local Storage: Not Supported
Remote Storage Throughput: 3750 IOPS / 85 MBps
Disk Controller Type: SCSI
G N/A Lsv3
Lasv3
Local Storage: Supported - NVMe
Remote Storage Throughput: 12800 IOPS / 200 MBps
Disk Controller Type: SCSI
Gs N/A Lsv3
Lasv3
Local Storage: Supported - NVMe
Remote Storage Throughput: 12800 IOPS / 200 MBps
Disk Controller Type: SCSI
Lsv2 N/A Lasv3 Local Storage: Supported - NVMe
Remote Storage Throughput: 12800 IOPS / 200 MBps
Disk Controller Type: SCSI

*Refers to the lowest VM size in the given target VM Family. For actual VM specifications, please refer to the VM product sizes page.

For optimal performance and experience, we generally 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.

Note that Lsv3 and Lasv3 series are the latest generation L-series VMs.

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?

The following sizes are being retired by 1 May 2028.

  • D/Ds series:
    • Standard_D1 to Standard_D4
    • Standard_DS1 to Standard_DS4
    • Standard_D11 to Standard_D14
    • Standard_DS11 to Standard_DS14
  • Dv2/Dsv2 series:
    • Standard_D1v2 to Standard_D5_v2
    • Standard_DS1v2 to Standard_DS5_v2
    • Standard_D11_v2 to Standard_D15_v2
    • Standard_DS11_v2 to Standard_DS15_v2
    • Standard_D2_v2_Promo to Standard_D5_v2_Promo
    • Standard_DS2_v2_Promo to Standard_DS5_v2_Promo
  • LS series:
    • Standard_L4s to Standard_L32s

Q: Why Should I Migrate?

If you are actively running any sizes listed in this article, these VMs are set to retire in 2028. 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: I am on pay-as-you-go (PayGo) or Savings Plan Pricing. Is There a Concern with Migration?

No. If you’re using PayGo 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: I'm on Reserved Instances (RIs) with an Older VM. How Do I Handle Migration?

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.