> 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/budgets-and-alerts.md).

# Budgets and alerts

Budgets help you track expected Azure spend and notify the right people before spend becomes a surprise.

## Budgets

Create budgets for a workspace to track monthly spend against a target amount.

Budgets can include:

* Budget name
* Monthly amount
* Threshold percentages
* Notification preferences
* Email recipients
* Slack webhook delivery

## Thresholds

Threshold alerts fire when spend crosses configured percentages of the budget.

Common threshold patterns are:

* 50 percent for early awareness
* 80 percent for action
* 100 percent for breach

Cloud Halo records alert events so you can see whether delivery was attempted or sent.

## Budget projection

Cloud Halo estimates when a budget may be reached based on current spend and forecast data.

Use the projected breach date to decide whether to reduce usage, resize services, increase the budget, or investigate a spike.

## Delivery channels

Budget alerts can be sent by:

* Email
* Slack incoming webhook

Email delivery requires the Cloud Halo environment to have a configured email provider and verified sender address.

Slack delivery requires a workspace-specific incoming webhook URL in alert preferences.

## Alert hygiene

Keep alerts useful by:

* Sending high-priority alerts to operational channels
* Avoiding too many low-value thresholds
* Reviewing recipients when team membership changes
* Checking alert event status if a notification is missing


---

# 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/budgets-and-alerts.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.