> 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/what-happens-if-i-leave.md).

# What Happens to My Azure Commitments if I Stop Using Archera?

Your reservations and savings plans were purchased inside your own Azure organization. They stay live for their full remaining term regardless of what happens to your Archera relationship, and we have no mechanism to take them back.

So the question is never what happens to the commitment. It's whether the insurance stays on it — and that's a decision you make **per commitment**, not once for your whole portfolio.

## Option A — Remove the Insurance

A clean exit for commitments whose usage has settled:

* You keep the native commitments exactly as purchased
* No further premiums are charged
* No rebates either, if a commitment later goes underutilized
* Nothing to stay connected to once the change is made

## Option B — Keep the Rebate in Place

Better for commitments already underutilized, or where future usage is uncertain:

* The commitment continues its lifecycle as a normal Guaranteed Commitment
* You receive a monthly rebate when it is underutilized
* You pay a monthly premium when it is saving you money
* You must stay connected to the platform for this to work — we can't measure utilization or pay a rebate without the integration

## You Can Blend the Two

These are per-commitment decisions. Most customers remove the insurance where usage has settled and keep the rebate on the commitments they're still unsure about.

To remove our access to your tenant entirely, follow Azure Offboarding — but note that doing so ends Option B on every commitment, since the rebate depends on the integration staying live.

## Related Resources

* [Azure Offboarding](https://docs.archera.ai/help-center/azure-onboarding/offboarding/offboarding.md)
* [Can I Bring My Existing Native Azure Reservations Into Archera?](https://docs.archera.ai/help-center/azure-faq/bring-existing-reservations.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/what-happens-if-i-leave.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.
