For the complete documentation index, see llms.txt. This page is also available as Markdown.

Self-Serve Guided Install

Install and deploy the Reporting Hub with our guided install service

Our guided installer deploys the Reporting Hub web application and all required Azure services into your own Azure environment, one wizard page at a time. For every Azure resource, you can either select an existing resource or create a new one.

Here's the full deployment journey. This page covers the install itself and turning on AI; the last two stages are quick configuration steps on their own pages.

Stage
What you'll do
Where

1. Install & deploy

Grant consent, choose your subscription and resource group, configure your Azure resources, then deploy and launch Reporting Hub.

This page (steps 1–12)

2. Add AI (BI Genius)

Deploy required services for AI: PostgreSQL and Azure AI Foundry.

3. Configure Power BI

Enable the required Power BI tenant settings and connect your workspaces.

4. Configure Reporting Hub

Sync your groups, set up your Global Tenant, and set your home page.

Before You Begin


Click here to start the installation


Installation Steps

1

After signing in, you'll be prompted to grant application admin consent to the Reporting Hub Installer application. This lets the Installer deploy the Azure services and Reporting Hub web application within your Azure environment. You must grant consent to proceed.

Reporting Hub Installer is a Microsoft 'verified' application, and Shift Analytics Inc. is a Microsoft ISV Partner as identified on the Admin Consent page. This admin consent can be revoked at anytime following deployment via your Azure Portal.

Admin Consent Form
2

Select the Azure Tenant & Subscription

  • Choose the Azure Tenant and Subscription from the dropdown lists.

  • Select Next.

Select the Azure Subscription
3

Select your Azure Resource group

You can select an existing resource group or add a new one. We recommend creating a new resource group to keep your Reporting Hub resources organized.

  • Existing resource group: select it from the dropdown, then select Next. If you're using existing Azure resources, choose the resource group those resources belong to.

  • New resource group:

    • Select Add New.

    • Enter a Name, and choose a resource group region.

    • Select Check Resource Availability to confirm the required resources can be deployed in that region.

      • App Service

      • SQL Database

      • Fabric Capacity

    • When each shows a green check, select Next.

Check your Azure Resource Quota
All resources have Quota for this region.
4

Select your Azure SQL Server and database

  • Existing SQL Server: select it from the dropdown, then select an existing database or create a new one. You'll be prompted to sign in with your SQL Server credentials. Any data in an existing database will be overwritten.

  • New SQL Server:

    • Select Add New.

    • Name your SQL Server and database.

    • Select Next.

Creating a new SQL Server and database
5

Select your Azure App Service.

  • Existing App Service: select the App Service, then select an existing slot or select Add New, then select Next.

  • New App Service:

    • Select Add New.

    • Enter a Name.

    • Select a Tier.

    • Select Next.

Creating a new App Service
6

Select your Fabric or Embedded capacity

  • Existing capacity: select it from the dropdown and select Next.

  • New capacity:

    • Select Add New.

    • Create Fabric capacity is checked by default. If you want to deploy an A1 Embedded capacity instead, uncheck the box.

    • Name your capacity.

    • Select Next.

Create a new Fabric Capacity
7

Select your Azure Translator

  • Existing Translator: select it from the dropdown and select Next.

  • New Translator:

    • Select Add New.

    • Name your Translator.

    • Select Next.

Create a Translator
8

Register your Entra ID application.

  • Name your Application: this is your Reporting Hub app registration.

  • Name your Service Principal: this creates an Entra ID security group with the app registration as a member. You'll use this security group in the next stage, when you enable your Power BI settings.

  • Select Microsoft SSO.

  • Select Next.

Name the Entra ID App Registration
9

Review the deployment checks

The installer deploys, or connects to, each Azure resource:

  • Azure SQL Server and Database

  • Azure App Service

  • Power BI Embedded/Fabric capacity

  • Azure AI Translator

  • Entra ID application.

Each shows Deploying…, then Deployed. Once every resource shows Deployed, select Next. If any shows Failed, see the callout below.

Confirming Resource Deployment
Successfully Deployed All Resources
10

You'll be prompted to grant consent for permission on your new Reporting Hub Azure Entra ID application. This allows your Reporting Hub instance to access your Microsoft tenant and Power BI. The name shown at the top of the consent screen matches the Application name you set in step 8, so you can confirm you're granting consent to the right application.

This consent grants permission for your deployed instance of Reporting Hub to access your Microsoft tenant details, including Power BI. It will show as "unverified". This is expected, since you haven't verified your application yet. To verify your application, see Microsoft's Mark App As Publisher Verified documentation. Note, verifying your app is not required.

Application Consent Explanation
Granting Consent
11

Complete the installation and contact form

After you grant consent, the installer copies the application files. This may take several minutes, depending on your Azure region.

On the Starting application page, fill in

  • Your Application Registration Information of the best contact person for your company.

  • The short Power BI Adoption questions.

  • Then select Save Contact Data to continue.

Files Installation
Fill in your details, then select Save Contact Data to proceed
12

Launch your application

On the Success! page, select the link to your new Reporting Hub application to open it. If the installation fails instead, review the Installation Failures page.

Select the link to access your application
13

(Optional) Add AI: Deploy BI Genius

Prefer to set up AI later? You can skip this step and deploy BI Genius at any time by following the BI Genius Deployment Step-by-Step guide. As with your other Reporting Hub resources, the PostgreSQL and Azure AI Foundry resources are deployed to your own Azure subscription, so Azure usage costs apply.

Your plan includes BI Genius, governed, no-code AI agents that answer questions on your Power BI semantic models in plain language, inside your own Azure tenant, with every answer showing its sources, reasoning, and DAX. Your plan comes with a starter agent, so you can turn on AI right at the end of the installation.

Because your Reporting Hub App Service is already deployed, BI Genius reuses it and only deploys the two extra Azure resources it needs:

  • Azure Database for PostgreSQL (flexible server)

  • Azure AI Foundry (Azure OpenAI)

To turn on AI now, select the add BI Genius link on the Success! page, or go to license.thereportinghub.com/install?id=bigenius, and follow the prompts to select or create these resources, just as you did for your Reporting Hub resources.

For details on each option, see the BI Genius Deployment Step-by-Step guide.

BI Genius Deployment Step-by-Step

Next (Required): Configure Power BI

Once the Reporting Hub application is installed, configure Power BI tenant settings and Reporting Hub settings to start adding content to The Power BI settings are enabled by a Fabric or Power BI administrator; the Reporting Hub App Settings require a Reporting Hub Global Admin (by default, the user who ran the install).

Follow these two guided tutorials to finish your deployment:

Enable Power BI Service SettingsConfigure Reporting Hub App Settings

Azure Services Configuration Settings

Please note: this section only applies if you're using pre-existing Azure services. If you are creating new services as part of the guided installation process, you can omit this section as the installer will ensure these services are configured correctly.

The details below are a reference if needed during installation. If you've already deployed your application successfully, continue to the Power BI Service Settings link above.

If you'd prefer to create the Azure services manually before running the installer, the minimum service requirements and configuration details are below. Ensure all of your Azure services settings match these values, then run the installer and select the resources you created. All Azure services can be scaled further as your needs grow.

All Azure services must be in the same Azure subscription. All services except the Translator must be in the same resource group, which you'll select during installation. They do not need to be in the same region.

Azure SQL Database

If a setting is not specified here, use the default value in the Azure portal.

When creating the database, ensure:

  • Set the Azure Subscription and Resource group to the same as your other Reporting Hub services are in.

  • If you are creating a new database for your Reporting Hub, we recommend the following settings:

    • Set Want to use SQL elastic pool? to No.

    • Set Workload environment to Production.

    • Set Compute + storage service tier to Basic (DTU-based purchasing model) 5 DTUs.

    • Set Backup storage redundancy to Geo-redundant backup storage.

  • The database must be empty.

Azure SQL Server

If a setting is not specified here, use the default value in the Azure portal.

When creating the Server, ensure:

  • Set the Azure Subscription and Resource group to the same as your other Reporting Hub services are in.

  • Set Authentication method to use both SQL and Microsoft Entra authentication.

  • Set the Microsoft Entra admin. We recommend setting it to the user that will perform the Reporting Hub installation.

  • Set the Server Admin login and password, or, if using an existing server, ensure you have the credentials. You can validate that your credentials are correct by logging in through the Query Editor on the Azure portal.

  • Under Networking, enable Allow Azure services and resources to access this server.

Once the server has been created, under Security > Networking,

  • Ensure Public network access is set to Selected networks.

Azure App Service

If a setting is not specified here, use the default value in the Azure portal.

When creating the App Service, ensure:

  • App Type should be Web App.

  • Set Subscription and Resource group to the resource group that your other Reporting Hub services are in.

  • Uncheck "Secure unique default hostname on".

  • Set Publishing model to Code.

  • Set Runtime stack to .NET 10 (LTS).

  • Set Operating system to Windows.

  • Set Pricing plan to Basic B1 or Standard S1.

  • We recommend setting Enable Application Insights to No.

Once the App Service has been created, under Settings > Configuration:

  • Set Platform to 64 Bit.

  • Set SCM Basic Auth Publishing to On.

  • Set FTP Basic Auth Publishing to On.

  • Set FTP state to All allowed.

Azure Translator
  • Set Pricing tier to Free F0.

Last updated