Microsoft Software Assurance:
Retain, Optimize, or Retire?

SA in Volume Licensing: What It Was Built For

Microsoft Software Assurance is a software maintenance and benefits program available through volume licensing. It provides an insurance policy on software investments by bundling upgrade rights and additional perks for a fixed annual fee, typically around 25% of the license cost per year. Organizations pay extra upfront or annually and, in return, receive automatic access to new versions, deployment resources, support, training, and more. SA spans a broad range of Microsoft products including Windows, Office, and server software, and has historically been the mechanism for keeping enterprise IT current and supported.

In Microsoft's traditional Enterprise Agreement (EA), designed for 500+ users, SA is automatically included with license purchases. This made EAs the popular choice for large enterprises, as they always had rights to the latest software and extra support. Similarly, under the Microsoft Products and Services Agreement (MPSA) and earlier programs such as Select Plus, customers could opt for SA to secure these advantages. SA became synonymous with future-proofing software assets. Organizations did not need to worry about surprise costs for the next Windows or Office upgrade because it was covered.

The flagship benefit was new version rights: the right to deploy all new version releases of covered products during the SA term. Windows, Office, server editions, all upgradeable without new license purchases. Training vouchers provided free training days with Microsoft Certified Partners. Deployment planning vouchers gave consulting time for migrations. License Mobility allowed reassigning certain server application licenses across servers or to third-party cloud providers, a critical enabler for hybrid and multi-cloud strategies that standard licenses did not allow. Included 24/7 support incidents covered critical issues, and disaster recovery rights permitted installing server products on standby without additional licenses.

SA was highly relevant in the era when software was primarily on-premises and major version upgrades were significant events. It kept enterprise customers current, supported, and locked into the Microsoft ecosystem. The question for 2026 is whether it still delivers that same value in a cloud-first world.

What Has Been Retired, What Remains

Over the past few years, Microsoft has made significant changes to Software Assurance benefits, driven by the shift to cloud services and new support models. Many traditional SA benefits have been retired, replaced, or transformed. Understanding what remains and what does not is essential for making informed EA optimization decisions.

Four major SA value-adds were retired between 2021 and 2023. Training Vouchers (SATV) ended in February 2021, with final redemption by January 2022. Microsoft replaced them with free Microsoft Learn online training, which is available to all customers regardless of SA status. E-Learning Courses were retired alongside SATV. Deployment Planning Services ended in February 2021, replaced by FastTrack for cloud deployment assistance. On-premises planning now requires paid professional services. And 24x7 Problem Resolution Support ended in February 2023. SA no longer provides free support incidents. Customers must purchase Unified Support or pay per incident. For large enterprises, annual Unified Support costs can run $100,000 to over $1 million depending on scope. Support costs that were previously bundled in SA are now a separate, visible line item.

What remains is a leaner set of core benefits focused on license rights rather than service perks. New Version Rights remain the headline benefit for perpetual license holders, allowing deployment of any release during the SA term at no additional cost. License Mobility continues to permit moving certain server application licenses to third-party cloud providers (AWS, GCP, hosting). Azure Hybrid Benefit requires SA or subscription licenses and delivers 30-50% savings on eligible Azure workloads. Disaster Recovery Rights allow cold standby instances for DR without additional license fees. Step-Up Licenses let you upgrade editions (Standard to Enterprise) by paying the price difference. The Workplace Discount Program (rebranded from Home Use Program) gives employees discounted M365 Personal and Family subscriptions.

MDOP expires in April 2026. The Microsoft Desktop Optimization Pack, a suite of tools including App-V, MED-V, UE-V, and DaRT, remains available to customers with Windows licenses under SA only until April 2026. After that date, MDOP is deprecated. Organizations currently relying on App-V for application virtualization should plan their transition to alternatives such as MSIX or Azure Virtual Desktop before this deadline. For most enterprises that have already migrated to Microsoft 365 E3/E5, which includes Windows Enterprise and modern management via Intune, MDOP's relevance has already diminished.

Where SA Is Still Required and Valuable

Despite the erosion of many benefits, Software Assurance remains essential or highly valuable in specific scenarios. The key is identifying precisely where SA still delivers measurable ROI versus where it has become legacy overhead.

