> 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/utilization-drops-start-of-month.md).

# Why Does Azure Utilization Drop at the Start of Each Month?

Microsoft delivers cost data for a new month with a lag — typically **8 to 24 hours** for usage to appear in Cost Management, and longer for a full month to settle. For the first days of each month, Archera can show commitments as underutilized simply because usage for the new month hasn't fully arrived.

## What to Expect

Judge utilization on the **prior full month**, not the current one. The current month's figure climbs as Microsoft delivers the backlog, and it isn't a reliable signal until the month is complete.

A commitment that looks underutilized on the 2nd and healthy on the 10th was healthy the whole time.

## When It Isn't the Lag

If a full, completed month still shows utilization you don't recognize, that isn't a reporting delay and it's worth raising with our support team. The usual causes are a cost export that stopped delivering or a permissions change in your tenant — both of which surface on the Integration Health page.

## Related Resources

* [Why Is My Dashboard a Day or Two Behind?](https://docs.archera.ai/help-center/user-guide/dashboard-day-behind.md)
* [Why Don't Archera's Azure Costs Match My CSP Invoice?](https://docs.archera.ai/help-center/azure-faq/costs-dont-match-csp-invoice.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/utilization-drops-start-of-month.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.
