> 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/storage-recommendations.md). # Azure Storage Recommendations Not Showing ## Likely Reasons Storage Recommendations Aren't Showing **Reason 1: Native Reservations Already Covering Storage Spend** The customer already has native reservations covering this storage or backup spend. Check their commitment inventory first before moving to the next reason. **Reason 2: Insufficient Storage Spend** The customer's storage or backup spend is not enough for the recommender to surface commitments. The minimum capacity to procure a reservation for storage or backup is **100TB**. You can find the customer's storage spend in Infrastructure Inventory and calculate the GB/hr metric over a 30-day timeframe to arrive at their rough monthly usage. ## Important Notes on Minimum Capacity ### Azure Storage Service The 100TB minimum is applicable to a particular tier (Hot, Cool). You **cannot** aggregate 60TB of Hot and 40TB of Cool in order to procure a 100TB Azure backup reservation. ### Azure Backup Service The 100TB minimum is applicable to a particular redundancy type. ## Related Resources * [Does Archera Rely on Azure Exchanges or Returns Policy?](/help-center/azure-faq/exchanges-returns-policy.md) * [What does Azure RI 'Instance Size Flexibility' mean and how does it work?](/help-center/azure-faq/instance-size-flexibility.md) * [Does Archera Support Reservations for Azure Storage Disks?](/help-center/azure-faq/storage-disks.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/storage-recommendations.md?ask=&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.