Overview
Business Application and resource dashboards fail to load for a small set of well-understood reasons: usually a permissions gap on the service principal, an unconfigured dashboard, or a resource that is no longer accessible. This article identifies the most common causes and how to fix them. Dashboards in Business Applications aggregate monitoring metrics, resource states, and operational data from Azure resources in real time.
Business value
Dashboard failures obscure the operational health of your Business Applications, forcing teams to switch to the Azure portal for information that should be available in a single view. Resolving them restores unified visibility and reduces the time needed to assess the state of your Azure resources.
How it works
Business Application dashboards pull data from associated Azure resources through the service principal. Each widget on the dashboard corresponds to a specific metric or resource state. If the service principal cannot access a resource, the widget fails to load. Custom dashboards depend on widgets being correctly added and configured by the user.
Dashboard data refreshes on each page load and, for monitoring state, after every monitoring cycle. A dashboard that loads but shows stale or empty data indicates a connectivity or permissions issue rather than a rendering failure.
Troubleshooting
-
Business Application dashboard shows a blank or empty state
Cause: No dashboards have been created by the user for this Business Application.
Fix: Navigate to the Business Application and open the Dashboard tab. Create a new dashboard and add the widgets relevant to your resources. The blank state is expected until at least one dashboard is created. -
Dashboard widget shows no data
Cause: The Azure resource the widget is scoped to has been deleted from Azure, the resource has been removed from the Business Application, or the data for the current monitoring cycle has not yet been fetched.
Fix: Verify the resource still exists in Azure and remains associated with the Business Application under the Resources tab. If the resource is present and associated, wait for the current monitoring cycle to complete and reload the dashboard. If the resource was deleted or removed, remove the corresponding widget from the dashboard. -
Resource dashboard widgets fail to load with a permissions error
Cause: The service principal does not have the permission required to read the metrics or state data for the resource type displayed in the widget.
Fix: In the Azure portal, verify that the Turbo360 service principal has at least Reader access to the resource. For metric-based widgets, the service principal may also need the Monitoring Reader role. Add the missing role assignment and reload the dashboard. -
Custom dashboard shows no widgets after configuration
Cause: Widgets were not saved after being added, or the dashboard configuration was cleared during a session timeout.
Fix: Open the dashboard, add widgets, and ensure each widget is saved before navigating away. If the dashboard is blank after a previous configuration, re-add and save the widgets. Custom dashboards persist per user within the Business Application. -
Dashboard loads correctly for some users but not others
Cause: The affected users do not have the required Business Applications permission level to view the dashboard or the associated resources.
Fix: Review the user's role and permission level in Business Applications. Users require at least Read access to the Business Application to view the dashboard. Adjust the role assignment for the affected users and ask them to reload the page.