> 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/cost-allocation.md).

# Cost allocation

Cost allocation maps Azure spend into business dimensions such as departments, projects, environments, or ownership groups.

## Dimensions

Create allocation dimensions for the areas your organisation reports on.

Common examples include:

* Department
* Project
* Environment
* Customer
* Platform team

Each dimension can have a name, type, and colour to make allocation views easier to scan.

## Rules

Allocation rules match Azure spend to a dimension.

Rules can match fields such as:

* Subscription
* Service
* Region
* Resource group
* Meter category
* Tag key and value

Rules can allocate a percentage of matched spend to a dimension.

## Tags

Cloud Halo captures Azure tags from synced cost data where Azure provides them.

Tag-based allocation works best when your organisation uses consistent tags such as:

* Environment
* Team
* Project
* CostCenter
* Owner

## Rule order and maintenance

Review rules regularly as Azure usage changes.

Keep naming consistent and remove old rules when applications, projects, or resource groups are retired.

## Plan access

Cost allocation may be limited by plan. If the page is unavailable or actions are disabled, review the workspace billing plan.


---

# 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/cost-allocation.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.