> 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/welcome/what-is-cloud-halo.md).

# What is Cloud Halo?

Cloud Halo is an Azure FinOps platform for teams that want clear cost visibility, alerting, and optimisation tracking without building their own reporting stack.

It connects to Azure with read-only access, collects cost and optimisation data, and turns that data into dashboards, budgets, alerts, forecasts, allocation views, recommendations, and scheduled reports.

## What Cloud Halo helps you do

Cloud Halo helps you:

* See current month Azure spend and forecast month-end spend
* Compare spend across recent months and quarters
* Understand spend by subscription, service, region, resource group, meter category, resource, and tag
* Allocate spend to departments, projects, environments, or custom ownership dimensions
* Create workspace, service, and resource-group cost alerts
* Detect unusual spend patterns and notify teams by email or Slack webhook
* Review Azure Advisor and Cloud Halo recommendations by Well-Architected Framework pillar
* Track whether resolved recommendations actually reduced spend
* Produce summary and export reports for stakeholders
* Manage workspaces, members, roles, invitations, and accountable admin activity

## Who Cloud Halo is for

Cloud Halo is built for:

* SMBs that need fast Azure cost visibility
* Enterprise teams managing multiple subscriptions, departments, or environments
* Managed service providers managing Azure spend across customer workspaces

## How Cloud Halo connects to Azure

Cloud Halo supports two Azure connection methods:

* Enterprise Application consent flow
* Service Principal credentials

Both methods are designed for read-only access. Cloud Halo does not need permission to create, update, or delete Azure resources in your Azure tenant.

## Billing access

Cloud Halo requires an active trial or paid plan before the product workspace is fully available.

Plans control limits such as the number of Azure subscriptions and workspace users. Some advanced product areas can also be plan-gated, such as forecasting, anomaly detection, and allocation features.

## What happens after Azure is connected

After you connect Azure and confirm a subscription, Cloud Halo syncs cost data and starts building:

* Overview dashboard data
* Historical cost trends
* Budget and alert status
* Forecasts
* Anomaly detection results
* Azure Advisor and Cloud Halo recommendations
* Cost allocation results
* Reports

You can add more subscriptions and tenants later from the Cloud Halo dashboard, subject to your plan limits.

## Where to get help

Open the Cloud Halo documentation from the dashboard sidebar or visit <https://docs.cloud-halo.io/>.

For account, billing, or connection questions, include your workspace name, sign-in email address, and the Azure tenant or subscription you are trying to connect when you contact support.


---

# 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/welcome/what-is-cloud-halo.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.