> For the complete documentation index, see [llms.txt](https://docs.thereportinghub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thereportinghub.com/getting-started/deployment-step-by-step.md).

# Deployment Step-by-Step

Get up and running with the Reporting Hub!

{% hint style="success" %}
**Get Started** with a 30-day Growth tier free trial. No obligation, no credit card required. *Please note:* *Azure services costs may still apply.*
{% endhint %}

**Deployment has two parts, and both are required before you can embed content.** 

First, **install** the Reporting Hub application (step 1). Then complete the configuration (steps 3–4): **Configure Power BI** requires a **Fabric or Power BI administrator**, and **Configure Reporting Hub** requires a **Reporting Hub Global Admin** (by default, the user who ran the install). Until configuration is done, no content can be embedded. Before you start, confirm who will handle each part.

#### 1. Install and deploy the Reporting Hub *(Azure Global Admin & Subscription Owner)*

{% content-ref url="/pages/1H8wP6dzjP8qdChwnaMg" %}
[Self-Serve Guided Install](/getting-started/deployment-step-by-step/self-serve-guided-install.md)
{% endcontent-ref %}

#### **2. Add AI with BI Genius (***Azure Global Admin & Subscription Owner)*

Your plan includes a BI Genius starter agent. Deploy it at the end of the install, or any time afterward.

{% content-ref url="/pages/8xuFfRGmiEWM9bp08DyU" %}
[BI Genius Deployment Step-by-Step](/bi-genius/bi-genius-deployment-step-by-step.md)
{% endcontent-ref %}

#### **3. Configure your Power BI Tenant settings** & Workspace *(Fabric or Power BI Admin)*

{% content-ref url="/pages/ZTurS8WKwsHYDkpOORRM" %}
[Enable Power BI Service Settings](/getting-started/deployment-step-by-step/enable-power-bi-service-settings.md)
{% endcontent-ref %}

#### **4. Configure your Reporting Hub App Settings** *(Reporting Hub Global Admin)*

{% content-ref url="/pages/D6QLOw6IhUgl69x7qJL6" %}
[Configure Reporting Hub App Settings](/getting-started/deployment-step-by-step/configure-reporting-hub-app-settings.md)
{% endcontent-ref %}

#### **5. Learn to use Reporting Hub**

{% content-ref url="/pages/fmYjHXgF7pL3ZhniLF1B" %}
[Learn to Use Reporting Hub](/getting-started/deployment-step-by-step/learn-to-use-reporting-hub.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thereportinghub.com/getting-started/deployment-step-by-step.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.