Software Assurance (SA) is the bundle of upgrade rights, deployment benefits, training vouchers and support entitlements that attach to perpetual Microsoft licences purchased under an Enterprise Agreement. SA can add 20 to 30 percent to the perpetual licence price, and the vast majority of customers never claim more than a fraction of the entitlements they pay for. Here is what is in the bundle, what is worth using, and how to negotiate SA renewal so the price reflects what you actually consume.
Software Assurance is a maintenance overlay that attaches to perpetual Microsoft licences (Windows Server, SQL Server, Visio, Project, Office Pro Plus when purchased as perpetual, the on-prem server family). SA is purchased annually, billed alongside the EA, and lasts the EA term. The published benefit categories include: new version rights (the largest single value), deployment planning services, training vouchers, home use programme, work-at-home rights, license mobility through SA (cloud), step-up licenses, spread payments, 24/7 problem resolution support, planning services, employee purchase programme, cold backup for disaster recovery, self-hosted application rights, and Microsoft Office Roaming Use Rights.
In our experience across 340+ engagements, fewer than 35% of SA-licensed customers actively claim more than two of these benefits. The cost of SA is the same whether benefits are claimed or not. The remediation pattern is either to claim aggressively or to challenge the SA renewal economics — preferably both.
Five categories deliver the bulk of the value: new version rights (entitling free upgrades to new product versions for the SA term), license mobility for SQL Server and other server products into Azure (eliminating the need to repurchase licences when migrating workloads to cloud), self-hosted application rights (permitting Microsoft software to be served to external customers as SaaS), training vouchers (typically 5–25 days per year for an EA), and planning services days (Microsoft-funded consulting time, typically 5–15 days per year).
The 60-day pre-anniversary window is the time to reconcile what SA actually delivered against what it cost — and re-tier where consumption does not justify the spend.
SA is priced as a percentage of the licence list price: typically 25% per year for application products and 25% for server products. Over a 3-year EA, total SA cost reaches 75% of the perpetual licence price — meaning customers can pay for the licence almost twice over across two EA cycles. The Microsoft sales rationale is that new version rights deliver a steady upgrade cadence. The counter-argument: most customers are now on subscription products (M365, Dynamics 365 SaaS, SQL Server in Azure) where SA is structurally irrelevant.
The negotiation pattern is to separate the SA position into three groups: SA on products genuinely consuming upgrades (defend the SA renewal); SA on stable products where the customer is on the long-term version (challenge the SA renewal as ongoing cost without commensurate value); and SA on products that are migration candidates to subscription (eliminate SA at renewal and migrate the workload).
If SA lapses (i.e. is not renewed at EA anniversary), the customer cannot re-add SA to those licences without paying a step-up cost equal to roughly 50% of the lapsed SA period. This Microsoft mechanism is rarely disclosed at the time of the lapse and is one of the most common surprises in subsequent EA renewals. Plan SA lapse explicitly: confirm the products where SA is genuinely no longer needed, document the rationale, and accept that the lapse is one-way unless the step-up is paid.
The SA renewal challenge patterns, the lapse-versus-step-up economics, and the structural protections worth fighting for at EA signing.
For subscription products (M365, Dynamics 365, Power Platform), there is no Software Assurance — the subscription includes upgrade rights and support by definition. SA only exists for perpetual products. As Microsoft has pushed more of its catalogue to subscription, the SA cost line should be shrinking proportionally. In practice it often is not, because account teams roll forward SA on perpetual licences that have been functionally superseded.
The cloud transition also reshapes specific SA benefits. License Mobility through SA is what permits SQL Server, BizTalk and other server products to be deployed in Azure or AWS without repurchasing — but the benefit is only available while SA is active. Self-Hosting Rights similarly require live SA. If migrating to cloud-native equivalents (Azure SQL Database, Power Apps, Dynamics 365 SaaS), the dependency on SA evaporates.
The SA reconciliation typically captures 8–18% of EA cost when the consumption mapping is honest.
For EAs above $1M annually, independent SA review — the heart of our license cost reduction work — captures cost reduction equal to three to seven times the advisory fee within a single EA renewal cycle.
We have re-tiered SA across EAs from $500K to $300M annually.
Weekly compliance intelligence for IT leaders.
