Microsoft Software Assurance CIO Playbook: What SA Is Still Worth in 2026

What Software Assurance Actually Is

Microsoft Software Assurance is a maintenance and benefits programme that can only be attached to perpetual (on-premises) volume licences at the time of initial purchase. It cannot be added retrospectively. Once a licence is purchased without SA and the initial window passes, that SA entitlement is gone permanently.

SA is priced as a percentage of the licence value — typically around 25 percent per year — and is renewed alongside the Enterprise Agreement. Under a standard three-year EA, SA renewal is bundled into the annual True-Up commitment, meaning most enterprise customers pay for SA whether they actively track its value or not.

The fundamental premise of SA was straightforward: pay a fixed annual fee and receive perpetual access to new product versions as Microsoft releases them, along with a portfolio of supplementary rights and services. In the on-premises software era of the early 2000s to mid-2010s, this was a compelling proposition. Windows Server and SQL Server major releases delivered material capability improvements every three to five years, SA covered the upgrade cost entirely, and the ancillary benefits — training vouchers, planning services, 24/7 support — had clear operational value.

The cloud era has fundamentally changed this calculation. Microsoft 365, Azure, and Dynamics 365 are all subscription services where upgrades are continuous and automatic. SA's version upgrade rights are irrelevant for subscription products. The ancillary benefits have been progressively retired. And Microsoft's strategic direction — pushing organisations from EA to MCA-E — will eliminate SA as a product category for many enterprise customers within the next two to three years.

The SA Benefits Landscape in 2026: What Remains, What Has Gone

Understanding the current SA benefit catalogue requires separating what Microsoft's marketing materials still describe as available from what has actually been retired. Three significant SA benefits have been permanently removed since 2021, and the trajectory is further consolidation.

Benefits Still Active in 2026

New Version Rights (Upgrade Rights). The core SA benefit — entitlement to upgrade to any new version of covered software released during the SA term — remains active. For organisations running Windows Server 2019 or 2022 on-premises, SA entitles them to Windows Server 2025 without purchasing new licences. For SQL Server, SA covers the upgrade path from SQL Server 2019 and 2022 to SQL Server 2025. Version rights are the primary reason organisations maintain SA on server software in 2026.

Azure Hybrid Benefit (AHB). The most financially significant active SA benefit. AHB allows organisations to bring their on-premises Windows Server and SQL Server licences — with active SA — into Azure, dramatically reducing the per-VM cost. For Windows Server, AHB can reduce Azure compute costs by up to 80 percent versus standard pay-as-you-go pricing. For SQL Server, AHB delivers an average 29 percent cost reduction compared to equivalent cloud-native provisioning. The AHB calculation is straightforward: one Windows Server Standard edition licence with SA covers two virtual cores in Azure, and one SQL Server Enterprise core licence covers four Azure vCores for highly virtualised workloads.

License Mobility Through Software Assurance. Allows certain server application licences — including SQL Server, Exchange Server, SharePoint Server, and Skype for Business Server — to be deployed at Authorised Mobility Partners (cloud providers including Azure, AWS, and others). This enables organisations to move workloads to cloud infrastructure without purchasing new licences. License Mobility is distinct from AHB: Mobility is for third-party authorised hosts, AHB is specifically for Microsoft Azure.

Flexible Virtualization Benefit. An extension introduced in recent years permitting deployment of Windows Server, SQL Server, and other eligible software on any Authorised Outsourcer's shared infrastructure — including multi-tenant environments — without the traditional per-server licensing constraints. This has particular value for organisations using managed hosting or third-party data centres.

Step-Up Licensing. Allows migration from a lower to a higher edition — for example, Office Standard to Office Professional Plus, or SQL Server Standard to SQL Server Enterprise — at a discounted step-up price rather than full new licence cost. Step-up remains available but its relevance is diminishing as these product categories migrate to subscription models.

Home Use Programme. Provides employees with access to Microsoft Office applications for personal home use at minimal cost during the period of active SA coverage. While operationally useful for end-user satisfaction, its financial value is limited in 2026 given the widespread adoption of M365 subscriptions that already include personal use rights across five devices.

Benefits Retired Since 2021

Three material SA benefits have been permanently withdrawn, significantly reducing the non-AHB value of SA for organisations that relied on them:

