Self-Serve Guided Install
Install and deploy the Reporting Hub with our guided install service
Last updated
Install and deploy the Reporting Hub with our guided install service
Last updated
Get Started with a 30-day Enterprise-tier free trial. No obligation, no credit card required. Please note: Azure services costs may still apply.
Installing the Reporting Hub is simple, easy and takes approximately 10 minutes. The Reporting Hub web application and required Azure services can all be fully deployed by following our guided installation service.
Please review the below checklist 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.
Need Help? Contact our support team at https://support.thereportinghub.com. A dedicated team member will be available to assist with your deployment.
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 using existing resources, please also reference the Azure configuration requirements documentation to ensure your resources are configured correctly.
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.
The 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.
Next, select your Azure Resource Group. You will be presented 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.
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.
The minimum App Service tier required is a B1 Basic Service Plan. The Free or Shared plans WILL NOT support the application. If you attempt to use the Free (F1) or Shared (D1) plan, the installation will fail.
Your app service name determines the default domain for your website: <AppServiceName>.azurewebsites.net.
Select your Azure SQL Server & Azure SQL Database. You will be presented the option to either select an existing SQL Server or add a new SQL Server.
If selecting an existing Azure SQL server, select from the dropdown menu, then 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.
If adding a new SQL Server, select Add New from the dropdown list, name your SQL Server and Database, then click Next.
Select your Power BI Embedded Capacity. You will be presented 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 from the dropdown list; then click Next.
Check Create Fabric Capacity to create a new F2 Fabric Capacity. Leave it unchecked if you want to create an A1 Embedded Capacity. Name your Capacity and select Next.
Register your Azure AD Application and Service Principal and select your default Authentication Scheme.
Name your application and service principal.
Select your default authentication scheme from the dropdown list; then click Next.
Please note: if your organization uses Multi-Factor-Authentication (MFA), you must ensure you select the Microsoft SSO option. Your authentication scheme can be updated at any time following deployment. For more info on authentication options, please visit Authentication Admin.
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 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 from the dropdown menu, name your Translator then 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. If there are any failures, hover over the information icon in the failed status bar and note the error message that appears. Then, please contact support@thereportinghub.com so we can assist in resolution. If any Azure resources fail to deploy with an error message that says the location is not accepting creation of new resources at this time, see this 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 the 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. If unsuccessful, you will receive a failure message; contact support@thereportinghub.com so we can assist in resolution.
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 properly configure your Power BI settings:
Enable Power BI Service SettingsConnect Power BI WorkspacesPlease 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.
Below are the minimum Azure service requirements and configuration details required for the Reporting Hub application. 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.
Recently there have been periodic limitations imposed by Microsoft on resource creation in several Azure locations, especially for Azure SQL Servers in the US. If you attempt to deploy in one of the affected locations, your deployment may fail and you will receive an error that says the location is not accepting creation of new resources at this time, like the screenshot below.
If you encounter this error, you can manually create the resource in another region and reinstall, or you can delete the resources that were created in your last installation and attempt a fresh installation in another region.
In the Azure portal, create the same type of resource that failed to deploy. For example, if the SQL Server failed, you'll need to create a new SQL Server in Azure. The configuration guidelines for creating the resources can be found in the Azure Services Configuration Settings. Be sure to create the resource in the same Azure subscription and resource group as the other Reporting Hub resources were created.
We recommend creating the resource in the closest available location to your other Azure resources. For example, if your other resources are in East US but you cannot create a SQL server in that location, choose East US 2 for your manual creation.
Once you have created the resource, run the Reporting Hub installer again and select any existing Azure resources along with the resource you have manually created.
If you'd prefer all of your Azure resources to be in the same region, you can delete all of your Reporting Hub resources, determine which location you'll reinstall in, and run the installation again.
If all of the Azure resources you created during your previous installation are in their own resource group, you can simply delete the resource group in the Azure portal. Otherwise, you can delete them individually.
You should also delete the app registration. In the Azure portal, go to Microsoft Entra ID. Under the Manage heading, select App registrations. Select All applications, select your Reporting Hub app registration and delete.
Before you attempt another installation, you can check location availability on the Azure portal by starting to create a resource and select the desired location. If the location is unavailable, there will be an error message saying so.
For example, if you try to create a new SQL Server in the Azure portal in an unavailable region, you will see a message saying, "Your subscription does not have access to create a server in the selected region." See the screenshot below for an example.
Use the Reporting Hub installer to create all of your resources again in the new location you have chosen.
