Troubleshooting Azure connection and no-data issues

Most Azure connection issues come from one of five causes: copied credential values, missing Cost Management/subscription read access, missing Storage Blob Data Reader for storage exports, delayed Azure billing data, or an expired client secret.

Connection says authentication failed

Check the client ID and client secret value. Azure shows both a secret ID and a secret value; CostRadar needs the secret value. Also check for extra spaces when copying.

If the secret has expired, create a new client secret in Azure and update the connection in CostRadar.

Subscription not found or access denied

Confirm that the tenant ID belongs to the Microsoft Entra tenant that owns the subscription. Then confirm the service principal has built-in Reader access at the subscription scope. For Storage Export ingestion, also grant Storage Blob Data Reader on the export container. The subscription connection check validates Reader access; blob access is validated when you configure the Storage Export.

Role assignments can take a short time to propagate in Azure. If you just assigned the role, wait and try again.

Connected but no cost data

Initial data can take a few minutes after a successful connection. Recent Azure billing data can also be delayed. Check Azure Cost Management for the same subscription and date range.

If Azure Cost Management has no data for the range, CostRadar cannot pull data for that period yet.

Data stopped updating

Check whether the client secret expired or was rotated. Also confirm the subscription still exists, billing access is active, the subscription read role assignment was not removed, and any configured Storage Export container still grants Storage Blob Data Reader to the same app.

What to send support

Send the subscription display name, the approximate connection time, the error text, and whether Azure Cost Management shows data for the same date range. Do not send Azure secrets.