Planning Services Vouchers — Retired February 2021. Planning Services provided entitlements to structured deployment planning sessions with Microsoft-certified partners. These were tangible professional services that organisations could use for complex deployments of Windows, SharePoint, Exchange, SQL Server, and other products. Their retirement removed what was, for many organisations, the second most valuable SA benefit after version rights.

Software Assurance Training Vouchers (SATVs) — Ended January 2022. SATVs provided employees with entitlements to certified technical training at Microsoft Authorised Training Providers. An active SA agreement could generate a meaningful training budget — typically several thousand dollars per covered product — that organisations could apply against instructor-led certification courses. The end of SATVs left a gap that many organisations filled with separate training budget allocations, effectively paying for the benefit twice (once through SA, once directly).

24/7 Problem Resolution Support — Retired February 2023. SA previously included 24/7 phone support for Microsoft products, providing a direct support escalation path with guaranteed response times. This benefit had material value for organisations without Microsoft Premier or Unified Support agreements. Its retirement means SA no longer provides any operational support entitlement, only licensing and rights-related benefits.

From SA Licences — Discontinued 2024

A separate but related change: Microsoft discontinued the "From SA" licence mechanism in 2024. From SA licences were created to allow organisations to transition from on-premises perpetual licences with active SA to cloud User Subscription Licences (USLs) at a discounted price. This was particularly relevant for Microsoft 365 and Dynamics 365 migration planning. From February 2024 for Microsoft 365 products and April 2024 for Dynamics 365, organisations could no longer order new or additional From SA licences. Existing From SA licences could still be renewed, but the migration discount pathway for new transitions is closed.

The EA-to-MCA-E Transition: SA's Existential Threat

The most consequential development for Software Assurance in 2026 is not a benefit retirement — it is the structural shift from Enterprise Agreement to Microsoft Customer Agreement for Enterprise (MCA-E). Microsoft began formally notifying enterprise customers in January 2025 that renewal of certain EA configurations is no longer possible. From March 1, 2026, Microsoft is actively migrating EA customers on MACC (Microsoft Azure Consumption Commitment) plans to MCA-E.

The critical licensing consequence of MCA-E is unambiguous: Software Assurance does not exist under MCA-E. Under an MCA, organisations cannot purchase or renew SA for perpetual licences. There are no SA benefits, no Azure Hybrid Benefit through the SA mechanism (though AHB may have alternative pathways), no License Mobility through SA, and no step-up rights.

Organisations that have transitioned from EA to MCA-E without proactive negotiation have reported cost increases of 10 to 30 percent at their first MCA-E renewal. These increases stem from two compounding factors: loss of negotiated EA discounts (standard EA discounts are 10 to 20 percent off list; MCA-E starts at list price) and loss of SA-enabled cost optimisations, particularly Azure Hybrid Benefit.

Capturing SA Value Before EA Expiry

For organisations facing an EA renewal that will transition to MCA-E, the immediate priority is maximising consumption of residual SA benefits before the transition. Specifically:

• Step-up rights not yet exercised. If SA entitles you to a licence upgrade you have been deferring — for example, moving SQL Server Standard to Enterprise to support a planned consolidation — execute that upgrade before EA expiry. The residual value of an unused step-up right is zero once SA lapses.
• Home Use Programme access. Notify employees to register and download Office under HUP before the SA expiry date. Post-expiry downloads are not permitted.
• Azure Hybrid Benefit audit. Confirm every Windows Server and SQL Server workload running in Azure is correctly configured to use AHB. Misconfigured workloads are paying standard Azure pricing — often two to four times the AHB rate. Correct configuration before the transition to ensure you are maximising the benefit during the remaining SA term.
• Version upgrade execution. If SA covers a Windows Server or SQL Server upgrade that is on your roadmap within the next 18 months, prioritise executing it before EA expiry. Under MCA-E, the same upgrade requires a new licence purchase.

Product-by-Product SA Decision Framework

The question of whether to maintain SA is not an organisation-wide binary decision. It is a product-by-product financial analysis. Different Microsoft products have fundamentally different SA economics, and the right answer for Windows Server is frequently the wrong answer for Office or Windows client.

