> 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/instance-size-flexibility.md).

# What does Azure RI 'Instance Size Flexibility' Mean?

## Can I Upsize or Downsize Within the Same Instance Family?

Azure Standard RIs for VMs offer **instance size flexibility** meaning that regardless of the RI size you have, it can cover running instances of any size in its particular family.

This means that if you scale up an instance, the smaller contract sizes will accumulate to cover the machine, as long as the total hours being used are less than what is reserved. You can easily verify this on your invoice and observe it reflected on our billing savings page.

## More Information

Azure offers more detailed information regarding Instance Size Flexibility for Azure Reserved Instances, including details about the instance sizes and their associated normalization factors.

See: [Instance Size Flexibility for Reserved Instances](https://learn.microsoft.com/en-us/azure/virtual-machines/reserved-vm-instance-size-flexibility#instance-size-flexibility-ratio-for-vms)

## Related Resources

* [Does Archera Rely on Azure Exchanges or Returns Policy?](/help-center/azure-faq/exchanges-returns-policy.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)
* [Azure Offboarding](/help-center/azure-onboarding/offboarding/offboarding.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/instance-size-flexibility.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.