.png)
AWS
Microsoft Azure
Google Cloud
To measure incremental savings accurately, teams need to compare the proposed strategy with the current optimized Azure position using the same scope, pricing, commitments, and workload assumptions.
What Are Incremental Azure Savings?
Incremental Azure savings are the additional savings created by a new action compared with what your organization would otherwise have paid.
A practical framework is:
Incremental Azure savings = current optimized Azure cost – proposed Azure cost
For this calculation, current optimized Azure cost should reflect applicable rates, existing Reservations and Savings Plans, and other savings already in place for the same portfolio and period.
Also read Azure Reservations Strategy Guide.
Quick Calculation Worksheet
| Measure | Illustrative value |
|---|---|
| Current optimized Azure cost | $700,000 |
| Proposed Azure cost | $650,000 |
| Incremental Azure savings | $50,000 |
| Incremental provider fee | $10,000 |
| Incremental operating cost | $2,000 |
| Net incremental value | $38,000 |
Use the same billing scope, currency, historical period, workloads, rates, commitments, and assumptions in both cases. Export Azure Cost Management Actual Cost and Amortized Cost data for the calculation period, and retain the applicable rate evidence, Reservation and Savings Plan inventory, and utilization or unused-cost data used to calculate each case.
The applicable commercial agreement, not this editorial calculation framework, determines the exact provider fee base.
Why the Wrong Baseline Inflates Savings
Suppose the same workloads would cost $900,000 per month at the relevant pay-as-you-go equivalent.Existing Reservations, Savings Plans, and pricing agreements already reduce your current cost to $700,000. A proposed strategy brings the same portfolio down to $650,000.
Comparing $650,000 with $900,000 produces a $250,000 headline discount.
But $200,000 of that benefit was already present.
The additional reduction is:
This example is illustrative and does not represent an actual Usage.ai customer result.
Step 1: Build the Baseline You Actually Have
Your baseline should answer:What would this same Azure portfolio cost if we continued with our current strategy?
Include the relevant billing scope, workloads, applicable rates, existing commitments, underutilization, and current management costs where applicable.
Microsoft’s recommendation methods support the same baseline discipline.
Azure Reservation recommendations account for existing Reservations and Savings Plans, and reported savings are calculated in addition to applicable negotiated or discounted prices.
Azure Savings Plan recommendations use actual eligible on-demand usage and costs, including negotiated on-demand discounts.
At Usage.ai, we keep existing Azure savings in the baseline and measure only the additional value created through new optimization opportunities.
Step 2: Compare the Same Azure Portfolio
Keep both cases aligned on:subscriptions or billing scope
services and SKUs
regions
historical period
negotiated rates
existing commitments
workload assumptions
planned migrations or shutdowns
Also read: Azure VM Cost Optimization Guide
Step 3: Apply a Simple Attribution Test
Suppose your current Azure Reservations already save $40,000 each month and a new strategy creates another $15,000.For an incremental-savings calculation, keep the existing $40,000 in the baseline and attribute the additional $15,000 reduction to the new strategy.
That does not determine how a provider is contractually allowed to calculate fees. Confirm the fee methodology in the applicable agreement.
Step 4: Use the Right Cost View
Azure provides actual and amortized cost views for Reservations and Savings Plans.Use actual cost to reconcile invoices and purchase timing. Use amortized cost to evaluate commitment economics over time because it spreads commitment charges across the resources that used the benefit.
Microsoft’s Azure Reservations and Savings Plan cost guidance explains the difference between these cost views.
When validating a savings claim, reconcile both views rather than relying on only one.
If unused commitment cost is already included in the proposed Azure cost, do not subtract it again as a separate penalty. That would count the same downside twice.
Step 5: Separate Projected Savings From Realized Savings
A recommendation is a forecast.Realized savings are what actually happened after the commitment became active.
Workloads can scale down, migrate, change SKU or region, shut down, or grow differently than expected.
For Azure Savings Plan for Compute, customers make a fixed hourly spend commitment for one or three years. Microsoft states that unused hourly commitment expires and does not roll over. See the Azure Savings Plan overview.
For Finance reporting, keep these two measures separate:
Projected savings: the expected opportunity before purchase.
Realized savings: the measured outcome after actual usage and billing are known.
For more background on how Azure commitments behave, see our Azure Savings Plans guide.
Step 6: Do Not Combine Overlapping Savings Claims
Rightsizing can reduce the usage that supports a Reservation or Savings Plan recommendation.Microsoft recommends sequencing Azure Advisor cost actions because resource changes can invalidate earlier commitment recommendations. See the Azure Advisor savings methodology.
Do not simply add:
Recommendation outputs are snapshots. Re-run the model after rightsizing, migrations, shutdowns, scope changes, or new commitment purchases before using the result in a Finance model.
Microsoft also recommends allowing commitment recommendations to update after purchases or material usage changes. See the Azure Savings Plan commitment guidance.
Step 7: Calculate the Value Finance Actually Keeps
Once the baseline is controlled:Current optimized Azure cost: $700,000
Proposed Azure cost: $650,000
Incremental Azure savings: $50,000
Incremental provider fee: $10,000
Incremental operating cost: $2,000
Net incremental value: $38,000
The applicable commercial agreement determines how a provider calculates its fee.
What Evidence Should Finance Keep?
To make the result reproducible, retain:the Azure Cost Management export for the calculation period
Actual Cost and Amortized Cost views where commitments are involved
applicable rate or negotiated-pricing evidence
the current Reservation and Savings Plan inventory
utilization or unused-cost data
the exact billing scope and period
assumptions used for the proposed case
the provider fee calculation and agreement terms
The final result should also reconcile to Azure billing data.
Once Finance agrees on the baseline and evidence requirements, the next question is whether a proposed service can demonstrate additional, reproducible value.
How Usage.ai Fits Into the Evaluation
At Usage.ai, we help teams evaluate additional eligible Azure commitment opportunities against their existing baseline rather than treating existing discounts as new value. For eligible Azure compute workloads, Azure Savings Plan for Compute can deliver estimated savings of up to 65% compared with pay-as-you-go pricing, according to Microsoft. Usage.ai helps teams pursue these commitment savings while providing cashback protection for eligible Flex Insured Commitments when qualifying downside occurs under our program terms.For this analysis, evaluate cashback separately from Azure-cost savings. Do not present a recovery mechanism as additional cloud-provider savings.
If you are deciding which commitment structure fits the remaining opportunity, see our Azure Savings Plan vs Reservations guide.
How Usage.ai Pricing Fits Into the Calculation
Our pricing model for applicable Flex Insured Commitment arrangements is savings-based.For Finance, the important distinction is between:
Gross incremental savings and net value retained after the applicable Usage.ai fee. Always confirm the exact fee base, eligibility rules, and commercial terms in the applicable customer agreement.
For more context on how savings-based models differ from other pricing approaches, see our cloud cost optimization pricing guide.
Final Verdict: Measure the Delta
A large Azure discount does not automatically mean a new platform created all of that value.A stronger incremental Azure savings calculation does five things:
establishes the current optimized baseline
compares the same portfolio and assumptions
keeps existing savings in the baseline
deducts the incremental cost of generating new savings
reconciles projections with realized billing results
It is to produce a number your CFO, FinOps team, and Procurement team can reproduce and defend.
Before committing to a new Azure savings strategy, calculate its value against the discounts and commitments you already have. With our Flex Commitments, we can help you assess additional eligible Azure commitment opportunities and provide cashback protection when an eligible commitment costs more than equivalent On-Demand usage, subject to current program eligibility and terms.
Frequently asked questions
What are incremental Azure savings?
Incremental Azure savings are the additional savings created by a new optimization strategy compared with your existing optimized Azure position.
Should existing Reservations and Savings Plans count as vendor savings?
Not when calculating incremental savings. Keep their existing benefit in the baseline, then attribute only the additional cost reduction from new actions to the new strategy. Confirm any provider fee methodology in the applicable agreement.
Does Microsoft account for negotiated pricing in Azure recommendations?
Yes. Microsoft says Azure Savings Plan recommendations use eligible on-demand usage and costs, including negotiated on-demand discounts. Reservation recommendations also account for applicable negotiated or discounted pricing.
Should I use actual or amortized cost?
It depends on the question. Use actual cost to reconcile invoices and purchase timing. Use amortized cost to evaluate commitment economics over time because it spreads Reservation and Savings Plan charges across the resources that used the benefit. Reconcile both views when validating a savings claim.
When should I refresh the calculation?
Refresh it after material changes such as rightsizing, migrations, shutdowns, scope changes, or new commitment purchases. These changes can alter the usage baseline and remaining commitment opportunity.
