> 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/azure.md).

# Azure FAQ

Azure-specific questions about commitments, reservations, and using Archera with Azure.

* [What does Azure RI 'Instance Size Flexibility' Mean?](/help-center/azure-faq/instance-size-flexibility.md)
* [Does Archera Rely on Azure Exchanges or Returns Policy?](/help-center/azure-faq/exchanges-returns-policy.md)
* [How Do Azure Reservation Exchanges Work, and What's Changing in February 2027?](/help-center/azure-faq/exchange-eligibility-and-2027-policy-change.md)
* [Why Does Archera Recommend Azure Savings Plans by Default?](/help-center/azure-faq/why-savings-plans-over-reservations-for-azure-compute.md)
* [What Is the Billing Subscription for Azure Reservations and Savings Plans?](/help-center/azure-faq/billing-subscription-and-scope.md)
* [What Reservable Azure Services Does Archera Insure?](/help-center/azure-faq/reservable-services.md)
* [Is Azure SQL Database Reservable on DTU or Only vCore?](/help-center/azure-faq/sql-database-vcore-vs-dtu-reservations.md)
* [Does Archera Support Reservations for Azure Storage Disks?](/help-center/azure-faq/storage-disks.md)
* [Azure Storage Recommendations Not Showing](/help-center/azure-faq/storage-recommendations.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/azure.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.