An Azure service that is used to provision Windows and Linux virtual machines.
Standard_DS3_v2 and Standard_DS4_v2 are part of the Dsv2 series.
From the migration guide FAQ table, the D-family series listed for retirement are:
- D
- Ds
- Dsv2
- Dv2
- Ls
For these series, the table shows:
- Dsv2 – 3-year RI expiration: 05/01/2025, 1-year RI expiration: 07/01/2026, Retirement Date: 05/01/2028.
So:
- Standard_DS3_v2 and Standard_DS4_v2 are Dsv2 sizes and are on the retirement list.
- They fall under the “Dsv2” row in the table.
- They will be retired on 05/01/2028; after that date, any VMs still on these sizes will be deallocated and stop working.
- For Dv3/Dsv3/Ev3/Esv3:
- The FAQ states: “Dv3, Dsv3, Ev3, and Esv3 are not being retired until further notice. However, three- and one-year reserved instances discounts will no longer be available for new purchases or renewals after July 1, 2026.”
- In the table, Dv3, Dsv3, Ev3, Esv3 all show “Product active” in the Retirement Date column.
- This means:
- Existing VMs on v3 sizes are still supported and not scheduled for retirement yet.
- But new or renewed 1-year and 3-year RIs for Dv3/Dsv3/Ev3/Esv3 won’t be available after 07/01/2026; workloads will fall back to pay-as-you-go unless moved to Savings Plan or to newer VM generations.
- For v4/v5/v6 sizes:
- The provided context only explicitly covers the D, Ds, Dv2, Dsv2, Dv3, Dsv3, Ev3, Esv3, and other listed series.
- It does not list v4/v5/v6 sizes as retired; they are the recommended migration targets from the retiring D/Ds/Dv2/Dsv2 and E-series:
- “If you are looking to migrate from Dv3/Dsv3, recommended VM series include Dsv5, Ddsv5, Dasv5, Dadsv5, Dsv6, Ddsv6, Dasv6, and Dadsv6.”
- “For Ev3/Esv3, recommended replacements include Esv5, Edsv5, Easv5, Eadsv5, Esv6, Edsv6, Easv6, and Eadsv6.”
- This supports the assumption that newer v5/v6 series are the supported next-gen options.
- Retirement behavior:
- When a VM size reaches its retirement date, “any remaining VMs in a retired series are deallocated, stop working, stop incurring charges, and no longer have SLA or support.”
- Managed disk data is preserved; to resume service, the VM must be resized to a supported size and restarted.
- What to do next for Standard_DS3_v2 / DS4_v2:
- Treat them as Dsv2 and plan migration before 05/01/2028.
- Use the migration guide’s recommendation to move to newer D-series generations (for example Dsv5/Ddsv5/Dasv5/Dadsv5 or Dsv6/Ddsv6/Dasv6/Dadsv6) based on workload requirements.
References: