Self-Serve Guided Install
Install and deploy the Reporting Hub with our guided install service
Get started with a 30-day Growth-tier free trial. No obligation, no credit card required. Please note: Azure services costs may still apply.
Getting Started
Installing Reporting Hub is simple, easy, and takes approximately 20 minutes. The Reporting Hub web application and required Azure services can all be fully deployed by following our guided installation service.
Please review the checklist below before getting started:
Azure Services Setup Conditions: Any and all Azure services are not included within your Reporting Hub subscription. These services are deployed to your organizations' Azure instance and reside within your Azure subscription. Any and all Azure subscription fees are the responsibility of your organization. Once deployed any changes or ongoing administration of these services are the responsibility of your organization.
Ready to Get Started? Click the link below and follow along!
The tutorial below outlines the step-by-step process to install and deploy the Reporting Hub and associated Azure services within your Azure environment. For each Azure resource, you will have the option to select an existing resource or create a new resource.
If you’re selecting existing resources, use the Azure Service Setting requirements documentation to verify that each resource is configured correctly. Correct any mismatched settings before continuingotherwise, the installation will fail.
Installation Steps
The following is a step by step of each page in the installation wizard to guide you through what is happening on each page.
Grant Application Admin Consent: After signing in, you will be prompted to grant application admin consent to the Reporting Hub Installer application. This consent will allow the Installer application to deploy the applicable Azure services and Reporting Hub web application within your Azure environment. You must grant consent to proceed and complete the installation.
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.
Start by selecting your Azure Subscription and Azure Subscription from the dropdown list and click Next.
If the Select Subscription used for the Reporting Hub dropdown is empty, you may not have Subscription Owner permission for any Azure Subscriptions.
Next, select your Azure Resource Group. You will be presented with the option to either select an existing Resource Group or add a new Resource Group.
If using an existing Resource Group, select it from the dropdown list and click Next. If you are using existing Azure resources instead of creating new ones, select the Resource Group that those resources belong to.
If adding a new Resource Group, select Add New from the dropdown list and fill in the required fields; then click Next.
It is recommended to create a new Resource Group. If you are in the East US region, we recommend choosing East US 2 to ensure a successful deployment.
Select your Azure App Service. You will be presented the option to either use an existing App Service or add a new App Service.
If using an existing App Service,
Select the App Service.
Then, select an existing App Service slot or select Add New from the dropdown list.
Then, click Next.
If adding a new App Service,
Select Add New and fill in the required fields.
Then, click Next.
Good to Know: Your app service name determines the default domain for your website: <AppServiceName>.azurewebsites.net.
The minimum App Service Plan required is a B1 Basic Service Plan. B1 is only for development or testing purposes if selected periods of poor performance in the application are expected. An S1 (Standard) is recommended for production.
Select your Azure SQL Server & Azure SQL Database. You will be presented with the option to either select an existing SQL Server or add a new SQL Server.
If selecting an existing Azure SQL server:
Select it from the dropdown menu
Select an existing database or create a new database. You will be asked to enter your SQL Server credentials if you're accessing an existing database. Note that any data will be overwritten in an existing database.
If adding a new SQL Server:
Select Add New from the dropdown list
Name your SQL Server and Database
Click Next.
Select your Embedded Capacity. You will be presented with the option to either select an existing Capacity or add a new Capacity.
If selecting an existing Capacity, select it from the dropdown list and click Next.
If adding a new Capacity
Select Add New
If you wish to deploy an F2 Fabric Capacity, check the box. Leave it unchecked if you want to create an A1 Embedded Capacity.
Name your capacity and select Next.
Good to Know: Reporting Hub will, by default, manage (pause/resume) the capacity selected or created at this stage based on in-app activity. This may affect existing workloads in Power BI/Fabric if you select an existing capacity.
Register your Azure AD Application and Service Principal and select your default Authentication Scheme.
Name your application and service principal. Consider incorporating "App" and "SP" into your naming conventions to clearly define them.
IMPORTANT: Ensure you take note of your Application name and Service Principal name, as you will need this later when granting access within the Power BI Service.
Select your Azure Translator. You will be presented with the option to either select an existing Translator or add a new Translator.
If selecting an existing Translator, select from the dropdown menu and click Next.
If adding a new Translator:
Select Add New
Name your Translator
Click Next.
The installer will now run a series of checks and deploy your new services and/or connect with your existing services. Each service will return a result of "Done" if successful, or "Failed" if unsuccessful.
Following successful completion of the Azure services, click Next.
Deployment Failures: First, review the Installation Failures page and follow the steps for the error you’re seeing. If the error is related to location/region, refer to the Location (Region) Errors section.
You will be prompted to grant application admin consent for your new Reporting Hub Azure Entra ID Application. This consent allows your Reporting Hub application to access your Microsoft tenant and Power BI.
This subsequent admin consent is to grant permission for your deployed application instance of Reporting Hub to access your Microsoft tenant details, including Power BI. It will show as "unverified".
This is the expected result, given you have yet to verify your application. Please reference Microsoft's documentation for more information on how to verify your application if desired: Mark App As Publisher Verified.
After providing consent, the Reporting Hub application installation will be initiated. This step may take several minutes, depending on your Azure Region.
The installer will then run a series of checks and start your new Reporting Hub application.
If successful, you will receive a success message with the URL link to your application. Click the link to access your application.
If unsuccessful, you will receive a failure message; review the Installation Failures page.
Click the link to access your application.
After Installation: Power BI Configuration
You must complete the Power BI Service Settings and Reporting Hub App Settings configurations before you can embed content in your application.
After you have completed the installation of the Reporting Hub application and Azure services, you will need to ensure Power BI is configured correctly to allow permission to the Reporting Hub.
Please follow the two guided tutorials to finish your deployment of the application
Enable Power BI Service SettingsConfigure Reporting Hub App SettingsAzure 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 following content is provided here as a reference if needed during the installation. If you have successfully deployed your application, move on to the Power BI Service Settings link above.
If you would prefer to create the Azure services manually before executing the installer, below are the minimum Azure service requirements and configuration details required. Ensure that all of your Azure Services settings match the below configuration, and then run the installer and select the created resources. All Azure services can be additionally scaled as required based on your needs.
All of the Azure services need to be in the same Azure subscription. All of the Azure services except for the Translator need to be in the same resource group, which you will be prompted to select during installation. They do not need to be in the same region.
Azure SQL Server
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 SQL Database
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 App Service
If a setting is not specified here, use the default value in the Azure portal.
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 8 (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.
Last updated