> 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/bring-existing-reservations.md).

# Can I Bring My Existing Native Azure Reservations Into Archera?

Yes. Existing reservations appear in Commitment Inventory once your integration is connected, whether you bought them directly or through a partner.

## At Expiration

We can renew an expiring reservation as a native commitment or as a Guaranteed Commitment.

## Mid-Term Exchanges

An eligible native reservation can be exchanged into the longer native reservation that backs a Guaranteed Commitment.

* **No cancellation-limit cost.** Microsoft's **$50,000** rolling 12-month limit applies to refunds. The refund leg of an exchange [does not count against it](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations), and there's no penalty or annual cap on exchanges.
* **Value test.** The new reservation's total lifetime commitment must be equal to or greater than the **remaining** commitment on the one you return — not its original purchase price.
* **Same SKU not required.** The replacement can be a different SKU, series, or region within the same product family.
* **Term start.** An exchange starts a new term from the exchange date. The exception is swapping a VM size for its premium-storage counterpart or back — for example F1 to F1s — which keeps the original term.

Microsoft is restricting exchange eligibility from February 1, 2027. The rules, and what they do and don't affect, are covered separately.

## If You Buy Through a CSP

Microsoft does not permit a CSP customer to exchange, cancel, renew, or refund a reservation themselves — your partner must action it. We coordinate the request; the partner executes it.

## Related Resources

* [How Do Azure Reservation Exchanges Work, and What's Changing in February 2027?](https://docs.archera.ai/help-center/azure-faq/exchange-eligibility-and-2027-policy-change.md)
* [Does Archera Rely on Azure Exchanges or Returns Policy?](https://docs.archera.ai/help-center/azure-faq/exchanges-returns-policy.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/bring-existing-reservations.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.
