# Troubleshooting Azure Connections
Use the checks below to resolve common issues when connecting Microsoft Azure to Cloud Ctrl or when data fails to appear after setup.
# 1. Connection Validation Fails
When adding an Azure connection in Cloud Ctrl, the validation step confirms access to both Azure APIs and Cost Management Exports.
If this step fails:
# Possible causes
- Incorrect Tenant ID, Client ID, or Client Secret
- Missing Reader role on one or more subscriptions
- API permissions not granted or consent not applied
- Conditional Access or MFA blocking the service principal
# How to fix
- Re-open your App Registration → Certificates & secrets and confirm that the secret is active and not expired.
- In App Registration → API Permissions, check that:
- Azure Service Management (user_impersonation)
- Azure Reservations (user_impersonation)
- Microsoft Graph (Directory.Read.All) (optional)
have been granted admin consent.
- In each subscription, confirm the service principal has the Reader role.
- Retry validation in Cloud Ctrl.
# 2. No Cost Data Appearing
If the connection validates successfully but no cost data is visible after 24 hours:
# Possible causes
- Cost Management Export not yet created or scheduled
- Export path or credentials mis-configured
- Storage Account access denied for the Application Credential
- Export file not yet generated by Azure (usually within 24 hours)
# How to fix
- In the Azure Portal, open Cost Management → Exports for your billing account, management group, or subscription.
- Confirm the export exists and is Enabled.
- In Storage Explorer or the Azure Portal, verify a recent
.csv
file is present in the target container. - Confirm the Application Credential has at least Reader or Owner access on the storage account.
- In Cloud Ctrl, open Setup → Cloud Accounts → Azure Connections and click Re-validate.
# 3. Partial or Incomplete Data
When some subscriptions appear in dashboards but others don’t:
# Possible causes
- Role assignment missing on one or more subscriptions
- Export configured only for part of your environment
- CSP automation unable to create exports for excluded subscriptions
# How to fix
- List all Azure subscriptions that should be included.
- For each, verify that the Application Credential has the appropriate role:
- Reader (standard accounts), or
- CSPExportManager (CSP accounts).
# 4. Historical Data Missing
# Possible causes
- Exports created recently (Azure does not backfill automatically)
- Historical export job still running (CSP automated backfill)
- CSV retention too short in the storage container
# How to fix
- Wait up to 24 hours after initial connection for backfill to complete.
- In the Azure Portal, check that Historical Exports are enabled if using automation.
- Increase retention or verify older CSV files are still available in storage.
- Cloud Ctrl will automatically identify and process historical exports during the next scheduled import.
# 5. Exports Not Updating Daily
# Possible causes
- Export schedule disabled in Azure
- Storage quota reached or container deleted
- Export failed due to transient Azure issue
# How to fix
- In Azure Portal → Cost Management → Exports, verify the Schedule is set to Daily.
- Check for failed export runs in the Activity Log.
- Ensure the storage account is active and has available capacity.
- In Cloud Ctrl, view Last Successful Import on the connection details page.
# 7. Still Need Help?
If issues persist after these checks, please contact Cloud Ctrl support.
Include the following details for faster assistance:
- Tenant ID
- One affected Subscription ID
- Date and time of your last successful export
- Screenshot of the export configuration or error message
💡 Tip: Most data issues originate from missing permissions or disabled exports.
Re-validating your connection in Cloud Ctrl will usually detect and report any of these configuration gaps.