Explain an Azure cost change before acting on it

Make the comparison reproducible

Record the selected subscriptions, date boundaries, billing currency and cost basis. Compare complete calendar months for a financial review, or matched weekday patterns for an operational investigation. A partial current month should not be compared directly with a complete previous month.

Actual cost reflects charges under the applicable commercial terms. Amortized cost spreads eligible commitment purchases across their benefit period. A reservation purchase can create a cash-cost spike without a corresponding increase in compute demand. Compare the same basis on both sides.

• Include the same scopes and charge categories in both periods.
• Check when the source last refreshed and whether the period is still open.
• Keep credits, tax and support treatment explicit when comparing with an invoice.
• Retain native currency totals instead of adding EUR and USD values.

Trace the change from service to meter

Group by service first to isolate the largest contributors to the difference. Within the affected service, inspect resource or meter-level charges where available. For storage, a capacity increase, transaction surge and retrieval charge have different causes even when they appear under the same service name.

Where quantity and effective-rate evidence is available, inspect each separately. Increased usage at a stable rate suggests demand or configuration movement. A stable quantity with a changed rate suggests a pricing, benefit or rating question. Some summary datasets do not contain enough detail for this decomposition.

Choose the view that answers the next question

Azure Cost Analysis is the native starting point for scoped trends, grouping and actual-versus-amortized investigation. Cost details or exports help when a summary cannot explain meter quantities or adjustments. Azure Monitor and workload telemetry supply the operational context that billing records lack.

Costframe can compare retained actual spend by supported subscription and service, then connect available resource charges with inventory context and related findings. Current inventory is a separate observation from historical billing. Costframe's net/list context is not a replacement for Azure commitment amortization or invoice administration.

When the answer must remain incomplete

A successful empty result, an unqueried date and a permission-limited subscription are different conditions. Do not interpret all three as zero spend. Open-period charges can be rerated; capture the extraction date so a later correction can be explained.

If the charge has no resource identifier, keep it in the service/subscription reconciliation instead of discarding it. Where a resource is known, the latest owner or tag does not prove who was responsible during the earlier billed period.

References and further reading

Provider documentation explains native capabilities. Costframe availability and limitations are stated separately in this guide.

• Microsoft: Cost Management data, timing and included charges

Related investigations

• Reconcile Azure billing data
• Net cost and list price
• Costframe cost investigation