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

# Recommendations

Recommendations help you identify and track Azure optimisation opportunities.

## Recommendation sources

Cloud Halo can show recommendations from:

* Azure Advisor
* Cloud Halo cost heuristics

Azure Advisor recommendations use stable Azure recommendation identifiers where available. Cloud Halo recommendations are generated from synced cost and usage patterns.

## Well-Architected Framework pillars

Recommendations are grouped by pillar:

* Reliability
* Security
* Cost Optimization
* Operational Excellence
* Performance Efficiency

Use the pillar grouping to focus different teams on the recommendations they own.

## Recommendation fields

Recommendations can include:

* Title and description
* Source
* Confidence
* Estimated savings
* Impact
* Status
* Azure source key
* Related subscription, service, resource group, or resource

## Status workflow

Use statuses to manage follow-up:

* Open: needs review
* Dismissed: not relevant or not worth actioning
* Resolved: action was taken
* Reopened: needs attention again

## Savings tracking

When a recommendation is resolved, Cloud Halo can compare later spend against the pre-resolution baseline for the related cost dimension.

Savings tracking helps confirm whether optimisation work produced measurable results.

## Good practice

Review recommendations regularly and assign ownership outside Cloud Halo if your team uses a ticketing system.

Dismiss recommendations that are not relevant so the open list stays useful.


---

# 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/recommendations.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.