How to review an Azure reservation coverage gap
Eligible stable usage is not covered by an existing reservation or equivalent commitment. A coverage gap is an analysis prompt—not an automatic purchase recommendation.
Model only the remaining durable usageWho reviews this signal?
- Accountable owner
- FinOps + procurement
- Review cadence
- Monthly review; quarterly purchase cycle
Check observation dates and read-only scope. Your team approves and implements changes outside Costframe.
How this finding happens
- →Workloads grow after the last commitment purchase.
- →Rightsizing, region, family, or scope changes reduce benefit matching.
- →Teams optimize coverage without tracking utilization or planned retirements.
Collected evidence and verification limits
Checked when available
- ✓Hourly eligible usage grouped by benefit-relevant dimensions
- ✓Existing reservation and savings-plan coverage and utilization
- ✓Current on-demand and commitment net economics
- ✓Planned migration, rightsizing, seasonality, and contract constraints supplied by owners
Not always verifiable
- —Monthly averages are insufficient for commitment quantity.
- —Provider eligibility, exchange, cancellation, and scope terms can change.
- —Cost data cannot know every roadmap or business-demand change.
Missing or stale evidence is a limitation, not a passed check.
Why this finding might be wrong
These conditions lower confidence or require manual owner review before action.
- Temporary growth or seasonal peak
- Workload scheduled for retirement or migration
- Existing commitment not matched because of scope/configuration
- Usage that should be right-sized before commitment
Plan the change and recovery path.
- Remove direct waste and complete high-confidence rightsizing first.
- Calculate hourly coverage and utilization for a representative period.
- Subtract known changes and choose a conservative baseline.
- Review term, scope, flexibility, cash flow, and current provider rules with finance/procurement.
Rollback / recovery
A commitment is a financial contract, not a reversible infrastructure change. Mitigation may involve scope adjustment, exchange, or workload alignment subject to current terms.
How savings are calculated
Modeled saving = eligible stable on-demand net cost − commitment net cost, adjusted for unused-commitment risk. It remains estimated until billed outcomes are observed.
Do not quote a quantified saving when the billing scope, pricing basis or required workload evidence is incomplete or stale. Treat a modeled amount as estimated until suitable billed outcomes support it.
Check the billed outcome
Coverage rises without unacceptable utilization loss or overcommitment.
Model only the remaining durable usage
Review hourly eligible demand after existing coverage, rightsizing and planned retirements. Separate coverage from purchased-benefit utilization. Bring the conservative purchase quantity, unused-commitment risk and current contract terms to procurement before buying.
Work through coverage and utilizationIf the owner cannot resolve a dependency or recovery requirement, keep the candidate in review rather than treating it as approved.