The spend problem was almost always commitment shape and waste, not unit price, and 15 to 30 percent of compute spend sat on resources nobody owned
On demand rates are largely fixed, so arguing them rarely pays. The leverage is choosing the right commitment instrument and removing spend that should not exist.
Prepared by Redress Compliance · August 19, 2026 · Azure estates reviewed. 20 to 35 files, 2024 to 2025.
Executive summary
Idle drag: 15 to 30 percent of compute spend went to oversized or idle resources nobody owned, across roughly 20 to 35 Azure estates reviewed between 2024 and 2025.
Commit mismatch: reservations and savings plans covered the wrong workloads, leaving steady use on demand and bursty use committed.
MACC overreach: spend commitments set to growth forecasts created shortfall exposure when the growth slipped, and the penalty erased the discount.
A commitment you cannot meet is a liability, not a saving. Size the commitment to a defensible floor and let growth land outside it.
What are the real Azure cost levers?
Commitment shape and waste recovery, not negotiating the on demand rate. Azure rewards customers who match committed pricing to steady usage and clean up the rest.
Microsoft documents the options in the Cost Management documentation, and current rates sit on the Azure pricing page.
The discount you capture depends on how well the commit matches the workload, not on a discount argument.
The three things that move Azure spend
- Commitment coverage: reservations and savings plans on the steady base load.
- Waste recovery: shutting down idle and oversized resources.
- Workload placement: right sizing and right region for the job.
Why list price is the wrong fight
On demand rates are largely fixed, so arguing them rarely pays. The leverage is in choosing the right commitment instrument and removing the spend that should not exist at all.
How do reservations and savings plans differ?
Reservations commit to a specific resource type for one or three years at a deep discount. Savings plans commit to an hourly spend across eligible compute with more flexibility and a smaller discount.
| Instrument | Best for | Trade off |
|---|---|---|
| Reservation | Steady, predictable resource | One to three year lock to a resource type |
| Savings plan | Variable compute | Hourly spend commit, more flexible |
| MACC | Whole Azure estate | Multi year spend pledge for incentives |
| On demand | Spiky or short lived | Highest unit rate |
When a reservation is right
Reservations suit steady workloads that will not change shape, detailed in the reservations documentation. The deeper discount rewards certainty.
- Predictable base load: databases and steady virtual machines.
- Stable region and family, where the resource type will not move.
- Long horizon: a three year term for the most certain workloads.
When a savings plan is right
Savings plans fit variable compute where the resource mix changes but overall spend is stable. They trade some discount for freedom to shift across instance types and regions.
Commitment coverage works only when finance and engineering agree on the steady base load that is safe to commit.
- Commitment coverage modelled against your actual steady base load
- MACC shortfall exposure priced before you agree the floor
- Every renewal and commitment clause flagged with replacement language
How should you approach the MACC?
The Azure Consumption Commitment trades a multi year spend pledge for discounting and marketplace incentives. It is powerful when sized to a floor and dangerous when sized to a forecast.
Sizing the commitment safely
- Commit the floor: the spend you are confident will occur regardless.
- Keep forecast headroom, so growth lands outside the locked commitment.
- Use marketplace eligibility, because qualifying spend can count toward the commit.
Reading the agreement terms
Check shortfall treatment, eligible spend definitions and term flexibility. Microsoft sets out the programme through its licensing resources, and the fine print on eligibility decides how achievable the commitment really is.
The wider renewal position sits in our EA 2027 series, and the server estate in the SQL Server licensing guide.
The Microsoft EA renewal playbook
The commitment sizing, the shortfall terms, and the renewal levers to run before the EA lands.
Get the playbook →What 20 to 35 Azure estates showed
Across the estates reviewed between 2024 and 2025, the spend problem was almost always commitment and waste rather than unit price.
The three patterns that recurred
- Idle drag: 15 to 30 percent of compute spend went to oversized or idle resources nobody owned.
- Commit mismatch: reservations and savings plans covered the wrong workloads, leaving steady use on demand and bursty use committed.
- MACC overreach: spend commitments set to growth forecasts created shortfall exposure when the growth slipped.
The ownership point in the first pattern is the one to sit with. Spend without an owner is not overspend anybody chose. It is overspend nobody noticed.
Research briefingAzure and the MACC before the 2027 renewalHow the consumption commitment interacts with the wider agreement, and what sizing it to a forecast actually costs.
Where the common advice on Azure cost is wrong
The standard advice is to sign the largest MACC you can to unlock the deepest discount. We disagree.
In roughly half of the estates reviewed, an aggressive MACC set to growth forecasts turned into a shortfall risk when the growth slipped, and the penalty erased the discount.
Size the MACC to a defensible spend floor, layer reservations and savings plans on the proven base load, and keep headroom for the forecast you have not yet earned.
A commitment you cannot meet is a liability, not a saving. The deepest discount on a floor you miss is more expensive than a shallower one you fill.
Oversized or idle capacity with no named owner attached.
Aggressive commitments set to growth that then slipped.
Reservations, savings plans and the consumption commitment.
Your first five moves
- Tag every resource and assign an owner, because cost without accountability is the waste nobody notices.
- Identify idle and oversized resources and recover that spend before committing to anything.
- Measure the steady base load that is genuinely safe to commit, with finance and engineering agreeing the number.
- Cover that base load with reservations and savings plans matched to workload shape, not to convenience.
- Size any MACC to a defensible floor rather than a growth forecast, and confirm shortfall and eligible spend terms before signing.
Frequently asked questions
What actually drives Azure overspend?
Commitment shape and waste, not unit price. Across the estates reviewed the rate was almost never the problem.
How much spend sits on idle resources?
Between 15 and 30 percent of compute spend went to oversized or idle resources that had no owner assigned to them.
Why is arguing the on demand rate a waste of time?
Because on demand rates are largely fixed. The leverage is in the commitment instrument and in removing spend that should not exist.
What is commit mismatch?
Reservations and savings plans covering the wrong workloads, so steady use runs on demand while bursty use sits committed.
When should you use a reservation?
For steady workloads that will not change shape: predictable base load, stable region and family, and a long horizon.
When is a savings plan the better fit?
Where the resource mix changes but overall spend is stable. It trades some discount for freedom to shift across instance types and regions.
Should you sign the largest MACC available?
No. In roughly half the estates reviewed, a MACC set to growth forecasts became shortfall risk when growth slipped, and the penalty erased the discount.
How should the MACC be sized?
To a defensible floor, the spend you are confident occurs regardless, with forecast growth landing outside the locked commitment.
What terms decide whether it is achievable?
Shortfall treatment, eligible spend definitions and term flexibility. The eligibility fine print decides more than the headline discount.
Where does commitment coverage break down?
Where finance and engineering have not agreed which base load is genuinely safe to commit. Coverage without that agreement is guesswork.