Windows Server — SA Has Strong Financial Justification

Windows Server is the clearest case for maintaining SA in a hybrid or Azure-connected environment. The Azure Hybrid Benefit calculus is straightforward: a Windows Server Datacenter licence with SA covers unlimited Azure VMs within the licence's core count. Windows Server Standard with SA covers up to two virtual machines per licence in Azure.

For an organisation with 500 Windows Server Standard licences (core-based) running workloads in Azure, the AHB saving versus standard Windows Server pricing in Azure typically exceeds the SA renewal cost within 12 to 18 months. The mathematics are compelling enough that SA on Windows Server should be the default position for any organisation with an existing Azure footprint or Azure migration in the roadmap.

The version rights dimension reinforces this: Windows Server 2025 delivers material improvements in security (security baseline hardening, enhanced SMB protocol controls), virtualisation (improved Hyper-V performance), and Azure Arc integration. Organisations still running Windows Server 2016 or 2019 on a refresh cycle have a clear SA value path.

SQL Server — SA Delivers Exceptional Azure ROI

SQL Server SA has the most mathematically compelling value case of any Microsoft product. SQL Server Enterprise Edition with SA under the AHB Highly Virtualized Workloads rule provides a four-to-one Azure vCore allocation: each on-premises SQL Server Enterprise core licence covers four Azure vCores in the General Purpose tier.

For a practical example: an organisation with 16 SQL Server Enterprise cores with SA can provision 64 Azure vCores of SQL Managed Instance or Azure SQL Database in the General Purpose tier under AHB — paying only compute costs above the base price, not the per-vCore SQL Server licence. At Azure SQL standard pricing, this equates to an annual saving well in excess of typical SA renewal costs for those 16 cores.

SQL Server 2025 also introduces meaningful capability changes, including native vector search, improved Always Encrypted performance, and enhanced AI integration through Azure OpenAI connectivity. For organisations with SQL Server on an active refresh cycle, version rights through SA remain relevant.

Microsoft 365 Products — SA Is Largely Redundant

Microsoft 365 E1, E3, E5, and the new E7 Frontier Suite are subscription licences. Subscription licences are inherently evergreen — they always include the current version of the software, receive continuous feature updates, and require no upgrade rights. SA on M365 subscription licences provides no version rights value because the subscription model already delivers that entitlement by definition.

For organisations that have perpetual Office licences (Office 2019, Office 2021) with SA, the version rights question is whether they plan to upgrade to the next perpetual release rather than migrate to M365. Microsoft's direction is unambiguous: Office perpetual licences receive only security patches, not new feature development. Microsoft 365 is the strategic product. The right question is not "should we renew SA on Office 2021?" but "should we migrate to M365?"

SA on Office is justified only if the organisation has specific business reasons for perpetual on-premises Office deployment — regulatory, network isolation, or contract-specific requirements — and plans to exercise the version upgrade rights to a future Office release. For most enterprises in 2026, this is a rapidly shrinking population.

Windows Client (Desktop) — SA Rarely Justified as Standalone

Windows 10 and 11 Pro/Enterprise perpetual licences with SA entitle organisations to upgrade to new Windows versions as they release. In practice, most enterprise Windows management is now handled through Microsoft 365 Business Premium, E3, or E5 which include Windows 11 Enterprise subscription rights directly. Paying SA on top of an M365 subscription that already provides Windows Enterprise is double-paying for the same entitlement.

The exception is organisations with large Device CAL or OEM licence estates that are not M365-licensed — manufacturing environments, kiosk deployments, or organisations using volume licences for their primary Windows provisioning rather than M365. For these environments, Windows SA version rights remain relevant.

Exchange Server and SharePoint Server — Sunset Phase

Both Exchange Server and SharePoint Server are in what Microsoft describes as their final on-premises release cycles. Exchange Server 2019 mainstream support ends October 2025 (extended security until 2026 for SA customers). SharePoint Server Subscription Edition continues, but Microsoft's development investment is concentrated in SharePoint Online and Teams.

License Mobility through SA has value for organisations using hosted Exchange or SharePoint with an Authorised Mobility Partner. Azure Hybrid Benefit applies to the Windows Server infrastructure running these workloads. But the Exchange or SharePoint application licences themselves have diminishing SA value as Microsoft constrains on-premises roadmap investment.

