Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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.
Recommended Replacement VM Series
| Current VM Series | Target VM Series | Differences in Specification in Target VM* |
|---|---|---|
| D Ds Dv2 Dsv2 |
Dsv5/Ddsv5/Dasv5/Dadsv5 Dasv6/Dadsv6/Dsv6/Ddsv6 Dasv7/Dadsv7 Esv6/Edsv6/Easv6/Eadsv6 Easv7/Eadsv7 |
D/Ev5 disk controller type: SCSI D/Ev6, D/Ev7 disk controller type: NVMe Local Storage Throughput: 9000 IOPS / 125 MBps Remote Storage Throughput: 3750 IOPS / 82 MBps |
| Ls | Lsv3/Lasv3 Lsv4/Lasv4 |
Local Storage: Supported - NVMe Remote Storage Throughput: 12800 IOPS / 200 MBps Disk Controller Type: SCSI and NVMe |
| Av2 Amv2 |
Bsv2/Bpsv2/Basv2 Dsv5/Ddv5/Dasv5/Dpsv5 Esv5/Edv5/Easv5/Epsv5 Dsv6/Ddsv6/Dasv6/Dpsv6 Esv6/Edsv6/Easv6/Epsv6 |
B/Bp/Bav2, D/Ev5 disk controller type: SCSI D/Ev6 disk controller type: NVMe Remote Storage Throughput: 3750 IOPS / 85 MBps |
| B | Bsv2/Bpsv2/Basv2 Dlsv5/Dldsv5/Dalsv5/Daldsv5 Dlsv6/Dldsv6/Dalsv6/Daldsv6 |
B/Bp/Bav2, D/Ev5 disk controller type: SCSI D/Ev6 disk controller type: NVMe Remote Storage Throughput: 3750 IOPS / 85 MBps Disk Controller Type: SCSI |
| F Fs Fsv2 |
Dlsv6/Dldsv6/Dalsv6/Daldsv6 Falsv6 Dldsv5/Dlsv5/Dsv5/Ddsv5 |
D/Ev5 disk controller type: SCSI D/Ev6 disk controller type: NVMe Remote Storage Throughput: 4167 IOPS / 124 MBps |
| G Gs |
Lsv3/Lasv3 Lsv4/Lasv4 |
Lv3/Lv4 controller type: SCSI and NVMe Remote Storage Throughput: 12800 IOPS / 200 MBps |
| Lsv2 | Lsv3/Lasv3 Lasv4/Lasv4 |
Local Storage: NVMe Remote Storage Throughput: 12800 IOPS / 200 MBps Disk Controller Type: SCSI and NVMe |
*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.
*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.
Important
The following SKUs aren't available in the Sovereign clouds: Bsv2, Bpsv2, Basv2
Recommended Replacement Isolated VM Sizes
| Current VM Size | Target VM Sizes | Differences in Specification in Target VM* |
|---|---|---|
| Standard_E64i_v3 Standard_E64is_v3 |
Standard_E192is_v6 Standard_E192ids_v6 Standard_E104i_v5 Standard_E104id_v5 Standard_E104is_v5 Standard_E104ids_v5 Standard_E80is_v4 Standard_E80ids_v4 |
Local Storage: Supported - NVMe Local Storage Throughput: 37,500 IOPS / 180 MBps Remote Storage Throughput: 3,750 IOPS / 106 MBps Disk Controller Type: NVMe |
*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 and v6 VM series. This ensures you have access to the latest features such as Premium Storage, Accelerated Networking, and Nested Virtualization. While the v6 VM series is preferred, there are certain scenarios where you might want to consider the v5 or even the v4 VM series. Here are some reasons why:
- v6 VMs require enabling NVMe which means that you must have a supported OS.
- v6 VMs support Generation 2 VMs only.
- v6 VMs require MANA (Microsoft Azure Network Adapter) and a MANA supported operating system.
- v6 VMs may not have available capacity in the regions and zones you need.
Note that Lsv4 and Lasv4 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 v6 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:
- Stop (deallocate) the VM.
- Resize the VM to your selected v6 series.
- 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 |
| Lsv2 | 11/15/2025 | 11/15/2027 | 11/15/2028 |
| G | 11/15/2025 | 11/15/2027 | 11/15/2028 |
| Gs | 11/15/2025 | 11/15/2027 | 11/15/2028 |
| Av2 | 11/15/2025 | 11/15/2027 | 11/15/2028 |
| Amv2 | 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 and v6 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
- Check your active RIs in the Azure portal.
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:
Exchange Existing Reservations:
Swap current RIs for a new VM series without any penalties.
Refer to the RI Exchange Guide
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.
Purchase New RIs:
Buy new reservations that align with your new v6 VM series.
Consider shorter terms (1-year) for flexibility.