CIO and IT finance team reviewing software costs in a planning session
Microsoft

Software Assurance. Renew, drop, or convert.

SA is an economics decision per workload. Price the benefits you use against the 25 to 29 percent premium, and let the rest expire on schedule.

Contact Us Microsoft Advisory
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Microsoft Software Assurance is an economics decision, not a default checkbox, and the CIO playbook is to price each benefit you actually use against the 25 to 29 percent annual premium SA adds to license cost.

Key takeaways

  • SA costs 25 to 29 percent a year: on top of license cost, every year, whether or not any benefit is used.
  • Most estates use three benefits or fewer: version rights, hybrid rights, and license mobility do the real work; the rest mostly expire unused.
  • The renew or drop decision is per workload: server estates moving to cloud need SA differently than stable desktop estates.
  • Subscription migration changes the question: M365 and cloud subscriptions embed SA equivalents, making standalone SA redundant on migrated workloads.
  • Dropping SA is reversible only at a price: reattaching later means repurchasing licenses, so the exit needs a roadmap, not a whim.
  • 15 to 30 percent savings are typical: estates that rationalized SA per workload cut that share of their SA spend in our file.

What does Software Assurance actually cost and include?

Software Assurance adds roughly 25 to 29 percent of license cost per year, bundled into L plus SA pricing on Enterprise Agreements. Over a three year term, you pay most of the license price again in assurance.

The benefit set spans version rights, Azure Hybrid Benefit, license mobility, training vouchers, and support incidents, defined in the Microsoft Product Terms. The economics question is which of those you would buy standalone at the price you are paying.

The SA benefits that matter, by estate type

BenefitWho actually uses itValue driver
New version rightsEstates with active upgrade cadenceAvoids repurchase at major versions
Azure Hybrid BenefitServer estates moving to AzureCuts Azure VM and SQL costs materially
License mobilityVirtualized and hosted server estatesMoves licenses across infrastructure
Disaster recovery rightsEstates with passive DR serversFree passive instances
Training and supportFew, in practiceVouchers that mostly expire

How do you decide to renew, drop, or convert SA?

The decision runs per workload, not per agreement. Map every SA carrying license to one of three paths: renew because a used benefit pays for it, drop because nothing does, or convert because a subscription will replace it.

  1. Inventory SA carrying licenses and their annual SA cost by workload.
  2. List benefits actually exercised in the last 24 months, with evidence.
  3. Tag each workload: cloud bound, stable on premises, or retiring.
  4. Price each used benefit standalone against the SA premium paid.
  5. Decide renew, drop, or convert per workload, and sequence the exits at renewal dates.

Where dropping SA goes wrong

Dropping SA ends version rights, and reattaching SA later requires repurchasing the license. The drop decision is safe on stable, fully depreciated workloads with a defined retirement path, and dangerous on anything with an undefined future.

How does the move to subscriptions change the SA question?

Microsoft 365 and most cloud subscriptions embed upgrade rights and mobility, which makes standalone SA redundant on migrated workloads. Every workload that moves to subscription should take its SA spend off the table at the next anniversary.

The trap is paying twice during transitions: subscription fees on the new model while SA renews on the licenses left behind. Transition estates should sequence SA expiry against migration milestones, not renew the full estate by default.

  • Migrated workloads: drop the legacy SA at the next renewal; the subscription carries the rights.
  • Transition workloads: renew selectively, matching SA terms to migration dates.
  • Staying workloads: run the per benefit economics honestly, especially on servers with Azure plans.

How do you negotiate SA at the EA renewal?

SA rationalization is renewal leverage. A buyer arriving with a per workload SA analysis signals the same discipline that moves discount bands, and the SA spend you retire funds the commitments Microsoft actually wants.

Run the SA decision inside the broader renewal program, not as a separate exercise. The EA program structure prices L plus SA together, so the negotiation should too.

What to trade and what to keep

Keep hybrid rights on cloud bound servers and version rights where the cadence is real. Trade the rest: retired SA spend converts into Azure commit, Copilot ramps, or simply a smaller bill, all worth more than vouchers that expire unused.

Where the common advice on Software Assurance is wrong

