Import issues

Overview

Cost Analyzer imports Azure cost and usage data from connected subscriptions on a scheduled basis. When an import fails or produces incomplete data, cost analysis, budgets, and anomaly detection all become unreliable. This article covers the most common import issues and how to resolve them.

Business value

• Restore accurate cost visibility quickly when imports fail
• Identify the root cause of missing or stale data before it affects budget tracking and reporting
• Prevent recurring import failures by addressing underlying configuration and permission issues

How it works

Import operations in Cost Analyzer retrieve cost and usage data from Azure Cost Management APIs for each connected subscription. A failed or partial import may result in missing data for one or more subscriptions, stale cost group totals, or anomaly detection alerts failing to trigger. Import status is visible in the Cost Analyzer settings.

Troubleshooting

1. Import completes but no data appears in cost analysis
   Cause: The Azure subscription has no cost data for the selected period, or the service principal does not have the Reader role at the subscription scope.
   Fix: Verify the service principal has the Reader role assigned at the subscription scope in Azure. Confirm the subscription has active resources and incurred spend for the period. Re-trigger the import manually from Cost Analyzer settings.

2. Import fails with an authentication error
   Cause: The service principal credentials stored in Turbo360 have expired, been revoked, or the client secret has rotated without being updated in the platform.
   Fix: Regenerate the client secret in Azure Active Directory and update the service principal configuration in Turbo360. Re-run the import after saving the updated credentials.

3. Import succeeds but data is incomplete — some subscriptions are missing
   Cause: The service principal does not have the Reader role on all subscriptions included in the cost group, or one or more subscriptions have been moved to a different Azure tenant.
   Fix: Review the subscription list in Cost Analyzer and verify Reader role assignment for each subscription. Remove subscriptions that have been migrated to a different tenant and reconfigure the connection under the correct tenant.

4. Import is stuck in a pending state
   Cause: The Azure Cost Management API is experiencing a delay or the import job timed out due to a large data volume.
   Fix: Wait 15–30 minutes and check whether the import completes. If it remains pending, cancel the import from Cost Analyzer settings and re-trigger it manually. If the issue persists, check the Azure Service Health dashboard for Cost Management API incidents.

5. Import succeeds but cost figures differ from the Azure portal
   Cause: Cost Analyzer and the Azure portal may use different amortization settings (actual vs. amortized cost), or there is a billing period lag in the Azure Cost Management API.
   Fix: Confirm that the amortization setting in Cost Analyzer matches the view you are comparing in the Azure portal. Allow up to 24 hours for Azure billing data to finalize for the current period before treating a discrepancy as an error.

Related articles

• Cost analysis
• Cost management groups
• Data delays
• Common errors