Azure cost history discrepancies after account transition - CloudHealth

Products

• CloudHealth

Issue/Introduction

This article addresses discrepancies where Azure Cost History reports show significantly higher spend than Archived reports or prior billing cycles following an account transition or the addition of a new subscription.

Environment

• CloudHealth
• Azure Cloud Service Provider (CSP)
• Partner and Customer Tiers

Cause

Symptoms:

• Sudden spikes in historical spend (e.g., June/July costs) appearing in the Cost History report.
• Archived reports show the original billed amount (e.g., ####), while Current Cost History shows a larger amount (e.g., ####).
• Recent addition or re-addition of Azure subscriptions to the tenant.

Cause: Discrepancies occur when a new or temporary Azure account is added, triggering a backfill of historical billing data. CloudHealth ingests the subscriptions and expanding the dataset beyond what was previously recorded, often resulting in duplicated or overlapping cost records for the same period.

Resolution

1. 1 Verify if a new Azure account or subscription was added recently that covers the same resource group or subscription ID as an existing account.
2. Compare the Current Cost History report against the "Archive" report to identify the specific Resource IDs causing the spike.
3. Audit the data using FlexReports, filtering by AccountType and UsageStartDate to check for overlapping PAYG and EA/MCA records.
4. If duplicate data is confirmed, contact Broadcom Support to trigger a manual billing rerun or data recollection to force-sync the tenant data with the correct backend billing files.
5. Subscribe to this article (Link: 275360) for updates on automated sync improvements.

Additional Information

To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.