The standard advice, repeated by most licensing partners, is that SA is cheap insurance you renew estate wide because dropping it is irreversible. We disagree. In roughly 30 to 45 Microsoft estate reviews Fredrik Filipsson advised in 2024 to 2025, estates exercised 2 to 4 benefits out of the dozen they paid for, and rationalizing SA per workload cut 15 to 30 percent of SA spend without losing anything in use. The buyer side move is to treat irreversibility as a sequencing problem: map retirement and migration dates, then let SA expire where the license has no future that needs it. Insurance you never claim on, for assets you are retiring, is not prudence. It is budget leakage with a comforting name.

IT asset manager reviewing license and cost data across multiple screens
The benefit audit is the whole decision: most estates exercise fewer than a third of the SA benefits they renew.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

25-29%
Annual SA premium on license cost
2-4
Benefits actually used per estate
15-30%
SA spend cut by rationalization

Source: Redress Compliance advisory engagement file, 2024 to 2025.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

  1. Inventory every SA carrying license and its annual SA cost by workload.
  2. Audit which SA benefits were exercised in the last 24 months, with evidence.
  3. Tag workloads as cloud bound, stable on premises, or retiring.
  4. Price the used benefits standalone against the premium you pay.
  5. Sequence SA drops against migration and retirement dates at renewal.
  6. Bring the per workload SA analysis into the EA renewal as leverage.
Cover of the Microsoft EA Renewal Playbook white paper from Redress Compliance

White Paper · Microsoft

Microsoft EA Renewal Playbook

The 12 month buyer side framework we use with Fortune 500 clients to cut the standard Microsoft EA uplift. Read it free.

Read the white paper

Frequently asked questions

What does Microsoft Software Assurance cost?

SA adds roughly 25 to 29 percent of license cost per year, bundled into L plus SA pricing on Enterprise Agreements. Over a standard three year term you pay most of the license price again in assurance fees.

Which SA benefits are actually worth the money?

New version rights on actively upgraded estates, Azure Hybrid Benefit on cloud bound servers, and license mobility on virtualized estates. Estates in our 2024 to 2025 file exercised 2 to 4 benefits out of the dozen or more attached to their agreements.

Can you drop Software Assurance and reattach it later?

Dropping SA ends version rights, and reattaching later requires repurchasing the underlying license. The drop is safe on stable workloads with a defined retirement path and risky on anything whose future is undefined.

Does Microsoft 365 make Software Assurance redundant?

On migrated workloads, largely yes. Subscriptions embed upgrade rights and mobility, so legacy SA on licenses left behind becomes double payment. Sequence SA expiry against migration milestones to avoid paying for rights twice.

How much can SA rationalization save?

Estates that rationalized SA per workload cut 15 to 30 percent of SA spend in our engagement file without losing a benefit in active use. The savings convert into renewal leverage or direct budget reduction.

Should SA be negotiated separately from the EA renewal?

No. Microsoft prices license and SA together, and the SA analysis is renewal leverage. Retired SA spend funds Azure commits or Copilot ramps, trades Microsoft values more than the vouchers most estates let expire.

Free Download

The full Microsoft EA Renewal Playbook framework from the Microsoft Advisory.

The EA renewal sequence, the SA economics, and the clause moves that hold the savings.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

No spam. We will only email you about this download. Privacy.
Run a software spend health check against your Microsoft estate in under five minutes.
Open the Tool →
25-29%
Annual SA premium on license cost
2-4
Benefits actually used per estate
15-30%
SA spend cut by rationalization

Insurance you never claim on, for assets you are retiring, is not prudence. It is budget leakage with a comforting name.

Fredrik Filipsson
Co Founder and Group CEO. Ex Oracle, IBM, SAP.
Deep Library

More on this topic.

Microsoft Advisory →
Benchmark data analysis on a screen
Microsoft
Microsoft EA Benchmarking Report
Where your discount should sit by volume band.
8 min read
License count reconciliation on a screen
Microsoft
Microsoft EA True Up Guide
How the annual true up actually works.
7 min read
Corporate negotiation meeting in progress
Microsoft
Fortune 500 EA Renewal
20 percent saved on a 60,000 seat estate.
8 min read
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.

Stay ahead of Microsoft licensing changes.

One buyer side briefing a week. Pricing moves, audit signals, and the levers that work. No vendor spin.