Skip to main content

Azure Billing Troubleshooting

Use this guide to diagnose common issues with Azure billing integrations in Cloudaware, including Cost Management export delivery, Storage account access, and scope mismatches.

Cost Data Does Not Appear​

  • In the Azure portal:
    • Confirm that the Microsoft Cost Management export exists and is enabled.
    • Verify that the export targets the expected Storage account and container.
    • Confirm that new export files are appearing on schedule.
  • In Cloudaware:
    • Go to Admin → Azure Billing → CONFIGURED.
    • Review the status for the affected billing account or subscription.
    • Confirm that the expected export is discovered and enabled.

Cost Management Exports Are Not Running​

  • In the Azure portal:
    • Go to Cost Management + Billing.
    • Select the affected Billing account or Subscription.
    • Open Cost Management → Exports and verify:
      • The export exists and is enabled.
      • The destination Storage account and container are correct.
      • The schedule aligns with expectations.
  • In the Storage account:
    • Confirm that new export files appear on the expected cadence.
    • Check for gaps in file timestamps that may indicate export failures.

Cloudaware App Lacks Required Permissions​

  • At the billing scope:
    • For MCA/MPA, ensure the Cloudaware app/service principal has Billing account reader or equivalent access.
    • For EA, ensure an appropriate enrollment reader role is assigned according to Microsoft guidance.
  • On the Storage account that receives exports:
    • Confirm the Cloudaware app/service principal has Storage Blob Data Reader.
    • If the app does not appear in search, manually type its name.
  • After changing role assignments, allow time for Azure permission propagation before rechecking Cloudaware status.

Scope Mismatch​

Cloudaware must be configured for the same scope as the Azure export.

  • If Cloudaware is configured for a billing account, the export should be at the billing account level.
  • If Cloudaware is configured for a specific subscription, the export should be at the subscription level.
  • Ensure that all relevant subscriptions and billing accounts are enabled in Cloudaware Admin → Azure Billing → CONFIGURED.

Costs Do Not Match Microsoft Cost Management​

Microsoft Azure and Cloudaware totals can differ when the comparison uses different scope, timing, or cost settings.

  • Compare the same billing account or subscription scope.
  • Use the same date range, preferably a completed day or month.
  • Confirm whether you are comparing actual cost, amortized cost, credits, adjustments, taxes, or discounts in the same way.
  • Check whether Microsoft Azure has recently reprocessed historical periods or posted late adjustments.

Legacy EA Billing Export Issues​

Azure Enterprise Agreement customers may still have historical exports configured through legacy EA APIs and formats.

  • Confirm whether the affected integration uses modern Cost Management exports or a legacy EA export.
  • For new deployments or modernization work, prefer Microsoft Cost Management Exports.
  • If a legacy EA export stops updating, verify the EA configuration and consider migrating to Cost Management exports.

When to Contact Cloudaware Support​

If you have verified Azure exports, Storage account permissions, and Cloudaware configuration, but issues persist:

  • Collect the following before opening a ticket:
    • Cloudaware org name and affected Azure billing integration.
    • Azure billing account, enrollment, or subscription IDs in scope.
    • Storage account, container, and export path used by the integration.
    • Screenshots or samples showing:
      • Microsoft Cost Management export configuration.
      • Storage account container with recent export files.
      • Azure Billing integration status and any error messages in Cloudaware.
  • Contact Cloudaware Support via your usual channel or support@cloudaware.com and include the collected information for faster triage.