Explain a cloud bill increase before changing resources
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
A bill increase can lead you to cut the wrong workload, so compare two months on the same cost basis, rank changes within each provider, and separate usage, prices, discounts, and credits before asking an owner to act.
What you need first
- Tool
- Use provider cost reports, which are read-only spending views: AWS Cost Explorer Compare, Azure Cost Analysis at subscription scope, and Google Cloud Billing reports. Record results in a text editor or spreadsheet.
- Access
- AWS Cost Comparison requires ce:GetCostAndUsageComparisons and ce:GetCostComparisonDrivers. For Azure and Google Cloud, ask an authorized billing colleague for read-only report results for the subscriptions or billing accounts in scope.
- If you do not use that tool
- Ask a cloud billing colleague to complete the worksheet. Give them the two months, AWS accounts, Azure subscriptions, and Google Cloud billing accounts or projects in scope. Request report references, filters, totals, leading changes, and usage, price, discount, or credit explanations.
Why this is worth a look
Skipping this can turn a billing symptom into the wrong resource change. AWS Cost Comparison breaks down usage and discount drivers. Google Cloud's cost breakdown separates credits, tax, and adjustments. Azure Cost Analysis can surface resource, SKU, and workload changes. Use those findings to test the explanation before changing resources.
Run this check
CHECKLISTComplete these read-only steps in a text editor or spreadsheet using provider reports. Compare two selected months within each provider first, and record cost currency and usage units separately.
Question: Why did the bill increase?
Prior month: __________ Current month: __________
Period completeness or corrections to check: __________
[ ] 1. Set comparison controls for each provider.
Provider: __________
Scope (AWS accounts, Azure subscriptions, or Google Cloud billing account/projects): __________
Report and reference: __________
Cost basis as labeled in the report: __________
Filters and included charges: __________
Currency: __________
Prior cost: __________ Current cost: __________
Change (current minus prior, in the same currency): __________
[ ] 2. Record leading changes within each provider.
AWS: Cost Comparison services, accounts, and Regions: __________
Azure: Cost Analysis resources with changed usage: __________
Google Cloud: Billing report services, projects, and regions: __________
If the report uses FOCUS fields, Service Name: __________
Report reference for each leading change: __________
[ ] 3. Test possible causes; mark unavailable details unknown.
Service or resource: __________
SKU (product or service identifier), where available: __________
Prior usage quantity and unit: __________
Current usage quantity and unit: __________
Price reference, unit, currency, tier, and applicable date: __________
If available, FOCUS SKU Price ID (provider price-list reference): __________
Usage change supported by report: __________
Price or discount change supported by report: __________
Google Cloud cost breakdown credits, taxes, or adjustments: __________
Do not use today's Google Cloud pricing report as proof of a past price.
Do not multiply quantity by price unless units and pricing treatment match.
[ ] 4. Record the explanation before requesting a resource change.
Owning team: __________
Confirmed cause and supporting report or team evidence: __________
Unresolved questions: __________
Proposed next action for the owner: __________
If combining providers, label-mapping assumptions: __________
If converting currencies, conversion method applied consistently: __________How to confirm it
- 01
Fix the comparison scope
Choose two months and record the cost basis, filters, included charges, and currency for each provider. Mark incomplete periods or corrections for follow-up. Keep provider totals separate until you record any currency conversion and label-mapping assumptions.
- 02
Open the provider reports
Open AWS Billing and Cost Management, choose Cost Explorer, then Compare in Report parameters. In Azure, open Cost Management from Azure Home, select a subscription, then Cost Analysis and a Smart view; select an anomaly insight if present. In the Google Cloud console, open the Billing report to review service, project, or regional usage costs.
- 03
Separate the leading cost drivers
Record AWS usage and discount drivers, Azure resources with changed usage, and Google Cloud credits, taxes, and adjustments from the relevant reports. Check prices only with compatible units and applicable dates. Google's pricing report shows prices as of the day viewed, not necessarily either comparison month.
- 04
Confirm the cause with the owner
Ask the owning team whether resource creation, a SKU change, or workload changes explain the movement. If using FOCUS fields, group by Service Name and use SKU Price ID to look up the provider's price-list entry. A stable SKU Price ID does not mean the price stayed fixed. Record unresolved causes instead of presenting them as confirmed savings opportunities.
Before making changes
Assume both months have a consistent scope, cost basis, filters, and currency. Provider labels are not automatically equivalent across clouds. FOCUS SKU Price ID is conditional and can be null. Azure anomaly detection runs 36 hours after the UTC day ends, so it is not an immediate check. This worksheet does not prove invoice completeness or root cause.