Why Azure cost data can be delayed
How Azure billing data timing affects CostRadar charts, current-month estimates, and anomaly detection.
CostRadar depends on Azure billing data. Azure does not publish every cost event in real time, and recent usage can change while Microsoft processes charges from different meters and billing systems.
CostRadar checks for updated cost data on a schedule. When Azure has not published new data yet, CostRadar cannot make it appear earlier.
Typical timing
Azure billing data timing varies by account type, service, meter, and region. Enterprise Agreement and Microsoft Customer Agreement data is often available within roughly a day. Pay-as-you-go data can take longer, sometimes up to several days.
Because of that delay, a cost increase from this morning may not appear in CostRadar immediately. It will appear after Azure has posted the underlying billing data and CostRadar has pulled the update.
Current month is estimated
Current-month totals are best treated as estimates. Azure continues to refine the month as charges are processed, credits are applied, taxes or adjustments are finalized, and late-arriving usage lands.
Completed prior months are more stable. If you are reconciling finance records, use finalized Azure billing records as the source of truth.
What to check when numbers look wrong
- Look for the data freshness timestamp in CostRadar.
- Compare the same date range in Azure Cost Management.
- Check whether the relevant service has delayed meter reporting.
- Confirm the subscription is still connected and the client secret has not expired.
If Azure Cost Management and CostRadar disagree for an older finalized period, contact support with the date range, subscription display name, and screenshots of both views.