End of Support for D, Ds, Dv2, Dsv2, and Ls Series Azure Virtual Machines

Microsoft has announced the retirement of several Azure virtual machine (short VM) series, including D, Ds, Dv2, Dsv2, and Ls, as part of the upcoming Azure VM Series Retirement 2028. To avoid your workloads from being distrusted (like your AVD session hosts), you need to migrate your applications and workloads to newer VM series before the retirement date (you still got time!). This transition allows you to leverage improved price to performance ratios, better regional availability, and the latest hardware capabilities.

Update Overview

You must migrate all of your “old VMs” to newer VM series before the 1st of May 2028. This proactive approach ensures you leverage improved performance, greater regional availability, and the latest hardware features.

Impacted VM Series

• D series
• Ds series
• Dv2 series
• Dsv2 series
• Ls series

Recommended Actions

To maintain your VM workloads uninterrupted, take the following steps:

1. Evaluate current VMs:
   • Assess your current VM’s workload and performance requirements.
2. Select replacement VMs:
   • Reference the VM size documentation to identify compatible VM sizes (more to that below).
3. Request quota increases:
   • Verify and request necessary quota increases via the Azure portal.
4. Resize VMs:
   • Use the Azure portal, Azure CLI, or PowerShell to resize and migrate your VMs. Please be cautious when migrating your VMs. It is crucial to back up your workloads before proceeding to avoid any potential data loss. Better to be safe than sorry! Here is a short guide to resizing via the Azure portal:
     • Stop (deallocate) the VM.
     • Resize to the selected VM series.
     • Start the VM after resizing.
5. Review billing implications:
   • Check potential changes to billing on the Azure Virtual Machines pricing page (Windows) or Azure Virtual Machines pricing page (Linux).
6. Review your automation scripts:
   • If you’re using Bicep or Terraform to deploy or manage your workloads, changes to your code will be necessary. Ensure you update the resource definitions and configurations to align with the new VM series.

Recommended Replacement VM Series

*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, newer v5 and v6 VM series are recommended. These series provide Premium Storage, Accelerated Networking, and Nested Virtualization, among other features. However, for certain conditions you may choose v4 series VMs, such as:

• NVMe requirements.
• Generation 2 VM support.
• Microsoft Azure Network Adapter (short MANA) and a MANA-supported operating system.
• Regional capacity limitations.

Key Considerations and Common Concerns

As you plan for this migration, you might have several questions and concerns. Here are some common questions you will surely ask yourself and important points to consider:

Which Sizes Are Being Retired?

Various sizes within the D, Ds, Dv2, Dsv2, and Ls series are being phased out. This includes sizes ranging from Standard_D1 to Standard_D15 v2, as well as Standard_L4s to Standard_L32s. For a detailed list, you can refer to the documentation.

Why Should I Migrate?

Migrating is essential to avoid unexpected service disruptions as these VM series will no longer be supported past the 1st of May 2028. Beyond this, migrating offers numerous benefits:

• Performance: The newer VM series provides significantly enhanced price-to-performance ratios, ensuring better efficiency for your workloads.
• Regional Availability: The latest VM series are more widely available across Azure data centers, providing more flexibility and redundancy options.
• Future-proofing: By transitioning now, you prepare your infrastructure for future advancements and potential needs, minimizing the risk of sudden disruptions.

I am on Pay-As-You-Go (PayGo) or Savings Plan Pricing. Will Migration Affect My Billing?

Not at all. If you’re utilizing PayGo or a savings plan, transitioning to newer VM types will seamlessly integrate into your existing billing structure. Your subscription and payment plans remain unaffected, ensuring continuity without extra administrative work. The same is for the CSP billing type.

I’m on Reserved Instances (short RIs) with an Older VM. How Should I Handle Migration?

For those with active RIs for D, Dv2, Dsv2, or L-series VMs, specific steps can facilitate a smoother transition:

1. Review Current Reservations:
   • Check your active RIs in the Azure portal. Identify which reservations are nearing expiration or will be impacted by the retirement.
2. Exchange Existing Reservations:
   • You have the option to swap current RIs for new VM series without incurring penalties. This can be done through the RI Exchange Guide. If you’re using the CSP billing type, contact your CSP for that matter.
3. Trade-In for Savings Plan:
   • Convert your existing RIs into an Azure Savings Plan for compute. This offers flexibility across various VM families and regions, as outlined in the Azure RI Trade-In Tutorial. If you’re using the CSP billing type, contact your CSP for that matter.
4. Purchase New RIs:
   • Buy new reservations that are compatible with the v6 VM series you’re transitioning to. Opting for shorter terms, like a 1-year period, could provide added flexibility.

Conclusion

This transition is crucial for the reliability and performance of your Azure environments. By migrating to newer VM series before the deadline, you’ll not only avoid service disruptions but also take advantage of enhanced capabilities and cost-efficiency.

Don’t wait until the last minute—start planning your migration today to ensure smooth and seamless continuity of your services. 

Additional Resources

For detailed migration guides and further assistance, refer to the Azure Virtual Machines Migration Guide page.