Software Assurance has been a cornerstone of Microsoft's volume licensing for decades, providing upgrade rights, training, support, and cloud mobility. But as Microsoft shifts to subscription-first, SA's benefits have been dramatically reshaped. This playbook covers what is still active, what has been retired, where SA remains essential, hybrid cloud rights, and a decision framework for retaining or retiring SA in your enterprise.
Microsoft Software Assurance is a software maintenance and benefits programme 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 licence cost per year. SA spans Windows, Office, and server software, offering tools and services to help plan, deploy, and use products effectively.
In Microsoft's traditional Enterprise Agreement (500+ users), SA is automatically included with licence purchases. Under MPSA and earlier programmes (Select, Select Plus), customers could opt for SA. SA became synonymous with future-proofing. Organisations with SA did not worry about surprise costs for the next Windows or Office upgrade. It conferred exclusive rights including home-use programmes, enterprise editions, and licence mobility.
The flagship benefit. Rights to all new version releases of covered products during the SA term. Ensured organisations could always upgrade without new licence purchases. This alone justified SA for many enterprises running Windows Server and SQL Server estates on upgrade cycles shorter than four years.
SA historically included training days redeemable with Microsoft Certified Partners, e-learning courses, deployment planning service vouchers for consulting with Microsoft partners, and 24/7 problem resolution support incidents. These services reduced the burden on internal teams and supplemented in-house skills.
Home Use Programme allowing employees to install Office at home. Virtual Desktop Access (VDA) rights. Windows Enterprise editions. Microsoft Desktop Optimisation Pack (MDOP). These perks differentiated SA-covered licences from bare perpetual licences.
SA enabled reassigning server licences to third-party clouds. Cold-backup standby server rights for disaster recovery without additional licences. These cloud-era benefits became increasingly important as enterprises adopted hybrid infrastructure strategies.
Identify which current licences are under SA and what benefits you have been using. Map historical SA benefits to your IT needs. If you are in an EA, SA is likely included in costs. Dropping SA may mean changing your licensing programme entirely. Understanding your baseline is the essential first step before any optimisation.
Microsoft has made significant changes to SA benefits during 2020 to 2023, driven by the shift to cloud services. Many traditional benefits have been retired, replaced, or transformed. Understanding what remains is critical for calculating the true value of SA in your current agreements.
| SA Benefit | Status | Notes / Replacement |
|---|---|---|
| New Version Rights | Active | Still core: upgrade to new on-prem versions during SA term. Critical for perpetual licences. |
| Licence Mobility | Active | Move server app licences to authorised third-party cloud providers (AWS, GCP, hosting). Windows Server excluded. |
| Azure Hybrid Benefit | Active | Requires SA. Reuse on-prem licences in Azure at reduced cost (30-50% savings). Covers Windows Server and SQL Server. |
| Home Use (Workplace Discount) | Active | Rebranded. Employees purchase M365 subscriptions at discount for home use. |
| Disaster Recovery Rights | Active | Cold standby instance for DR without additional licence fee. |
| Step-Up Licences | Active | Upgrade editions (Standard to Enterprise) paying only the price difference. SA-only benefit. |
| Training Vouchers (SATV) | Retired Feb 2021 | Final redemption Jan 2022. Replaced by free Microsoft Learn online training. |
| E-Learning Courses | Retired | Replaced by Microsoft Learn platform. Free, no SA needed. |
| Planning Services (DPS) | Retired Feb 2021 | Replaced by FastTrack programme for cloud deployment assistance. |
| 24x7 Support Incidents | Retired Feb 2023 | Eliminated in favour of paid Unified Support contracts. SA no longer includes free support calls. |
| Windows Enterprise SA Rights | Transformed | Most enterprises now get Windows Enterprise via M365 subscriptions. SA on Windows Pro still grants similar rights but diminishing. |
| Enterprise Source Code Access | Active (niche) | Available for 10,000+ desktop SA customers. Rarely used. |
What remains is a leaner set of core SA benefits focused on licence rights rather than service perks. Upgrade rights remain the headline benefit. Licence Mobility and Azure Hybrid Benefit are the cloud-relevant benefits. Traditional perks like Home Use still exist but have evolved to align with subscription offerings.
SA benefits do not apply under newer purchasing models (MCA, CSP) for cloud subscriptions. Those programmes use subscription licensing which inherently includes some of these rights. SA now mostly applies to traditional volume licensing programmes (EA, MPSA, Open Value, perpetual licences).
Update internal policies referencing retired benefits (training vouchers, planning services, support calls). Allocate budget for costs SA previously covered, especially support (now requires paid Unified Support). Use the benefit status table as a checklist to evaluate which benefits you actually use. If you are paying for SA but not using any active benefits, you are wasting money.
SA is no longer universally needed in an era of cloud subscriptions. But there are specific scenarios where it remains essential or highly valuable. Identifying these scenarios within your own environment is the key to right-sizing your SA investment.
If you use on-prem perpetual licences (Windows Server, SQL Server, Exchange, SharePoint) and plan to upgrade to latest versions, SA is the most efficient path. Without SA, you must purchase entirely new licences. Any perpetual software you expect to upgrade every few years should be under SA. The cost of SA over a typical upgrade cycle is almost always less than purchasing new licences outright.
For hybrid or multi-cloud strategies, SA enables bring-your-own-licence (BYOL) to third-party clouds (AWS, GCP). Moving SQL Server to AWS using existing licences is only allowed with active SA. Without SA, many Microsoft products cannot legally run on third-party cloud infrastructure using your perpetual licences. If multi-cloud flexibility matters to your architecture, SA is non-negotiable.
Windows Server Datacenter with SA can cover up to two Azure VM instances. SQL Server licences with SA dramatically reduce Azure SQL costs. AHB is one of the strongest reasons to maintain SA on server products if you plan hybrid or Azure deployments. Dual-use is allowed during migration (up to 180 days). AHB turns SA into a tangible budget saver rather than just a promise for future upgrades.
SA waives the 90-day licence reassignment restriction for certain products, critical in virtualised environments using VMware vMotion or Hyper-V Live Migration. SA enables passive secondary server for failover (HA/DR) without additional licensing for products like SQL Server. These rights are often overlooked but can represent significant savings in enterprise data centre environments.
Microsoft sometimes offers Extended Security Updates (ESUs) only to customers with SA or subscription equivalents. SA can be a prerequisite for purchasing extended support patches when you cannot upgrade a legacy system by end-of-support date. This is a critical safety net for legacy environments where migration timelines extend beyond product support dates.
Organisations not fully migrated to M365 still need SA for Windows Enterprise features (BitLocker, AppLocker) and perpetual Office upgrade rights. If you are in a regulated or offline environment using perpetual Office, SA is the only way to stay current with new releases. This applies to a decreasing number of organisations but remains critical where it does apply.
Audit your IT portfolio to identify which systems depend on SA. Calculate Azure Hybrid Benefit savings versus cost of SA. Calculate licence cost avoidance of upgrading via SA versus buying new licences. Use SA as a bridge: maintain it until cloud migration is complete, then reassess at the next renewal. Data-driven analysis prevents both overspending and under-protection.
Get an independent audit of which SA benefits you are using, which are wasted, and where Azure Hybrid Benefit can offset your SA costs. Redress Compliance provides vendor-independent SA assessment as part of our Microsoft optimisation advisory.
Microsoft Optimisation Services →One of the most significant aspects of SA in recent years is its role in enabling hybrid cloud scenarios. Two key mechanisms, Licence Mobility and Azure Hybrid Benefit, both require SA but apply in different contexts. Understanding the distinction is essential for any enterprise running workloads across on-premises, Azure, and third-party clouds.
| Feature | Licence Mobility | Azure Hybrid Benefit (AHB) |
|---|---|---|
| Scope | Third-party clouds (AWS, GCP, hosting partners) | Microsoft Azure only |
| Requires SA? | Yes. Active SA required at migration. | Yes. SA or equivalent subscription licences. |
| Products Covered | Application servers: SQL, Exchange, SharePoint, Dynamics. Not Windows Server. | Windows Server and SQL Server. Also Azure VMware Solution, Azure Stack. |
| Key Benefit | BYOL to any Authorised Mobility Partner infrastructure | 30-50% Azure VM/SQL cost savings by reusing on-prem licences |
| Windows Server | Not covered | Covered (Datacenter with SA equals 2 Azure VMs) |
| Dual-Use Period | Not formally offered | Up to 180 days concurrent on-prem plus Azure during migration |
Licence Mobility lets you deploy server applications (SQL, Exchange, SharePoint, Dynamics) on cloud VMs at AWS, GCP, or hosting partners using existing licences without buying new licences through that cloud provider. The provider must be a Microsoft Authorised Mobility Partner. In 2022, Microsoft introduced the Flexible Virtualisation Benefit (FVB), expanding this by allowing any cloud provider infrastructure with fewer restrictions except a short list of major providers. FVB reinforces that having SA is key to unlocking flexible cloud use.
AHB allows customers to reuse Windows Server and SQL Server licences in Azure at dramatically reduced rates. You only pay base compute, not the licence portion. A Windows Server Datacenter licence with SA covers up to two Azure VM instances. SQL Server Enterprise licences with SA can be applied to Azure SQL Database or Managed Instance at a fraction of normal cost. AHB can be activated directly in the Azure portal. It turns SA into a tangible budget saver rather than just a promise for future upgrades.
Apply Azure Hybrid Benefit to every eligible VM. It is a quick path to cost savings that many organisations overlook. For multi-cloud, maintain SA on critical workload licences to hedge against changes. Ensure cloud architects and SAM teams collaborate: cloud teams should know what SA entitles them to do.
If maintaining SA costs X but AHB saves 2X in Azure, SA pays for itself. This calculation should be performed licence by licence for your server estate. Some licences will show clear positive ROI from AHB alone. Others will not. The arithmetic determines your retain-or-retire decision for each product.
Microsoft has been aggressively pushing subscription-based licensing: M365, Dynamics 365, Azure consumption. This shift profoundly impacts SA's relevance, as subscriptions inherently include benefits SA used to provide. Understanding this trajectory is essential for making informed SA decisions.
With Office 365 and Microsoft 365, upgrade rights are built in. Always the latest version. Home use is covered by the O365 licence. Windows Enterprise is included in M365 E3/E5 as a user-based subscription. No separate SA needed. Result: SA for client software is irrelevant for M365 organisations. If you have moved to M365, you are already paying for what SA used to provide on the desktop side.
Azure IaaS/PaaS includes licence costs in service pricing (unless using AHB). Microsoft now offers server subscriptions for on-prem use via CSP. These function like SA but are not called SA. These subscription licences are replacing the classical SA programme for server products. The trend is clear: Microsoft is building SA-equivalent rights into subscription models.
Microsoft is transitioning EA customers to the Microsoft Customer Agreement (MCA). Under MCA/CSP, SA benefits do not apply the same way. The licensing construct is fundamentally different. Microsoft is de-emphasising perpetual licensing. The classic SA programme is less central than a decade ago. Plan accordingly.
If 70% of spend is M365 E5 and Azure, those do not use SA. Perhaps only on-prem Windows Server and SQL Server (remaining 30%) are under SA, and even those may be candidates for cloud migration. Microsoft has reduced SA incentives (retiring training, planning, support) as they anticipate lower need across their customer base.
SA adds approximately 25% annually. Over four years, that is equivalent to buying the licence again. If you have not used upgrades, support, or cloud mobility in that time, the money is wasted. Why pay SA on SharePoint Server if you intend to migrate to SharePoint Online next year? The subscription shift makes such scenarios common across enterprise estates.
SA is less central in a cloud-first world, but still matters for legacy and hybrid scenarios. Over the next 3 to 5 years, Microsoft will likely continue making SA less visible, possibly incorporating benefits into other offerings. Plan your long-term strategy with the assumption that SA may not be as readily available in the future. Maintain it where the ROI is clear. Drop it where subscriptions have replaced the need.
Evaluate moving to M365 and cloud services where feasible. These simplify licensing and often remove SA need. Identify SA orphans: products where SA is the only reason you maintain the programme. Use dropping SA as a bargaining chip for M365 discounts during EA renewal. Ensure finance understands the CapEx-plus-SA to OpEx subscription shift and its implications for budgeting and forecasting.
Get expert guidance on where to keep and where to drop Software Assurance. Redress Compliance provides independent advisory with current benchmark data, SA value assessments, and negotiation expertise to maximise every dollar of your Microsoft investment.
Microsoft EA Optimisation Service →The ultimate question: where should you keep paying for SA, and where can you safely drop it? This section provides a decision framework based on the scenarios that justify SA retention and the scenarios that signal it is time to let SA lapse.
Keep SA for Windows Server, SQL Server, or other server software you know will be upgraded. SA cost (approximately 25% per year) is usually less than purchasing new licences every few years. If you intend to stay current with on-premises versions, SA is worth it. The break-even point is typically around 4 years: if you upgrade within that window, SA pays for itself.
Retain SA on any licences you plan to use in Azure (for AHB savings) or third-party clouds (for Licence Mobility). For any workload mobility scenario, SA is a must. Dropping it locks workloads to your data centre or forces higher costs by requiring you to purchase licence-included cloud pricing.
Disaster recovery rights, Step-Up licences, Workplace Discount, virtualisation flexibility. While these alone may not justify cost, they add to value if you are already leaning towards keeping SA. Tally up every benefit you actually exercise, not just the benefits Microsoft lists in the programme guide.
Some products may only be available as perpetual licences. If mission-critical with no cloud equivalent (data residency, compliance requirements, air-gapped environments), SA is your lifeline for staying current. This applies to a shrinking but still significant number of enterprise workloads.
If you have concrete plans to decommission on-prem licences, continuing SA is wasted money. Coordinate SA decisions with project timelines. Keep SA until migration cut-over is complete, then drop. Do not pay SA for 3 years on software you will retire in 18 months.
Systems in steady state that will not be upgraded for 5+ years. Let SA lapse and run with your perpetual licence. This saves costs but accept the trade-off: if you suddenly need an upgrade, you will purchase new licences at that point. For truly stable environments, this is often the right call.
If you have not used upgrades, cloud mobility, or support in four years, SA spend is effectively wasted. Over four years, SA costs approximately equal another full licence. Cut losses and do not renew on those products. Redirect the budget to areas where SA delivers measurable value.
If you transitioned to M365 Apps, Windows E5 per-user, or Azure services, do not keep SA on the replaced perpetual licences. Avoid double-paying. The subscription already includes the rights SA used to provide. The only exception is a brief overlap period during migration cut-over.
Plan upgrades to align with SA term. If SA runs through 2028, schedule Windows Server and SQL Server upgrades before expiry. Do not leave upgrade rights unused. Unused upgrade rights are the most common form of SA waste in enterprise environments.
Actively apply Azure Hybrid Benefit to every eligible VM. Consider reassigning spare SA licences from on-prem to cloud BYOL scenarios. This is a direct way to recoup SA cost. If you are paying for SA, extract every possible cloud benefit from it.
Need SQL Enterprise but own SQL Standard with SA? Use Step-Up to pay only the difference. This represents significant savings versus buying new full licences. Step-Up is an SA-only benefit that many organisations overlook during procurement planning.
Tell employees about the home-use discount programme. Zero extra cost to the company. Improves goodwill and Microsoft technology adoption. While not a major financial benefit for IT, it is a zero-cost employee perk that justifies a small portion of your SA investment.
Keep SA for what you need. Drop it for what you do not. It is not all-or-nothing. You might keep SA on server products but drop desktop products. Or keep SQL but drop BizTalk if phasing out. Microsoft allows product-level SA choices at renewal. Tie every SA decision to your IT roadmap, not to historical habit.
Software Assurance is a software maintenance and benefits programme available through Microsoft's volume licensing. It bundles upgrade rights, cloud mobility, and additional perks for a fixed annual fee, typically around 25% of the licence cost per year. In an Enterprise Agreement, SA is automatically included. In other programmes (MPSA, Open Value), it is optional. SA covers Windows, Office, and server software (Windows Server, SQL Server, Exchange, SharePoint, and others).
Four major benefits were retired during 2021 to 2023. Training Vouchers were retired in February 2021 and replaced by free Microsoft Learn. E-Learning Courses were retired and replaced by Microsoft Learn. Deployment Planning Services were retired in February 2021 and replaced by FastTrack. 24x7 Support Incidents were retired in February 2023 and replaced by paid Unified Support contracts. What remains: New Version Rights (upgrades), Licence Mobility, Azure Hybrid Benefit, Home Use (Workplace Discount), Disaster Recovery rights, and Step-Up licences.
Azure Hybrid Benefit (AHB) lets you reuse on-premises Windows Server and SQL Server licences in Azure at reduced rates. You pay only the base compute cost, not the licence portion. Requires active SA. A Windows Server Datacenter licence with SA covers up to 2 Azure VMs. Savings estimates range 30 to 50% on eligible Azure VM workloads. AHB can be activated directly in the Azure portal. It is one of the strongest reasons to maintain SA on server products if you use Azure.
Licence Mobility covers third-party clouds (AWS, GCP, hosting partners). It lets you deploy server applications (SQL, Exchange, SharePoint) using existing SA-covered licences, but excludes Windows Server. Azure Hybrid Benefit is Azure-only but covers Windows Server and SQL Server, with 30 to 50% cost savings. They are complementary: one for non-Azure clouds, one for Azure. Both require active SA. The 2022 Flexible Virtualisation Benefit expanded Licence Mobility to more providers.
For client software (Office, Windows desktop), generally no. M365 subscriptions include upgrade rights, enterprise features, home use, and always-current versions. SA for client software is irrelevant if you are on M365. However, you may still need SA for server products (Windows Server, SQL Server) if you have on-premises infrastructure. M365 does not cover server licensing. The decision is product-specific: drop SA on anything replaced by subscription, keep it on remaining on-prem server workloads.
In most cases, no. Microsoft's Licence Mobility rules require active SA to deploy covered server applications on third-party cloud infrastructure. Without SA, you would typically need to use the cloud provider's licence-included rates (often more expensive) or dedicated tenancy arrangements. Some exceptions exist for products with specific BYOL terms, but the general rule is: SA is required for BYOL to multi-tenant cloud environments. If multi-cloud flexibility is important, maintain SA on those licences.
Drop SA when: you are migrating the workload to cloud/SaaS within 1 to 2 years; the product is in stable state with no planned upgrades for 5+ years; you have not used upgrades or cloud mobility in the current term (wasted spend); or you have switched to subscription licensing for that product (avoid double-paying). Keep SA when: you plan to upgrade (Windows Server, SQL Server); you need Azure Hybrid Benefit or Licence Mobility; you rely on DR rights or Step-Up licences. It is not all-or-nothing. Be selective by product.
For large enterprises with significant Microsoft estates, independent advisors deliver substantial ROI. They bring benchmark data from hundreds of EA renewals, identify where SA is overspent or under-utilised, calculate Azure Hybrid Benefit opportunities, and navigate the complex retain-or-retire decision across hundreds of licences. The key is engaging 6 to 12 months before renewal. The advisory fee is typically a fraction of the savings achieved. Choose an advisor who is genuinely independent and has no commercial relationship with Microsoft.
Approaching an EA renewal, evaluating SA coverage, or planning a cloud migration? Redress Compliance provides independent advisory with current benchmark data, SA value assessments, and negotiation expertise to maximise every dollar of your Microsoft investment.