What Software Assurance Actually Is (and What It Is Not)
Software Assurance is Microsoft’s maintenance programme for volume-licenced products. When you purchase a perpetual licence under an EA or other volume agreement and add SA, you pay an annual fee equal to 29% of the licence price for desktop products (such as Windows and Office perpetual) or 25% for server products. In exchange, you receive the right to upgrade to new versions of the covered product as they are released, plus a bundle of secondary benefits: home use rights, licence mobility, Azure Hybrid Benefit, training vouchers, and deployment planning services.
What SA is not: it is not a subscription licence. The subscription model — M365 E3, E5, E7, and their equivalents — includes version upgrade rights as a structural feature of the subscription. Customers paying for M365 E3 at $39 per user per month from July 1, 2026 do not need and cannot separately purchase SA on top of their subscription licence. SA applies only to perpetual volume licences, which are an increasingly rare procurement pattern given Microsoft’s commercial push toward subscription and NCE.
The organisations that still carry meaningful SA obligations are typically those that made large perpetual licence investments in the 2015 to 2020 period, particularly for Windows Server, SQL Server, and Office, and have continued renewing SA from inertia rather than active decision-making.
The Core Value Calculation: Version Rights
The primary value proposition of SA has always been version upgrade rights. If Microsoft releases a new version of Windows Server or SQL Server during your SA term, you can upgrade to it without buying new licences. Over a three-year EA term, the SA cost equals 87% of the original licence fee. The underlying question is: are the version rights received worth 87% of the licence price?
For desktop products like Office (where the subscription equivalent, M365, has largely displaced perpetual deployments in enterprise), the answer in 2026 is almost always no. The organisations still running perpetual Office with SA are paying 29% annually for upgrade rights to a product they may never upgrade, given that the practical alternative is transitioning to M365 subscriptions that render the SA coverage redundant. The SA cost is a legacy expense attached to a legacy procurement model.
For server products, the calculation is more nuanced. Windows Server and SQL Server still have large perpetual licence deployments in enterprise infrastructure. The Azure Hybrid Benefit — which allows you to bring Windows Server or SQL Server licences with active SA to Azure for significantly reduced compute costs — is a genuinely valuable SA benefit for organisations with hybrid cloud strategies. For a company running 500 Windows Server instances in Azure, the Azure Hybrid Benefit alone can offset the SA cost by a factor of two or three. That is the scenario where SA earns its cost in 2026.
The Benefits You Are Probably Not Using
SA comes with a wide portfolio of secondary benefits that Microsoft’s documentation lists prominently: training vouchers, desktop deployment planning, home use rights, Step-Up licence rights, and technical support days. The reality across the enterprise organisations we work with is that the utilisation rate on these secondary benefits is low. Training vouchers expire unused. Desktop deployment planning services are rarely activated. Home use rights are less relevant in an era of subscription-based M365 deployments where each user already has rights across devices.
This is not a criticism of the benefits themselves — some are genuinely useful when proactively managed. It is an observation that SA renewal decisions are rarely preceded by a usage audit of secondary benefits, which means the renewal decision is effectively a decision to pay for something without knowing whether it is being consumed. In every SA review we conduct, the gap between what is paid and what is used is material.
The one benefit worth calling out as consistently valuable is Licence Mobility. For organisations deploying Microsoft server software in hosted or cloud environments via authorised mobility partners, SA is required to enable that deployment model. Without SA, the licence cannot be moved to an authorised partner’s infrastructure. For organisations running hybrid deployments with significant partner-hosted components, this benefit is structural rather than optional.
SA in the Context of the 2026 Microsoft Licensing Landscape
The 2026 context makes the SA evaluation more urgent than in previous years for three reasons. First, Microsoft eliminated Level B, C, and D volume discounts in November 2025. Every EA customer is now at Level A list pricing. For organisations renewing SA on large perpetual estates at the new list price baseline, the cost of SA has effectively increased even without any per-unit price change. Second, the July 1, 2026 list price increases affect M365 subscription pricing (E3 to $39, E5 to $60, E7 at $99), which creates the right moment to comprehensively review the split between perpetual/SA spending and subscription spending within the estate.
Third, Microsoft’s commercial motion is increasingly oriented toward MCA and NCE subscriptions rather than EA perpetual. Field teams are compensated to sell subscription uplift, not to protect perpetual SA renewals. In practice, this means that a proactive Microsoft account team (where one still exists following 2025 layoffs) will typically steer organisations toward E3/E5/E7 subscriptions rather than helping them optimise their existing SA entitlements. The risk is that organisations transition to subscriptions while continuing to pay SA fees on perpetual licences that are now redundant — double-paying for upgrade rights they no longer need on the perpetual side.
Is your organisation double-paying SA on licences you no longer need?
Our Microsoft licensing advisory specialists audit SA entitlements and identify elimination opportunities before your next EA renewal.When SA Is Still Worth It in 2026
Based on our analysis, SA remains worth renewing in three specific scenarios. The first is for Windows Server and SQL Server licences actively deployed in Azure under Azure Hybrid Benefit. The cost savings from Hybrid Benefit on Azure compute can be substantial — Microsoft cites up to 40% savings on Azure VM costs for Windows Server workloads — and those savings require active SA. For a large Azure deployment, the arithmetic typically favours maintaining SA on server licences even at 25% annual cost.
The second scenario is for organisations with Licence Mobility requirements: those running Microsoft server software in hosting environments through authorised mobility partners. Without SA, this deployment model is not permitted under Microsoft’s licensing terms. Organisations in this situation have no practical alternative to SA renewal until they are ready to migrate fully to subscription-based licensing.
The third scenario is for organisations with documented plans to upgrade to the next major version within the SA term. If a new version of SQL Server or Windows Server is on your roadmap within 24 months, SA may be a cheaper option than purchasing upgrade licences separately. This requires an honest internal timeline assessment — not an aspirational roadmap, but a committed deployment plan.
Structuring the SA Renewal Decision
The right process for evaluating SA renewal is a three-step audit. First, catalogue every product carrying SA coverage, the quantity, and the annual SA cost. Second, for each product category, assess which of the SA benefits are actively being consumed — upgrade rights, Azure Hybrid Benefit, Licence Mobility, training vouchers — and assign a realistic commercial value to each. Third, compare the total value received against the SA cost. Where the value-to-cost ratio is below 1.0, the SA should be discontinued at the next natural break point.
The EA renewal conversation is the right moment for this audit because SA is typically bundled into EA negotiations rather than assessed independently. Microsoft’s commercial teams do not proactively suggest dropping SA — that reduces their revenue. Independent Microsoft licensing advisory specialists working on the buyer side are the appropriate resource for this analysis, particularly given the complexity of the 2026 pricing environment and the interaction between SA costs, the July 1 price increases, and the shift toward subscription-based models.
For most enterprise organisations in 2026, Software Assurance on desktop products is a candidate for elimination. For server products with active cloud or mobility deployments, the calculus is different and worth computing carefully before making any change. The key is to make the decision deliberately rather than renewing by default — and to understand that a well-timed EA renewal in Microsoft’s Q4 window (April to June) is the moment when that decision has the most commercial leverage behind it.
Download the Microsoft EA Renewal Playbook
Includes SA benefit audit framework and elimination criteria — independent, buyer-side only.