Perpetual license upgrade rights for server and database products. If the organization runs perpetual licenses for on-premises server software, particularly Windows Server and SQL Server, SA is the most cost-efficient way to stay current. Without SA, upgrading from Windows Server 2019 to 2025 or SQL Server 2019 to 2022 requires purchasing entirely new licenses. SA's new version rights allow deployment of any release during the term at no additional cost. This is especially critical given Microsoft's increasingly aggressive end-of-support timelines. SQL Server 2016 reaches end of support in July 2026, and Office LTSC 2021 in October 2026. Organizations running these versions without SA will face the choice of buying new licenses at full price, purchasing Extended Security Updates (ESU), or accepting unpatched security risk. For SQL Server Enterprise at ~$15,000 per 2-core pack, SA at ~$3,750/year beats a full repurchase within 4 years.

Azure Hybrid Benefit delivers 30-50% cloud cost savings. If the strategy involves significant Azure usage, AHB is one of the strongest reasons to maintain SA on server products. AHB allows reusing existing Windows Server and SQL Server licenses in Azure VMs and Azure SQL services, paying only the base compute rate instead of the full license-included rate. A Windows Server Datacenter license with SA can cover up to two Azure VM instances, dramatically reducing cost. SQL Server licenses with SA can be applied to Azure SQL Database or SQL Managed Instance at a fraction of the normal price. AHB also allows concurrent use during migration: you can run a license both on-premises and in Azure for up to 180 days when actively migrating a workload. This dual-use provision prevents downtime costs during cloud transitions.

License Mobility enables multi-cloud flexibility. Organizations pursuing a hybrid or multi-cloud strategy may need SA for its License Mobility benefits. Deploying an on-premises license on a third-party cloud such as AWS or Google Cloud requires that SA cover the license. This enables bring-your-own-license (BYOL) scenarios for SQL Server, Exchange, SharePoint, and other server applications on authorized cloud providers. In 2022, Microsoft introduced the Flexible Virtualization Benefit (FVB), which expanded License Mobility by allowing SA-covered licenses to be used on any cloud provider's infrastructure except a short list of "Listed Providers." Note that License Mobility does not cover Windows Server itself. You cannot bring your own Windows Server license to a multi-tenant cloud VM. Windows Server BYOL requires dedicated hardware arrangements or Azure Hybrid Benefit specifically. Plan accordingly for virtualized environments.

Virtualization, failover, and disaster recovery rights. In on-premises contexts, SA provides advanced use rights that standard licenses do not include. License reassignment flexibility: standard licenses without SA can only be moved between servers every 90 days, while SA often waives this restriction, which is critical for virtualized server farm environments using VMware vMotion or Hyper-V Live Migration. For SQL Server, SA allows a passive secondary server for high availability without additional licensing. For Windows Server, SA enables standby instances for disaster recovery. SQL Server 2022 licensing changes now explicitly require SA for licensing at the virtual machine level ("License by vCore"). Without SA, organizations must fully license all physical host cores, an extremely costly approach that negates virtualization benefits.

Extended Security Updates and legacy support. SA can be a prerequisite for purchasing Extended Security Updates for products past end-of-life. With SQL Server 2016 reaching end of support in July 2026 and the final ESU year for Windows Server 2012/R2 ending October 2026, organizations with legacy systems should evaluate whether SA provides a safety net for obtaining critical security patches during transition periods. Azure also offers free ESU for 3 years when you migrate legacy workloads to Azure VMs, another reason to maintain SA during cloud migration using AHB to move the workload and then receiving free ESU in Azure.

License Mobility Versus Azure Hybrid Benefit: Different Tools, Different Clouds

Two of SA's most significant benefits in 2026 relate to hybrid cloud scenarios. License Mobility and Azure Hybrid Benefit both involve using existing licenses in cloud environments, but they serve different purposes and apply in different contexts. Understanding the distinction is essential for optimizing your cloud licensing strategy.

License Mobility applies to third-party clouds. It covers server applications (SQL Server, Exchange, SharePoint, Dynamics) deployed to AWS, GCP, or hosting providers. It requires active SA at the time of migration. Concurrent use is not permitted: the on-premises deployment must be decommissioned. Typical savings come from avoiding re-licensing on the cloud provider, which usually represents 20-40% cost avoidance. The Flexible Virtualization Benefit (2022) expanded these rights to any outsourcer's infrastructure except a short list of restricted providers.

