Installation Failures
Common errors you may encounter during installation
Troubleshooting Deployment Failures
If you reach the deployment check page and the deployment fails, complete the cleanup steps below before trying again.
In most failed deployments, many resources are still created successfully. In the Azure portal, you’ll typically see all Reporting Hub resources except the one that failed. When you rerun the installer, you can select those existing resources instead of recreating them. In the example below, everything was deployed except for the Azure SQL Server/Database
Delete Reporting Hub Entra ID Objects
A failed installation will still create Entra ID objects (an app registration and a security group). Delete those before retrying. You named these objects in step 7 of the Self-Serve Guided Install.
Delete the App Registration
In the Azure portal, go to Microsoft Entra ID.
Under Manage, select App registrations.
Select All applications.
Find your Reporting Hub app registration.
Select it, then select Delete.
Delete the Security Group
In the Azure portal, go to Microsoft Entra ID.
Under Manage, select Groups.
Select All groups.
Search for the security group created during installation.
Select it, then select Delete.
Common Issues
Azure Subscription Quota Restriction
If you getting an error returned regarding quota, you can request more via Azure Support.
Go to: https://portal.azure.com
In the left menu, select Help + support.
Click Create a support request
Search for Service and subscription limits (quotas)
Click Create a support request
On the Problem description tab:
Issue type: Service and subscription limits (quotas)
Subscription: Select the subscription where you need more SQL quota.
Service: Choose SQL Database
On Additional details tab, click Enter Details
Quota type: Region Access
Location: Region you need
Expected consumption: 1
Submit the Request
Installer does not proceed after selecting a resource group
This usually means your account does not have the Subscription Owner role.
If you are a Contributor, you can often proceed by selecting an existing resource group (instead of creating a new one).
Otherwise, either:
activate/get the Owner role for your account, or
ask an Azure admin in your organization to complete the installation.
Blank screen with “Microsoft login failed.”
This is typically caused by the account signing in not having a Power BI Service account yet (common in brand-new Azure tenants). You can double-check this by viewing the error in the URL bar. To fix this:
Go to
https://app.powerbi.com.Sign in with the same email used for the installer.
Confirm the account is successfully created/accessible, then retry the installation.
SQL Credentials Failing
If you are selecting an existing SQL server, the installer will prompt you to enter your SQL admin credentials. Your Entra ID credentials will not work here, you must use SQL Authentication.
The progress bar says 100%, but has not moved past that.
If this happens, then likely the installation was successful, but the installer timed out. To verify if the installation completed, navigate to the Azure App Service via the Azure Portal. On the overview page, select the default domain, and the application should start.
Azure Kudo Services has been blocked
This typically means that the settings configuration on the Azure App Service is incorrect. If you created the resource manually, ensure that the App Service Configuration Settings are correct.
Region Not Available
Microsoft sometimes places temporary limits on resource creation in specific Azure regions (commonly impacting Azure SQL Server creation). When this happens, the deployment may fail with an error indicating the region is not accepting new resource creation.
Recommendation: Before retrying, delete the Entra ID objects created by the failed installation (see the cleanup section above).
If you encounter this error, we recommend manually creating the resource in another region via Azure and then attempting the installation again, or you can delete the resources that were created in your last installation and attempt a fresh installation in another region. Before doing either, you should delete the Entra ID objects that the failed installation created.
Option 1: Creating a Resource in Another Region
Option 1: Manually Create the Failed Resource in Another Region
Use this option if you want to keep most resources where they already deployed, and only place the failed resource in a different region.
In the Azure portal, create the same resource type that failed.
Example: If the SQL Server failed, create a new Azure SQL Server.
Configure the resource using the guidelines in Azure Services Configuration Settings.
Create it in the same Azure subscription and resource group as the other Reporting Hub resources.
Choose a region that is available and close to your other resources.
Example: If resources are in East US and that region is blocked for SQL Server creation, try East US 2.
Rerun the Reporting Hub installer and select:
the existing resources already deployed, and
the manually created resource.
Option 2: Reinstall All Resources in Another Region
Use this option if you want all Reporting Hub resources in the same region.
Delete Reporting Hub Resources
If the Reporting Hub resources are contained in a dedicated resource group, delete the resource group.
Otherwise, delete the resources individually.
Check Location Availability Before Reinstalling
Before starting the installer again, confirm the target region supports creation of the required resources:
In the Azure portal, start creating a resource (for example, SQL Server).
Select your desired region.
If the region is unavailable, you may see an error such as:
“Your subscription does not have access to create a server in the selected region.”
Reinstall
Run the Reporting Hub installer again and create all resources in the new region you selected.
Contact Support
If none of the above cover the issue you are encountering, you can reach out to our support team to create a ticket. You’ll need to create a support account first—use the Sign Up link in the top right corner of the Support page. Where it says Application URL, input Installation Error.
Last updated