> For the complete documentation index, see [llms.txt](https://docs.cloud-halo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud-halo.io/finops/overview-dashboard.md).

# Overview dashboard

The overview dashboard is the first place to check workspace health and current Azure spend.

## Main metrics

The overview shows:

* Current month Azure spend
* Forecast month-end spend
* Month-over-month movement
* Budget status
* Top subscriptions, services, regions, and resources
* Recent recommendations
* Azure connection health

## Forecast

Cloud Halo uses historical daily cost trends where available. Forecasting is more accurate after the workspace has several days of synced cost history.

Forecasts are estimates and can change when Azure posts delayed usage, credits, refunds, or reservation adjustments.

## Azure connection health

Connection health highlights whether Cloud Halo can still access the connected Azure subscriptions.

Review this area when:

* Cost data stops updating
* A Service Principal secret is near expiry or has expired
* Azure roles have changed
* A subscription becomes inaccessible
* The latest sync reports an error

## Empty dashboard

If the overview has no cost data:

1. Confirm the workspace has an active trial or plan.
2. Confirm Azure is connected.
3. Confirm the Azure identity has Cost Management Reader at the correct scope.
4. Run Sync now from Azure connections.
5. Wait for Azure role assignments and cost data to propagate.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloud-halo.io/finops/overview-dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.