Azure Hybrid Benefit applies to Microsoft Azure only. It covers Windows Server, SQL Server, and other Azure services. It requires SA or equivalent subscription licenses. Crucially, it permits up to 180 days of concurrent use during active migration, meaning you can run both on-premises and Azure simultaneously during the transition. Typical savings range from 30-50% reduction on Azure VM and SQL costs. AHB has been extended to Azure VMware Solution and Azure Stack HCI as well.

They are complementary, not interchangeable. One is for non-Azure clouds. One is for Azure. Both require SA or subscription coverage. Without SA, moving a SQL Server workload to AWS means paying the cloud provider's license-included rate, often 2-3x the BYOL cost. Moving to Azure without AHB means paying the full Azure VM rate which includes Windows and SQL licensing at Microsoft's prices.

Consider a mid-size enterprise running 50 SQL Server Enterprise 2-core packs across on-premises and multi-cloud environments. Annual SA cost is approximately $187,500. Benefits realized: 30 cores on Azure SQL with AHB saves roughly $280,000/year versus pay-as-you-go pricing. 20 cores on AWS via License Mobility BYOL saves approximately $120,000/year versus license-included EC2. And SQL Server 2022 deployment completed at no additional license cost avoids roughly $375,000 in repurchases. Total annual SA cost: $187,500. Total annual value realized: $775,000+. SA delivers a 4:1 return on investment in that scenario, but only because the organization actively uses all three benefit categories.

2026 Context: EA Changes, M365 Price Hikes, and Copilot Costs

Software Assurance decisions do not exist in isolation. They are part of a broader Microsoft cost picture that has shifted dramatically in 2025-2026. Several concurrent changes compound the financial pressure on enterprise buyers and affect how SA value should be calculated.

November 2025: EA volume discount tiers eliminated. Levels B, C, and D were removed for online services. All EA customers now pay Level A (list) pricing regardless of volume. Large enterprises previously enjoying 10-25% automatic discounts face 6-12% immediate cost increases at renewal. This is the single largest pricing change Microsoft has made to the EA program in its history.

April 2025: 5% monthly billing premium. Annual subscriptions paid on monthly billing cycles now cost 5% more across CSP, MCA-E, and Web Direct. Power BI Pro increased 40% ($10 to $14/user/month). Teams Phone increased 25%.

July 2026: M365 price increases of 5-8%. Microsoft 365 E3 increases approximately 8.3%, E5 increases approximately 5.3%. Combined with the volume discount elimination, large enterprises face 15-23% effective increases depending on their previous discount level.

2025-2026: Copilot add-on costs. Microsoft 365 Copilot is priced at $30/user/month, nearly as much as an E3 license. Security Copilot is licensed by capacity at tens of thousands annually. These AI costs layer on top of existing spend without replacing anything in the current stack.

2025-2026: EA-to-MCA-E migration push. Microsoft is pushing EA customers toward the Microsoft Customer Agreement for Enterprise (MCA-E). Under MCA, SA benefits do not apply the same way. Subscriptions replace the perpetual+SA model. CIOs should understand how each SA benefit translates (or does not) before agreeing to a program transition.

What this means for SA decisions. The volume discount elimination applies to online services only, not on-premises perpetual licenses with SA. SA pricing for Windows Server, SQL Server, and other on-prem products is not directly impacted. CIOs should use this as leverage in negotiations. With Azure costs rising due to Level A pricing, the Azure Hybrid Benefit savings from SA become relatively more valuable. The 30-50% AHB discount offsets a larger absolute dollar amount when baseline Azure prices increase. If Microsoft moves the organization from EA to MCA-E, the perpetual+SA model gives way to pure subscriptions, and the SA exit strategy should be planned alongside any MCA migration timeline. In renewal negotiations, offer to move SA spend to cloud commitments as a bargaining chip. Microsoft's goal is cloud revenue. Trading SA for better M365/Azure pricing can benefit both parties.

Microsoft's Shift to Subscriptions and SA's Diminishing Relevance

