> 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/advisor-savings-higher-than-archera.md).

# Why Is Azure Advisor's Savings Figure Higher Than Archera's?

Azure Advisor sizes its recommendation to the lookback window and term you select, and it offers both reservation and savings plan recommendations for the same workload. Those are alternatives, not additions.

## Where the Double Count Comes From

A reservation recommendation and a savings plan recommendation covering the same usage cannot both be purchased for full value — buy one and the other's savings largely disappear. Adding the two figures together, or comparing Advisor's 3-year number against a 1-year Archera plan, counts the same savings twice.

## What Archera Reports Instead

We recommend one commitment per unit of usage, and we report savings **net of any Guaranteed Commitment premium**. Expect our figure to be lower than an Advisor total and closer to what lands on your bill.

If you want to compare like for like, set Advisor to the same term as the Archera plan and read only the reservation *or* the savings plan recommendation — not both.

## Related Resources

* [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)
* [What Reservable Azure Services Does Archera Insure?](https://docs.archera.ai/help-center/azure-faq/reservable-services.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/advisor-savings-higher-than-archera.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.
