> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/azure-faq/legacy-vm-series-reservation-retirement.md).

# Microsoft Stopped Selling Reservations for Older VM Series. What Are My Options?

From **July 1, 2026**, Microsoft [no longer sells or renews](https://techcommunity.microsoft.com/blog/azurecompute/azure-reserved-vm-instances-for-select-vm-series-will-no-longer-be-available-sta/4516505) one-year reservations for Av2, Amv2, Bv1, D, Ds, Dv2, Dsv2, F, Fs, Fsv2, G, Gs, Ls, and Lsv2. One-year *and* three-year reservations also ended for Dv3, Dsv3, Ev3, and Esv3.

Existing reservations run to the end of their term. At expiry the VMs bill at pay-as-you-go rates **even if auto-renew is on**.

## Your Options

We can only purchase commitments Microsoft sells, so there are two paths: cover the workload with a compute savings plan, at a lower discount than a reservation, or migrate to a current VM series and reserve that.

## Which Path Depends on Your Series

**D, Ds, Dv2, Dsv2, and Ls retire on May 1, 2028; Av2, B, F, G, and Lsv2 by November 15, 2028.** At retirement these VMs are deallocated and lose SLA and support, so migration is required regardless of commitment strategy. Treat the reservation change as the prompt to start planning.

**Dv3, Dsv3, Ev3, and Esv3 are not scheduled for retirement.** They lost reservation eligibility only. A savings plan is a durable option here, and migration is a cost decision rather than a deadline.

## Related Resources

* [What does Azure RI 'Instance Size Flexibility' Mean?](https://docs.archera.ai/help-center/azure-faq/instance-size-flexibility.md)
* [Why Does Archera Recommend Azure Savings Plans by Default?](https://docs.archera.ai/help-center/azure-faq/why-savings-plans-over-reservations-for-azure-compute.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archera.ai/help-center/azure-faq/legacy-vm-series-reservation-retirement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
