> 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/getting-started/get-started.md).

# Get started

This guide walks through the normal first-time setup for a new Cloud Halo workspace.

## Before you begin

You need:

* A Cloud Halo account
* Access to the Azure tenant or subscription you want to monitor
* Permission to approve an Enterprise Application or create a Service Principal
* Permission to assign read-only Azure roles at the subscription scope
* A payment method or trial eligibility for the plan you choose

If another person manages your Azure tenant, invite them to help with the Azure connection step.

## Setup overview

The first-time setup has five steps:

1. Create your Cloud Halo account
2. Name your workspace
3. Choose a plan or start a 14-day trial
4. Connect Azure
5. Assign the required Azure role and confirm the subscription

Email sign-ups pause on an email verification screen before onboarding starts. After you confirm your email, return to Cloud Halo and select Continue setup.

## Workspace name

During setup, you will name your workspace. Cloud Halo creates a workspace URL from this name.

Workspace URLs must be unique. If your chosen URL is already taken, choose a different workspace name or adjust the wording.

## Recommended Azure connection path

For most customers, use the Enterprise Application consent flow.

This is the simplest option because it lets an Azure administrator approve Cloud Halo once, then assign the required read-only role to the subscriptions you want to monitor.

Use Service Principal setup if your organisation prefers managing app registrations and client secrets directly.

## After setup

After setup, go to the dashboard and check:

* Current month spend
* Forecasted month spend
* Budget status and budget projections
* Azure connection health
* Recommendations
* Connected Azure tenants and subscriptions

If the dashboard has no cost data yet, check that the Azure role assignment has been completed and then run Sync now from the Azure connections page.

## Keep setup healthy

After the first sync, review these areas:

* Add budgets and threshold alerts
* Add Slack webhook delivery if your team uses Slack for operational alerts
* Invite team members from workspace settings
* Create allocation dimensions and rules if you need department, project, or environment reporting
* Schedule reports if stakeholders need regular summaries by email
* Review the savings ledger after recommendations are resolved so reported savings stay tied to real optimisation work


---

# 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/getting-started/get-started.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.