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

# Frequently asked questions

## What is Cloud Halo?

Cloud Halo is an Azure FinOps platform for cost visibility, budgets, anomaly alerts, recommendations, savings tracking, allocation, and customer-ready reporting.

## Who is Cloud Halo built for?

Cloud Halo is built for Azure-first MSPs, Azure consultancies, SMBs, and internal teams that need practical FinOps workflows without building their own reporting stack.

## Does Cloud Halo change resources in Azure?

No. Cloud Halo is designed for read-only Azure access. It collects cost, subscription, tag, recommendation, and connection-health data so you can analyse spend and track optimisation work.

## Which Azure connection method should I use?

Most customers should use Enterprise Application consent because an Azure administrator can approve Cloud Halo once and then assign read-only roles to the required subscriptions. Use Service Principal setup if your organisation prefers managing app credentials directly.

## What billing options are available?

Starter, Team, Growth, and MSP Launch are available with monthly or annual billing. Annual billing includes two months free. Scale is a custom plan for larger partner estates or enterprise requirements.

## What happens after I start a trial?

You can connect Azure, invite users, review costs, set budgets, and validate reports during the 14-day trial. A payment method is collected securely by Stripe before the trial starts, and the plan renews unless cancelled before the trial ends.

## Can MSPs manage multiple customers?

Yes. MSP Launch and Scale support client workspaces so partners can keep customer subscriptions, reporting, users, and alert routing separated.

## Can I send client or executive reports?

Yes. Cloud Halo supports executive summaries, scheduled reports, cost exports, recommendation summaries, allocation reports, and chargeback or showback statements where plan features allow.

## How do I prove savings?

Resolve a recommendation after action is taken, then review the savings ledger. Cloud Halo compares later spend with the related baseline so teams can track confirmed, pending, and disputed savings.

## Where are terms, refunds, and cancellation details shown?

The checkout flow shows the order terms before Stripe opens. Customers must accept the current Terms, Privacy Policy, and DPA before placing a self-serve order. Cancellations take effect at the end of the current billing period, and fees already paid are non-refundable except where required by law.

## Where can I get help?

Use the help docs at <https://docs.cloud-halo.io/> first. If you still need support, include your workspace name, sign-in email, Azure tenant or subscription ID, and a screenshot or copy of the error message.


---

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