# Installation Failures
**Pre-Install Quota Check.** When you select your resource group region, the installer now checks your Azure subscription's quota for **App Service**, **SQL Database**, and **Fabric Capacity** in that region. A green check means quota is available. A red icon means there is no quota in the selected region — you can't continue until you either:
* Select **Will select region on creation** for the flagged resource (you'll be prompted to choose a different region for that resource later), or
* Request a quota increase for that resource in your preferred region, then retry. {% endhint %}
#### 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
## Clean Up 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
1. In the Azure portal, go to **Microsoft Entra ID**.
2. Under **Manage**, select **App registrations**.
3. Select **All applications**.
4. Find your **Reporting Hub** app registration.
5. Select it, then select **Delete**.
#### Delete the Security Group
1. In the Azure portal, go to **Microsoft Entra ID**.
2. Under **Manage**, select **Groups**.
3. Select **All groups**.
4. Search for the security group **created during installation**.
5. Select it, then select **Delete**.
## Resource Not Available in Your Region (Quota Restriction)
The installer checks your subscription's quota for **App Service**, **SQL Database**, and **Fabric Capacity** when you select a resource group region. If a resource has no quota in that region, the installer marks it with a red icon and blocks you from continuing.
You have two options:
1. **Deploy the flagged resource in a different region.** Select the **Will select region on creation** checkbox next to the flagged resource and continue. You'll be prompted to choose a region for that resource when it's created.
2. **Request a quota increase for your preferred region.** Use this if you need all resources in the same region for compliance, latency, or data residency reasons.
{% content-ref url="/pages/RP5Mb9RFz5iB9wIimXXU" %}
[Request a Quota Increase in Azure](/getting-started/deployment-step-by-step/self-serve-guided-install/quota.md)
{% endcontent-ref %}
## Other Common Issues
#### 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 **Azure Subscription 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:
1. Go to [`https://app.powerbi.com`](https://app.powerbi.com/)`.`
2. Sign in with the same email used for the installer.
3. 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.](https://learn.microsoft.com/en-us/azure/azure-sql/database/logins-create-manage?view=azuresql#authentication-and-authorization)
#### 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](https://docs.thereportinghub.com/getting-started/deployment-step-by-step/self-serve-guided-install#azure-services-configuration-settings) Settings are correct.
#### Reinstall
Run the [Reporting Hub installer](https://license.thereportinghub.com/install) 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](https://support.thereportinghub.com/) 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**.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.thereportinghub.com/getting-started/deployment-step-by-step/self-serve-guided-install/installation-failures.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.