Preparing this Costframe view
Preparing this Costframe viewCostframe field guide
Azure Reservations exchange a one- or three-year commitment for discounted eligible usage. The safe purchase amount comes from a durable hourly baseline after rightsizing, existing commitments, scope, region, family flexibility, planned migrations, and business risk are considered. A reservation is a billing decision, not proof that capacity is required.
Framework
Eligible usage receiving a reservation benefit ÷ total eligible usage. Low coverage can indicate opportunity, but not the safe purchase quantity.
Reserved hours used ÷ reserved hours purchased. Low utilization means the commitment is not being fully consumed.
The lower, durable band of eligible usage that persists across weekdays, weekends, releases, and seasonal periods.
Remove waste and right-size first; otherwise a commitment can lock in capacity the team should have removed.
Implementation playbook
Group by benefit-relevant scope, region, family, meter, and hour; account for current reservations and savings plans.
Use a representative window and subtract known retirements, migrations, rightsizing, and seasonal peaks.
Evaluate term, payment option, scope, exchange/cancellation terms, and opportunity cost.
Track utilization and coverage separately; investigate drift before buying more.
Worked example
Illustrative only. Purchase decisions require hourly, eligibility-aware analysis and current provider terms.
Evidence standard
Costframe separates observed evidence from inference. Every finding can show what was checked, what was unavailable, why confidence may be lower, and whether the action still needs approval.
Decision tree
If source data is missing or stale, record the limitation before quoting impact.
If no team owns the resource, assign ownership before opening a change.
Treat the number as estimated until follow-up billing evidence supports it.
Failure modes
FAQ
Use it as an operating framework, then verify the resource, owner, evidence freshness, and billing basis before approving work.
Reject or park the estimate when provider data is incomplete, confidence is low, ownership is unclear, or the action conflicts with migration, resilience, or compliance plans.
Document the evidence source, net/list basis, assumption, owner, approval state, and how follow-up cost sync will verify the result.
Put the framework to work
Costframe connects read-only, records the evidence behind each finding, and keeps list-price estimates separate from net savings.