For organisations mid-migration from Exchange on-premises to Exchange Online, SA on Exchange Server is worth preserving only for the duration of the migration. Once migrated, the Exchange on-premises licences and their SA become legacy overhead.

The SA ROI Calculation: A Worked Framework

A rigorous SA renewal decision requires quantifying the expected value of each benefit for each product against the SA renewal cost. The calculation is straightforward in structure, though it requires accurate inventory data to execute.

Step 1: Inventory Your SA-Covered Licences

Pull your current EA product list from the Microsoft Licensing Statement (MLS) or Volume Licensing Service Centre (VLSC). Identify every product line item that includes Software Assurance. For each SA-covered product, note: the product and version, the number of licences (or cores/CALs), and the current SA renewal cost for the upcoming term.

Step 2: Calculate Azure Hybrid Benefit Value

For Windows Server and SQL Server: identify how many of these licences are currently deployed in Azure or are on an Azure migration roadmap within 24 months. Apply the AHB formula to quantify annual Azure cost avoidance. If the AHB saving exceeds the SA renewal cost for those licences, maintain SA. If the organisation has no Azure deployment or migration plan for those licences, the AHB benefit is zero and the value case relies entirely on version rights.

Step 3: Assess Version Upgrade Value

For each SA-covered product, determine whether a version upgrade is planned within the next 24 months. If so, calculate the cost of the upgrade without SA (i.e., new licence purchase) versus the cost of SA renewal. If new licence purchase cost exceeds SA renewal cost, SA provides net positive value. If no upgrade is planned within 24 months, version rights have no current value.

Step 4: Evaluate License Mobility and Flexible Virtualisation

For organisations using Authorised Outsourcers or managed hosting providers: assess which workloads depend on License Mobility for their licence compliance position. If workloads are running in cloud or managed hosting environments under License Mobility, removing SA would require either purchasing new licences or migrating those workloads. Quantify the cost of the alternative to determine License Mobility value.

Step 5: Subtract Retired Benefit Expectations

Confirm that your SA renewal analysis excludes value from Planning Services, Training Vouchers, and 24/7 support — all retired. If your SA budget historically assumed value from these benefits, the renewal cost should be recalibrated downward by the percentage that these now-defunct benefits represented.

Step 6: Model the MCA-E Timeline

If your EA is due for renewal in the next 12 to 24 months and Microsoft has indicated a transition to MCA-E, the SA renewal decision must account for the possibility that the current EA renewal is the last opportunity to hold SA. In this scenario, the SA renewal and the maximisation of SA benefits within the current term become a single time-bounded exercise.

Negotiating SA Within the Enterprise Agreement

SA renewal is not a fixed-cost item. Within an EA negotiation, SA coverage levels are negotiable, and CIOs should approach the conversation with specific data on which product lines have justified ROI and which do not.

Product-Level SA Carve-Outs

It is operationally and contractually acceptable to decline SA on specific products within an EA while maintaining it on others. Microsoft's field teams prefer blanket SA coverage for simplicity, but nothing in the EA licence terms mandates uniform SA across all products. Organisations routinely exclude SA from product lines where the ROI analysis is negative — most commonly Office perpetual, Windows client in M365-licensed environments, and legacy server applications in end-of-life phases.

Timing Within Microsoft's Fiscal Year

Microsoft's fiscal year ends June 30. The Q4 pressure window — April 1 through June 30 — represents the highest leverage period for buyers. Microsoft field representatives have maximum incentive to close and discount in Q4. EA renewals negotiated during this window, particularly for organisations with True-Up dates in the spring and summer, should use this calendar leverage to negotiate SA terms, including product-level carve-outs and pricing adjustments on SA renewal rates.

We are currently in Microsoft's Q4 2026 window. If you have an EA renewal or True-Up negotiation scheduled, April through June 2026 is precisely the window where Microsoft's closing pressure creates buyer leverage.

SA vs. MCA-E: Using SA as Negotiation Currency

For organisations that Microsoft is pushing toward MCA-E, the retention of an EA with SA is a negotiating position, not just a commercial preference. Microsoft's field teams receive revenue credit for MCA-E conversions. Organisations willing to extend their EA — which requires maintaining SA — have leverage to negotiate better MCA-E transition terms, including price protection clauses, extended transition timelines, and contractual commitments on AHB availability post-transition.

