📋 Executive Summary
Microsoft Software Assurance has been a cornerstone of enterprise volume licensing for over two decades, bundling upgrade rights, cloud mobility, and operational benefits for a ~25% annual fee on top of license costs. But SA's value equation has fundamentally shifted in 2025–2026. Training vouchers, planning services, and included support incidents have all been retired. Microsoft's elimination of EA volume discount tiers (November 2025) and the upcoming July 2026 M365 price increases of 5–8% compound the pressure on enterprise budgets.
What remains of SA is a leaner, license-rights-focused program: new version upgrade rights, Azure Hybrid Benefit (delivering 30–50% cloud savings), License Mobility for multi-cloud deployments, and disaster recovery rights. For CIOs, the decision is no longer "keep or drop SA" — it's "where does SA still deliver measurable ROI, and where should we redirect that spend to subscriptions?" This playbook provides the framework.
📑 Table of Contents
- SA in Volume Licensing: Historical Role & Purpose
- Recent Changes: Retired vs. Remaining Benefits
- Where SA Is Still Required & Valuable
- SA & Hybrid Cloud: License Mobility vs. Azure Hybrid Benefit
- 2026 Context: EA Changes, M365 Price Hikes & Copilot Costs
- Microsoft's Shift to Subscriptions & SA's Diminishing Relevance
- Retain or Retire? Making the SA Decision in 2026
- CIO Recommendations
- Frequently Asked Questions
1. SA in Volume Licensing: Historical Role & Purpose
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. In practical terms, 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.
SA's Role in Enterprise Agreements & MPSA
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 didn't need to worry about surprise costs for the next Windows or Office upgrade because it was covered.
New Version Rights
The flagship benefit — rights to all new version releases of covered products during the SA term. Ensured organizations could always upgrade to the latest Windows, Office, or server editions without new license purchases.
Training & Planning Services
Free training days with Microsoft Certified Partners, e-Learning courses, and deployment planning vouchers for consulting on migrations. (Now retired — replaced by Microsoft Learn and FastTrack.)
License Mobility
Right to reassign 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.
24/7 Support & DR Rights
Included support incidents for critical issues, plus disaster recovery (cold backup) rights to install server products on standby without additional licenses. (Support incidents now retired — Unified Support required.)
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.
SA was Microsoft's way of keeping enterprise customers invested in the ecosystem while ensuring they were always well-supported and up-to-date. In 2026, the same lock-in effect persists, but the value proposition has narrowed considerably. CIOs should now evaluate SA product-by-product rather than treating it as a blanket cost of doing business. Our Microsoft optimization advisors routinely find that 30–40% of SA spend delivers no measurable return in organizations that have already shifted substantially to M365 and Azure.
📋 Unsure what SA benefits you're actually using? Our team runs free SA utilization assessments for enterprise clients.
Microsoft Optimization →2. Recent Changes: Retired vs. Remaining Benefits
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 doesn't — is essential for making informed EA optimization decisions.
| SA Benefit | Status | Notes / Replacement |
|---|---|---|
| New Version Rights (Upgrade Rights) | ✅ Active | Core to SA: allows upgrading to new on-prem software versions (Windows Server, SQL Server, Office perpetual) released during term. Critical for organizations on perpetual licenses. |
| License Mobility (Third-Party Cloud) | ✅ Active | Permits moving certain server application licenses to authorized cloud providers (AWS, GCP, hosting). Virtualization rights expanded via Flexible Virtualization Benefit (2022). |
| Azure Hybrid Benefit (AHB) | ✅ Active | Requires SA or subscription licenses. Reuse on-prem licenses in Azure VMs/SQL at reduced cost — savings of 30–50% on eligible workloads. Key cloud cost optimization lever. |
| Disaster Recovery Rights | ✅ Active | Cold standby instance for DR without additional license fee. Ensures HA/DR setups don't double licensing cost. |
| Step-Up Licenses | ✅ Active | Upgrade editions (Standard → Enterprise) by paying the price difference. Only available with active SA. |
| Workplace Discount (Home Use) | ✅ Active | Rebranded from Home Use Program. Employees get discounted M365 Personal/Family subscriptions. Aligned with subscription model. |
| MDOP (Desktop Optimization Pack) | ⚠️ Expiring | Available until April 2026 for Windows licenses with SA. After that, these tools are deprecated. |
| Enterprise Source Code Access | ⚠️ Limited | Available only for very large customers (10,000+ desktops with SA). Niche benefit; most organizations won't use. |
| Training Vouchers (SATV) | ❌ Retired | Retired Feb 2021. Final redemption by Jan 2022. Replaced by free Microsoft Learn online training. |
| E-Learning Courses | ❌ Retired | Retired alongside SATV. Microsoft Learn platform provides free web-based training for all customers. |
| Planning Services (DPS) | ❌ Retired | Retired Feb 2021. Replaced by FastTrack for cloud deployment assistance. On-prem planning now requires paid services. |
| 24×7 Problem Resolution Support | ❌ Retired | Retired Feb 2023. SA no longer provides free support incidents. Customers must purchase Unified Support or pay per incident. |
Between 2021 and 2023, Microsoft retired four major SA value-adds — training vouchers, deployment planning, e-learning, and included support. These historically represented significant operational value beyond raw upgrade rights. CIOs whose IT budgets still assume these resources exist should update their plans immediately. Training is now free via Microsoft Learn. Support now requires a Unified Support contract — often costing $50,000–$500,000+ annually depending on organization size.
What remains is a leaner set of core SA benefits focused on license rights rather than service perks. The upgrade rights remain the headline benefit for perpetual license holders. License Mobility and Azure Hybrid Benefit remain highly relevant for hybrid cloud scenarios. But the retirement of services has fundamentally reduced the total value proposition.
Impact on Your SA Cost-Benefit Calculation
At ~25% of license cost per year, SA equates to buying the license again every four years. With four major service benefits now retired, the breakeven calculus changes dramatically. If you're paying SA on a product simply for upgrade rights, you need to verify: (a) that a new version will actually release during your term, (b) that you'll deploy it, and (c) that the upgrade cost would exceed your cumulative SA payments.
Example: A $6,000 SQL Server Standard license with SA costs ~$1,500/year or $4,500 over 3 years. If you plan to upgrade to SQL Server 2025, that upgrade would cost a new license (~$6,000+). SA pays for itself. But if you plan to migrate to Azure SQL within 2 years, you're paying $3,000 in SA for an upgrade you'll never use — unless you leverage Azure Hybrid Benefit to offset Azure costs.
Unified Support: What Replaced SA's Free Incidents
Microsoft's retirement of SA support incidents was part of a broader shift to the Unified Support model — an account-wide, paid support offering covering both cloud and on-premises services. Unified Support replaces Premier Support and is priced based on organization size, product portfolio, and support tier. For large enterprises, annual Unified Support costs can run $100,000 to $1M+ depending on scope.
This means support costs that were previously "bundled" in SA are now a separate, visible line item. CIOs should factor this into their total Microsoft cost analysis. For guidance on negotiating Unified Support terms, see our Microsoft Unified Support negotiation advisory.
MDOP Expiration — April 2026 Deadline
The Microsoft Desktop Optimization Pack (MDOP) — 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. But confirm with your desktop team that no critical dependency exists before letting this benefit lapse.
3. Where SA Is Still Required & 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's become legacy overhead. Here are the scenarios where SA still matters most:
Perpetual License Upgrade Rights — Server & Database
If your 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 your 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.
Rule of thumb: 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. 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 — Cloud Cost Savings (30–50%)
If your strategy involves significant Microsoft Azure usage, Azure Hybrid Benefit (AHB) is one of the strongest reasons to maintain SA on server products. AHB allows you to reuse 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. The savings are substantial — typically 30–50% on eligible workloads compared to paying full Azure rates.
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.
2026 context: With EA volume discounts eliminated since November 2025, Azure costs are rising for many enterprises. AHB becomes even more valuable as a mechanism to offset higher baseline pricing. Ensure every eligible Azure deployment has AHB enabled — our optimization assessments frequently identify missed AHB savings.
License Mobility — Multi-Cloud Flexibility
Organizations pursuing a hybrid or multi-cloud strategy may need SA for its License Mobility benefits. If you want to deploy an on-premises license on a third-party cloud — such as AWS or Google Cloud — Microsoft 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 on License Mobility by allowing SA-covered licenses to be used on any cloud provider's infrastructure (including non-Authorized ones) except a short list of "Listed Providers." FVB reinforces that having SA is the key to unlocking flexible cross-cloud use of licenses.
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.
Server Farm Flexibility, Failover & DR Rights
In purely on-premises contexts, SA provides advanced use rights that standard licenses don't include. License reassignment flexibility: standard licenses without SA can only be moved between servers every 90 days; SA often waives this restriction, which is critical for virtualized "server farm" environments using VMware vMotion or Hyper-V Live Migration.
Failover rights: For products like SQL Server, SA allows a passive secondary server for high availability without additional licensing. For Windows Server, SA enables the use of standby instances for disaster recovery. CIOs running mission-critical applications on-premises should verify whether SA is needed to cover their HA/DR environments.
Additionally, 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 & Legacy Support
SA can be a prerequisite for purchasing Extended Security Updates (ESU) for products past end-of-life. Windows Server 2012/R2 ESUs, for example, required active SA or subscription coverage. 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). This is particularly relevant for organizations that cannot upgrade legacy systems by their end-of-support date due to application compatibility constraints.
📋 Not sure which of your licenses still need SA? Our advisors map every SA benefit to your specific infrastructure and cloud roadmap.
EA Optimization →4. SA & Hybrid Cloud: License Mobility vs. Azure Hybrid Benefit
Two of SA's most significant benefits in 2026 relate to hybrid cloud scenarios: License Mobility and Azure Hybrid Benefit. While both involve using existing licenses in cloud environments, they serve different purposes and apply in different contexts. Understanding the distinction is essential for optimizing your cloud licensing strategy.
| Dimension | License Mobility | Azure Hybrid Benefit |
|---|---|---|
| Applies To | Third-party clouds (AWS, GCP, hosting providers) | Microsoft Azure only |
| Products Covered | Server applications (SQL, Exchange, SharePoint, Dynamics). Not Windows Server OS. | Windows Server + SQL Server + other Azure services |
| Requires SA? | Yes — active SA required at time of migration | Yes — SA or equivalent subscription licenses required |
| Concurrent Use | Not permitted (must decommission on-prem) | Up to 180 days dual-use during active migration |
| Typical Savings | Avoids re-licensing on cloud provider (20–40%) | 30–50% reduction on Azure VM/SQL costs |
| 2022+ Enhancement | Flexible Virtualization Benefit expands to any outsourcer | Extended to Azure VMware Solution, Azure Stack HCI |
How They Work Together
License Mobility and AHB are complementary: one for non-Azure clouds, one 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–3× the BYOL cost), and moving to Azure without AHB means paying the full Azure VM rate (which includes Windows/SQL licensing at Microsoft's prices).
Cost Scenario — Multi-Cloud Strategy with SA
A mid-size enterprise runs 50 SQL Server Enterprise 2-core packs across on-premises and multi-cloud environments. Annual SA cost: ~$187,500. Benefits realized:
• Azure: 30 cores on Azure SQL with AHB → saves ~$280,000/year vs. pay-as-you-go pricing
• AWS: 20 cores on AWS via License Mobility BYOL → saves ~$120,000/year vs. license-included EC2
• Upgrade rights: SQL Server 2022 deployment completed at no additional license cost → avoided ~$375,000 repurchase
Total annual SA cost: $187,500. Total annual value realized: $775,000+. In this scenario, SA delivers a 4:1 return on investment — but only because the organization actively uses all three benefit categories.
The critical mistake we see is organizations paying for SA but not activating AHB on eligible Azure deployments. In our Microsoft optimization engagements, we routinely find that 30–50% of Azure VMs that qualify for AHB don't have it enabled — essentially leaving money on the table while paying for the SA that enables it. Cloud architects and SAM teams need to collaborate to ensure every eligible deployment uses AHB. This single action can recoup the entire cost of SA.
Microsoft's broader strategy is to nudge customers toward Azure by offering AHB exclusives (Windows Server BYOL only works in Azure, not AWS/GCP) while restricting certain rights in competing clouds. CIOs pursuing multi-cloud strategies should maintain SA for maximum flexibility, but also watch for policy changes. Microsoft has shown a pattern of evolving these benefits — the Flexible Virtualization Benefit (2022) expanded some rights, but future changes could restrict others. Work with licensing specialists to stay ahead of policy shifts.
5. 2026 Context: EA Changes, M365 Price Hikes & Copilot Costs
Software Assurance decisions don't exist in isolation — they're 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.
A 25,000-user enterprise on M365 E5 that previously enjoyed Level D volume pricing faces an estimated $3 million annual increase when factoring both the volume discount elimination and July 2026 price hikes. Adding Copilot at $30/user/month for even 5,000 users adds another $1.8 million annually. In this environment, every SA dollar must deliver measurable ROI. CIOs should negotiate aggressively and treat SA as a line item subject to the same scrutiny as any other license spend.
What This Means for SA Decisions
The EA pricing overhaul has several implications for SA strategy:
SA on On-Prem Is Unaffected (For Now)
The volume discount elimination applies to online services only. On-premises perpetual licenses with SA retain their existing pricing structure. This means SA for Windows Server, SQL Server, and other on-prem products isn't directly impacted — but CIOs should use this as leverage in negotiations.
SA as Azure Hedge Grows More Valuable
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.
MCA Transition Erodes SA Relevance
If Microsoft moves your organization from EA to MCA-E, the perpetual+SA model gives way to pure subscriptions. Plan your SA exit strategy alongside any MCA migration timeline.
Negotiate SA Concessions as Leverage
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.
6. Microsoft's Shift to Subscriptions & 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 Microsoft 365, 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.
The result: organizations that moved to M365 have found that SA for client software is no longer relevant. Under newer agreements (MCA, CSP), SA isn't even an option for cloud subscriptions. If 70% of your spend is on M365 and Azure, only the remaining on-prem server licenses may qualify for SA.
Azure & Server Subscriptions Bypass SA
On the server side, Azure IaaS/PaaS means you don't buy Windows Server or SQL Server licenses outright — it's 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-prem licensing through Azure's consumption model.
These subscription alternatives mean the classical SA program is increasingly bypassed. CIOs have more options than ever to license infrastructure without committing to perpetual licenses + SA.
The Shrinking SA Attach Rate
Many organizations find that fewer products even qualify for or require SA. 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. CIOs report that the "SA spend" portion of their 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 — not a permanent fixture.
Cost vs. Benefit: When SA Stops Making Sense
SA adds ~25% to license cost annually — over four years, that's equivalent to buying the license again. If during that period you haven't 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're migrating to SharePoint Online next year?
A practical test: for each SA-covered product, ask "What would happen if we dropped SA today?" If the answer is "nothing changes for 2+ years," that's a strong signal to retire SA on that product and redirect the spend. See our EA optimization service for product-by-product analysis.
7. Retain or Retire? Making the SA Decision in 2026
The ultimate question: where should you keep paying for SA, and where can you safely drop it? This section provides a structured decision framework.
When to Retain SA
✅ Core On-Prem Products You'll 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.
✅ Hybrid Cloud / Multi-Cloud Deployments
Keep SA for any licenses you'll 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.
✅ Virtualization & 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'd need to license all physical host cores.
✅ No Subscription Alternative Exists
Some products (specialized server tools, certain developer platforms) have no cloud/subscription equivalent. If the product is mission-critical and you need ongoing updates, SA remains your lifeline.
When to Let SA Lapse
❌ Cloud Migration Within 1–2 Years
If you have a concrete plan to decommission on-prem licenses for cloud services, continuing SA is wasted spend. Time the SA drop to align with migration completion.
❌ Stable Legacy Products — No Upgrade Planned
Systems running in steady state (e.g., manufacturing floor, dedicated appliances) that won't be upgraded for 5+ years. You can run the perpetual license indefinitely without SA.
❌ Already Migrated to Subscriptions
If you've moved from Office 2019 to M365, or from on-prem Exchange to Exchange Online, drop SA on the old perpetual licenses — you're paying double otherwise.
❌ SA Cost Outweighs Realized Benefits
If you've 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.
Decision Framework — Product-by-Product
For each SA-covered product, answer these four questions:
1. Will we upgrade this product within the SA term? → If no, lean toward retiring SA.
2. Will we use this license in Azure (AHB) or another cloud (Mobility)? → If yes, retain SA.
3. Does this product require SA for our virtualization/DR rights? → If yes, retain SA.
4. Is there a subscription alternative we're migrating to? → If yes, plan SA phase-out.
If all four answers point to "no value," retire SA on that product and redirect the spend. This is the framework our Microsoft optimization advisors use in every engagement.
Maximizing 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 your 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. In our assessments, we typically find 30–50% of eligible VMs don't have AHB activated — this represents direct, recoverable savings.
Time Upgrades to Your SA Window
If you renewed SA on Windows Server in 2025 through 2028, you're entitled to any release during that window. Encourage infrastructure teams to schedule upgrades (e.g., Windows Server 2025) before SA expires. Don't leave upgrade rights on the table — if SA lapses, you can still use versions released before then, but not after.
Leverage Step-Up Licenses and Workplace Discount
If you foresee needing a higher edition (SQL Standard → Enterprise, for example), use the Step-Up benefit to pay only the price difference rather than a full new license. Also promote the Workplace Discount Program to employees — discounted M365 Personal/Family subscriptions improve morale at zero incremental cost to the company.
8. CIO Recommendations
✅ SA 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 our four-question decision framework to retain or retire each product's SA.
- Adopt a selective SA strategy — not blanket coverage. Keep SA for products where it delivers measurable ROI (server upgrades, AHB, License Mobility, virtualization rights). Drop it everywhere else. It's acceptable and optimal to have mixed coverage.
- 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.
- Account for retired benefits in your budget. Training, planning services, and support incidents are gone. Budget separately for Unified Support, third-party training, and professional services that SA previously bundled.
- 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 won't use.
- 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.
- Watch the EA-to-MCA transition closely. If Microsoft moves your organization to MCA-E, understand how SA benefits translate (or don't) to the new model. Plan your SA exit strategy alongside any program migration.
- Monitor policy changes proactively. Microsoft regularly updates License Mobility, AHB, and FVB rules. Subscribe to licensing news or work with independent advisors to stay ahead of changes that could affect your rights.
- Avoid double-paying. If you've 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. 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.
Key Takeaway #1
SA's value is now concentrated in three areas: upgrade rights for on-prem perpetual licenses, Azure Hybrid Benefit for cloud savings, and License Mobility for multi-cloud flexibility. If none of these apply to a product, SA is overhead.
Key Takeaway #2
The retirement of training, planning, and support benefits means SA's total value proposition is 30–40% lower than it was in 2020. Recalculate ROI with current benefits, not historical ones.
Key Takeaway #3
With EA volume discounts eliminated and M365 prices rising in July 2026, every Microsoft dollar is under scrutiny. Selective SA optimization can free budget for cloud investments or Copilot pilots.
Key Takeaway #4
SA re-enrollment is possible at future renewals. Dropping SA now is not irreversible — you can add it back later (though you may only add SA to the current version). This reduces the risk of optimizing aggressively.
Microsoft Optimization Services
EA Optimization Service
Contract Negotiation Service
Audit Defense Service
Frequently Asked Questions
Optimize Your Microsoft Software Assurance Strategy
Our independent advisors assess your SA utilization product-by-product, identify wasted spend, and build a retain-or-retire roadmap that maximizes ROI.
Related Resources
Microsoft EA Renewal Case Studies
Proven strategies to slash spend and avoid Microsoft traps at renewal.
Case StudyMicrosoft Negotiation Case Studies
How global enterprises slashed costs and beat Microsoft's negotiation tactics.
ArticleMicrosoft Licensing Trends 2025–2026
What's changing and how to respond — EA discounts, MCA transition, AI add-ons.
ArticleEA Pricing: Level A Changes
All customers move to Level A pricing — impact analysis and strategies.
ArticleEA Renewals: CIO & Procurement Guide
Comprehensive guide to negotiating Microsoft Enterprise Agreement renewals.
ArticleSQL Server 2022 Licensing Guide
Strategic licensing guide for ITAM professionals — editions, models, SA requirements.
ArticleWindows Server & SQL Server Licensing
Practical guide covering licensing models, virtualization scenarios, and pitfalls.
ArticleMicrosoft Volume Licensing Guide
Complete guide to EA, MPSA, Open Value, CSP, and MCA licensing programs.
ArticleMicrosoft Licensing Models Explained
Perpetual vs. subscription, per-user vs. per-device, and capacity-based models.
ArticleMicrosoft 365 Enterprise Plan Guide
CIO playbook for selecting the right M365 E1/E3/E5/F-level plan.
ArticleMicrosoft Customer Agreement (MCA) Explained
Why Microsoft is pushing MCA and what it means for your licensing strategy.
Knowledge HubMicrosoft Licensing Knowledge Hub
Complete resource library for Microsoft licensing guidance and advisories.
Fredrik Filipsson
Fredrik Filipsson brings over 20 years of experience in enterprise software licensing, including direct roles at IBM, SAP, and Oracle. As co-founder of Redress Compliance, he has helped hundreds of Fortune 500 organizations optimize costs, avoid compliance risks, and secure favorable terms with major software vendors including Microsoft.