Microsoft has been aggressively pushing customers toward subscription-based licensing: Microsoft 365, Dynamics 365, and Azure consumption. This cloud-centric shift has a profound impact on SA's relevance, as subscriptions inherently include many benefits that SA used to provide uniquely.

Microsoft 365 makes desktop SA largely redundant. With M365, customers no longer purchase perpetual Office licenses. They subscribe to Microsoft 365 Apps, which is continually updated. Upgrade rights are built in. You always have the latest version. Similarly, M365 E3/E5 subscriptions include Windows 10/11 Enterprise as a user-based license, providing virtualization rights, regular updates, and version flexibility. No separate SA is needed. The subscription covers it. Organizations that have moved to M365 have found that SA for client software is no longer relevant. Under newer agreements (MCA, CSP), SA is not even an option for cloud subscriptions.

Azure and server subscriptions bypass SA entirely. On the server side, Azure IaaS and PaaS means you do not buy Windows Server or SQL Server licenses outright. They are part of the service cost. Microsoft has introduced server subscriptions for on-premises use via CSP, granting 1-3 year rights including upgrades without using the SA construct. SQL Server's new pay-as-you-go option via Azure Arc integration allows on-premises licensing through Azure's consumption model. These subscription alternatives mean the classical SA program is increasingly bypassed.

The shrinking SA attach rate reflects this reality. If 70% of your Microsoft spend is M365 and Azure, only the remaining on-prem servers carry SA. And even those may be candidates for Azure migration or subscription conversion. The SA spend portion of enterprise agreements has been shrinking relative to cloud subscription spend for years. Microsoft has reinforced this trend by reducing SA incentives, retiring training, planning, and support benefits. The message is clear: Microsoft sees SA as a transitional mechanism, not a long-term product. Organizations should plan accordingly, treating SA as a bridge to cloud rather than a permanent fixture.

SA adds ~25% to license cost annually. Over four years, that is equivalent to buying the license again. If during that period you have not used any SA benefit, no upgrades deployed, no AHB activated, no License Mobility exercised, that money is wasted. The shift to cloud makes this increasingly common. Why pay SA on SharePoint Server if you are migrating to SharePoint Online next year? A practical test: for each SA-covered product, ask what would happen if SA were dropped today. If the answer is "nothing changes for 2+ years," that is a strong signal to retire SA on that product and redirect the spend. See our EA optimization service for product-by-product analysis.

Retain or Retire: The 2026 Decision Framework

The ultimate question: where should you keep paying for SA, and where can you safely drop it? The answer varies by product, by deployment scenario, and by cloud strategy. What follows is a structured framework for making this decision across your entire Microsoft estate.

Retain SA on core on-premises products you will upgrade. Keep SA for Windows Server, SQL Server, and other server software where new versions are anticipated and you plan to deploy them. SA's upgrade rights cost less than repurchasing licenses every few years. If you expect to upgrade an on-premises server product within the next 3 years, SA almost certainly costs less than purchasing a new license.

Retain SA for hybrid and multi-cloud deployments. Keep SA for any licenses you will use in Azure (for AHB) or in AWS/GCP (for License Mobility). Dropping SA could lock workloads to your datacenter or force significantly higher cloud costs. The 4:1 ROI scenario described earlier is achievable only when SA is active on the licenses being deployed to cloud.

Retain SA for virtualization and HA/DR requirements. Keep SA for SQL Server and Windows Server in heavily virtualized environments. The License by vCore benefit requires SA, and without it, you would need to license all physical host cores, an extremely costly approach. Mission-critical applications running on-premises should have their HA/DR licensing requirements verified against SA coverage.

Retain SA where no subscription alternative exists. Some products, specialized server tools, certain developer platforms, have no cloud or subscription equivalent. If the product is mission-critical and you need ongoing updates, SA remains your lifeline.

Let SA lapse on workloads migrating to cloud within 1-2 years. If you have a concrete plan to decommission on-premises licenses for cloud services, continuing SA is wasted spend. Time the SA drop to align with migration completion.

Let SA lapse on stable legacy products with no planned upgrade. Systems running in steady state, manufacturing floor controllers, dedicated appliances, environments that will not be upgraded for 5+ years, do not need SA. You can run the perpetual license indefinitely without it.

Let SA lapse on products already migrated to subscriptions. If you have moved from Office 2019 to M365, or from on-premises Exchange to Exchange Online, drop SA on the old perpetual licenses. You are paying double otherwise.

