Common errors

Overview

This article covers common errors encountered across Cost Analyzer — including cost group configuration, service principal setup, dashboard loading, and report generation — that are not specific to a single feature area. For errors related to a specific area, refer to the dedicated troubleshooting articles linked below.

Business value

• Quickly identify the root cause of general errors without navigating multiple articles
• Resolve the most frequently encountered platform-level issues without raising a support ticket
• Understand which errors require Turbo360 support escalation versus self-service resolution

How it works

Cost Analyzer errors may surface in the UI as inline error messages, in the import status log, or as missing or blank content in dashboards and analysis views. Most errors fall into one of three root cause categories: permission gaps on the Azure service principal, misconfigured cost group definitions, or transient platform or API issues.

Troubleshooting

1. "Insufficient permissions" error when loading a cost group or subscription
   Cause: The Turbo360 service principal does not have the Reader role at the required scope (subscription or management group) in Azure.
   Fix: In the Azure portal, navigate to the subscription or management group and assign the Reader role to the Turbo360 service principal. If Reservation data is also required, assign the Reservation Reader role at the subscription scope. Allow up to 5 minutes for role propagation before retrying in Cost Analyzer.

2. Dashboard widgets show "No data available" after a successful import
   Cause: The cost group definition does not match any resources with spend in the selected period, or the dashboard filter is set to a date range outside the available import history.
   Fix: Review the cost group scope configuration and confirm it includes the correct subscriptions, resource groups, or tags. Adjust the dashboard date filter to a period covered by the import history. If spend is expected but not appearing, check whether the relevant resources are tagged correctly and included in the cost group dimensions.

3. "Failed to load" error on the analysis or forecasting page
   Cause: A transient API error, a browser session timeout, or a cost group with an exceptionally large dataset that is timing out during rendering.
   Fix: Refresh the page. If the error persists, clear the browser cache and try again. For large cost groups, apply filters (subscription, date range, resource type) to reduce the dataset before loading the analysis view. If the error persists after filtering, contact Turbo360 support with the cost group name and the time the error occurred.

4. Report generation fails or produces a blank report
   Cause: The report configuration references a cost group or analysis view that has been deleted or renamed, or the service principal does not have sufficient permissions to retrieve data for the report scope.
   Fix: Open the report configuration and verify that the linked cost group and analysis view still exist and are correctly named. Re-link the report if the source has been renamed. Verify service principal permissions for the report scope. Re-run the report after correcting the configuration.

5. Cost Analyzer shows a different total than the Azure portal for the same subscription and period
   Cause: The amortization setting (actual vs. amortized cost) differs between Cost Analyzer and the Azure portal view being compared, or the Azure billing pipeline has not yet finalized data for the period.
   Fix: Confirm the amortization setting in Cost Analyzer matches the cost view in the Azure portal. Allow 24–72 hours for the current billing period's data to finalize. If the discrepancy persists beyond 72 hours on a closed billing period, contact Turbo360 support with the subscription ID, period, and both figures.

Related articles

• Import issues
• Budget issues
• Data delays
• Alert failures
• Governance recommendations