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 article lists Azure Virtual Machine (VM) sizes scheduled for retirement in 2025, along with recommended replacement options and migration guidance.
Important
Retirement plans can change. Always validate the latest availability for your region and subscription before making changes.
List of retiring VM sizes
Use the following tables to identify impacted VM sizes.
FPGA-accelerated sizes
| VM size family | Affected sizes | Retirement date | Suggested replacement | Migration article | Notes |
|---|---|---|---|---|---|
| NP-series | All sizes | 2027-05-31 | NDv2, NCads_H100_v5, NCasT4_v3 | Retirement info | 1- and 3-year purchases end April 2, 2026 |
High Performance Compute sizes
| VM size family | Affected sizes | Retirement date | Suggested replacement | Migration article | Notes |
|---|---|---|---|---|---|
| HC-series | All sizes | 2027-05-31 | HBv5, HBv4, HX, HBv3 | Retirement info | 1- and 3-year purchases end April 2, 2026 |
| HBv2-series | All sizes | 2027-05-31 | HBv5, HBv4, HX, HBv3 | Retirement info | 1- and 3-year purchases end April 2, 2026 |
Retirement timeline
Azure has announced the retirement of these VM sizes effective on the dates specified in the table above. The announcement was made to allow sufficient time for planning and migration. End of sale for these sizes will occur prior to the retirement date, after which new purchases will no longer be available. Upon the retirement date, existing VMs running these sizes will be subject to deallocation, and Azure will no longer provide support or maintenance for these VM families.
Impact
If you use a retiring VM size, you might be affected in the following ways:
- New deployments of the retiring size may be blocked after the retirement date.
- Existing VMs may need to be resized or migrated to remain supported.
Recommended actions
- Identify VMs using the retiring sizes.
- Choose a replacement size that meets your requirements.
- Resize test workloads first, then schedule production changes.
- Validate performance, networking, extensions, and availability zone support after resizing.
Note
Some replacement sizes may not be available in all regions.
Support
If you need help planning or executing a migration, contact Azure support.