Let SA lapse where the cost outweighs realized benefits. If you have been paying SA for years without deploying an upgrade, using AHB, or exercising mobility, the cumulative waste exceeds the cost of repurchasing when you eventually need it.

Maximize the value from SA you retain. Activate Azure Hybrid Benefit on every eligible VM. This is the single highest-ROI action for SA holders using Azure. Work with cloud architects to verify that AHB is enabled for every eligible Azure VM and database service. Monitor new deployments to ensure AHB is applied by default. Time upgrades to your SA window. If you renewed SA on Windows Server in 2025 through 2028, you are entitled to any release during that window. Do not leave upgrade rights on the table. Leverage Step-Up licenses to upgrade editions (SQL Standard to Enterprise) by paying only the price difference rather than a full new license. Promote the Workplace Discount Program to employees for discounted M365 Personal and Family subscriptions at zero incremental cost to the company.

SA re-enrollment is possible at future renewals. You can typically re-enroll licenses in SA at the next Enterprise Agreement renewal by purchasing an SA-only SKU. However, you can usually only add SA to the current version of a product. If you dropped SA on SQL Server 2019 and SQL Server 2025 has since released, you may need to purchase a full new license for SQL 2025 before adding SA. Long gaps without SA can result in higher catch-up costs. Make bold optimization decisions now, but document your rationale and revisit at each renewal cycle.

CIO Strategic Action Plan for 2026

Perform an SA value assessment before every EA renewal. For each product, map SA cost against benefits used. Include app owners, infrastructure, cloud strategy, and finance. Use the four-question decision framework to retain or retire each product's SA. A selective approach, keeping SA where it delivers measurable ROI and dropping it everywhere else, is both acceptable and optimal. Blanket coverage is no longer defensible.

Maximize Azure Hybrid Benefit immediately. Audit every Azure VM and SQL deployment for AHB eligibility. Enable it by default on all new deployments. This single action often recoups the entire cost of maintaining SA on server products. In our assessments, we typically find 30-50% of eligible VMs do not have AHB activated, representing direct, recoverable savings.

Account for retired benefits in your budget. Training, planning services, and support incidents are gone from SA. Budget separately for Unified Support, third-party training, and professional services that SA previously bundled. CIOs whose IT budgets still assume these resources exist should update their plans immediately.

Plan cloud migrations with SA timelines in mind. Maintain SA on workloads during migration for dual-use rights and AHB, then drop SA once migration completes. Coordinate SA renewal dates with project milestones to avoid paying for coverage you will not use. This requires collaboration between the SAM team, cloud migration team, and procurement.

Use SA as negotiation leverage. When renewing your Enterprise Agreement, offer to redirect SA spend toward cloud commitments. Microsoft wants cloud revenue. Trading perpetual+SA for better M365/Azure pricing can benefit both parties. This is particularly effective in the current environment where Microsoft is actively encouraging EA-to-MCA transitions.

Watch the EA-to-MCA transition closely. If Microsoft moves the organization to MCA-E, understand how SA benefits translate (or do not) to the new model. Plan your SA exit strategy alongside any program migration. Under MCA, subscriptions replace perpetual+SA. On-premises perpetual licenses may still require SA for upgrade and mobility rights, and Microsoft may propose a mixed model with MPSA for on-prem alongside MCA for cloud.

Monitor policy changes proactively. Microsoft regularly updates License Mobility, AHB, and FVB rules. The Flexible Virtualization Benefit expanded some rights in 2022, but future changes could restrict others. Subscribe to licensing news or work with independent advisors to stay ahead of changes that could affect your rights.

Avoid double-paying. If you have migrated to M365, Exchange Online, or Azure SQL, drop SA on the corresponding perpetual licenses. Maintain awareness of overlap periods but never pay for both subscription and SA for the same workload beyond the transition window.

Engage independent licensing expertise. Microsoft licensing complexity is at an all-time high. Volume discount elimination, MCA transitions, Copilot pricing, evolving AHB rules, server subscription alternatives. Independent advisors can benchmark your SA utilization against industry peers, identify waste, and negotiate better terms. The ROI on expert guidance typically exceeds 5:1 for large enterprises.