Common Troubleshooting
Last updated
Last updated
Ensure your workspace is not empty. A workspace must contain content to be visible to the Reporting Hub.
Ensure the Reporting Hub has been granted access your Workspace; see Configure Power BI Workspaces.
Ensure your Workspace has been assigned to your Embedded Capacity; see Configure Power BI Workspaces.
Click 'Refresh Workspaces' when creating a new Report page.
From the Admin Settings menu > Manage Groups > select Sync Groups
Ensure that either: no parent group is selected for the tenant, or that the desired group is contained within the selected parent or admin group
In order to enable Service Principal Profiles, you'll need to go to the Power BI service, Admin portal, Developer Settings and turn on the toggle that states "Allow Service Principals to create and use profiles".
The reason you're not able to sign in as that your Azure security policy requires you to use multi-factor authentication (MFA). The Reporting Hub authentication does not support multi-factor authentication. You can go to the Azure portal and disable MFA for your user account. https://learn.microsoft.com/en-us/entra/fundamentals/security-defaults
Then you will be able to sign into the Reporting Hub. From here, you have two options: if you need to enable MFA for all of your users, you can switch the authentication scheme in the Reporting Hub to Microsoft SSO. If you don't require MFA, you can continue to use the Reporting Hub authentication scheme. However, if any of your users, including guest users, require MFA, you'll need to enable it: https://docs.thereportinghub.com/tutorials/app-settings/authentication-admin
Ensure your global tenant has a parent group defined and that you're assigned to that parent group. If not, create a parent group (and associated member security groups) for the global tenant. Assign yourself to one of the associated member groups. Sign out and sign back in again. See Tenant Switching for more information.
After accepting your invitation, if your guest user gets the "Contact System Admin" message, your guest user may require multi-factor authentication (MFA). Even though your Entra ID doesn't require MFA, your guest's Entra ID may. In order for the Reporting Hub application to allow the guest user to connect, you will need to switch The Reporting Hub authentication to Microsoft Single Sign On (SSO) / MFA. You can do so by following these instructions: https://docs.thereportinghub.com/tutorials/organization-setup/authentication-admin
The likely cause of this is that the SMTP that you've set up is not enabled. Please return back to the SMTP Setup tab, edit the SMTP and you'll see a toggle to enable it. Once you've saved the changes, please log out and log back into the Reporting Hub. You should now be able to schedule an email.
If you had issues while running the Reporting Hub installer, you will need to do some clean up in your Azure environment:
Entra ID App Registration
Service Principal security group
The above items are created every time the installer is run. If you've used the same name for each install for the App Registration and/or the Service Principal, you may need to use date created to determine which ones to keep and which ones to remove.
Go to Azure Portal -> App Service.
In the configuration section of app service, verify that the following options are enabled:
1) FTP Basic Auth
2) SCM Basic Auth
Ensure that:
The capacity is turned on. You can either view a report in your Reporting Hub (which will turn the capacity on) or turn it on in the Azure portal.
You're a capacity admin.
You're a workspace admin.
If a Power Report is showing an error or, not rendering correctly in the Reporting Hub you must first identify if the issue is with the report within Power BI, or the Reporting Hub.
To understand where the issue with your Power BI report lies, start by accessing the report within the Power BI service.
If the report is not working as expected in the Power BI service: the issue is with the Report itself or with Power BI. You must address the issue with your report or with the Power BI service. In this scenario the Reporting Hub is passing along the error it's receiving from the Power BI service.
If the Report is working as expected within the Power BI Service, but not working in the Reporting Hub: the issue is with the Reporting Hub. There may be several reasons why this is happening. Try troubleshooting the following items:
Is your Power BI Embedded capacity active? See Embedded Capacity Admin.
Does the Reporting Hub service principal have access to the workspace where the data model resides? See Add the Reporting Hub Application to your Workspace.
If your report uses a direct query connection to data behind a gateway OR is a paginated report that references a data source behind a gateway: Has the Reporting Hub been granted access to your data source? See Managing Your Gateway.
Does your report use RLS and reside in a different workspace than its underlying semantic model? Ensure that the semantic model's workspace is added to your Reporting Hub tenant. If it's not added, you'll see the "Couldn't generate identity token for current user and report. Please make sure Service principal has admin rights on data gateway" error.
Make sure your Embedded capacity is active - see Embedded Capacity Admin tutorial.
Check that your Embedded capacity refresh time is scheduled just prior to your scheduled refresh time in the Power BI service -- see the Setting Your Refresh Schedule tutorial to learn how.
The Power BI service starts scheduled refreshes on a best effort basis (their words). They will try to start refreshes within 15 minutes of the time scheduled, however it could be up to an hour delayed. As such, you may need to account for this delay in the schedule you create in the Capacity Manager by increasing the duration.
Unfortunately, cross-report drillthrough isn't available for Power BI Embedded reports, which means it isn't available in the Reporting Hub, or any other embedded scenario.
As a workaround, you can merge the target report page into the source report and use drill-through within the same report.
Additionally, we encourage you to vote for this feature on Microsoft Fabric Ideas to help bring attention to its importance.
If a DAX identity function, like USERNAME() or USERPRINCIPALNAME(), isn't behaving as expected:
If the identity function is returning a GUID like "abcd-1234-abcd-1234-abcd-1234abcd1234", ensure that your semantic model has security roles defined on it, even if you don't need to use row-level filtering.
If you use a non-Entra authentication scheme, it could be using a different attribute for user identity than what you expect. Learn more here.
Custom visuals that don't require a license will work on the Reporting Hub without any additional configuration. Licensed visuals that you purchase from AppSource or from a third-party vendor may require a special license to be displayed on the Reporting Hub or may be blocked from loading in an embedded scenario altogether. If you have questions about a particular visual, contact the vendor. It may be helpful in your inquiry to mention that the Reporting Hub is an "embed for your customers" or "app owns data" scenario.