Organisations that transition to MCA-E without negotiation have consistently reported 10 to 30 percent cost increases at first MCA-E renewal. The transition negotiation is where SA's residual value can be converted into MCA-E price protections rather than simply forfeited.

Software Assurance in the M365 SKU Context

Understanding SA's role in 2026 requires setting it against the current Microsoft 365 SKU stack: E1, E3, E5, and the new E7 Frontier Suite. Microsoft's SKU strategy increasingly embeds what would previously have been separate add-ons — security features, compliance tools, AI capabilities — directly into higher-tier subscriptions.

E7, released above E5 as the new top-tier M365 SKU, bundles Microsoft 365 Copilot ($30/user/month if purchased separately), advanced security features previously requiring E5 Security add-ons, and Agent 365 capabilities. For organisations on E5 that Microsoft is now upselling toward E7 at renewal, the SA question for any on-premises infrastructure running alongside the M365 estate becomes more urgent: as subscription spend increases, the opportunity cost of paying SA on licences with no active benefit becomes more visible.

Microsoft's field motion in 2026 follows a predictable pattern: upsell M365 E5 customers to E7 at renewal while simultaneously positioning MCA-E as the vehicle for that commercial relationship. CIOs should model the total cost picture — M365 subscription tier, on-premises infrastructure SA, Azure workload costs — as a unified analysis rather than separate procurement decisions.

The Seven-Question SA Decision Checklist

Before your next EA renewal or True-Up, work through these seven questions for every SA-covered product line:

1. Do we run this product in Azure or are we planning Azure migration within 24 months? If yes for Windows Server or SQL Server, AHB through SA is likely ROI-positive. Calculate specifically before deciding.
2. Is a version upgrade to the next major release planned within 24 months? If yes, compare new licence cost without SA against SA renewal cost. If the upgrade is not planned, version rights have zero current value.
3. Do we use License Mobility or Flexible Virtualisation for this product? If workloads are hosted at an Authorised Outsourcer under Mobility, removing SA requires re-licensing or migration. Quantify the alternative cost.
4. Is this product on a subscription trajectory within 24 months? If the product is being migrated to a subscription SKU — Office 2021 to M365, Exchange on-premises to Exchange Online — SA on the perpetual licence has a defined expiry for relevance.
5. Are we being migrated to MCA-E at the next renewal? If yes, the current SA term is your last window to exercise residual SA benefits. Create an extraction plan to capture all remaining value before expiry.
6. Have we excluded retired benefits from our SA value calculation? Remove Planning Services, SATVs, and 24/7 support from any SA ROI model. These are gone and will not return.
7. Is our EA renewal falling in Microsoft's Q4 window (April–June)? If yes, the timing provides negotiation leverage. Use it to negotiate product-level SA carve-outs, pricing adjustments, and MCA-E transition protections simultaneously.

What Independent Assessment Looks Like

In our Microsoft EA advisory practice, an SA assessment follows a structured methodology. We begin with an inventory of every SA-covered line item from the current Licensing Statement, then model AHB savings for all Windows Server and SQL Server products against current Azure billing data. Where organisations have not yet migrated but have a defined Azure roadmap, we model AHB value against projected workload counts.

The typical output of this analysis is the identification of two to four product lines where SA can be removed at next renewal without licence compliance risk, representing 15 to 35 percent of total SA renewal cost. We also commonly identify Windows Server or SQL Server deployments in Azure that are not correctly configured for AHB, where correcting the configuration immediately reduces Azure billing and validates the ongoing SA investment.

Where organisations face an MCA-E transition, we model the total cost impact of transition timing, negotiate price protection clauses that preserve AHB equivalent savings post-transition, and structure the final EA renewal to extract maximum SA benefit before the transition closes the window.

Software Assurance is neither a wholesale keep nor a wholesale drop. It is a portfolio of entitlements, each of which should be evaluated independently against current and planned deployment realities. The organisations that manage SA strategically — selectively, with clear ROI data and precise execution timing — consistently outperform those that treat it as a fixed overhead line item.