What Software Assurance Is — and What It Is Not
Software Assurance is Microsoft's premium maintenance programme, available only at the time of perpetual licence purchase and only through Volume Licensing channels. It cannot be added retrospectively. Once an SA subscription lapses, it cannot be reinstated without purchasing new licences — a point that catches many organisations off guard when they decide to cancel EA subscriptions without assessing the downstream impact on their licence rights.
SA is not simply a support contract. It bundles a range of technical rights, deployment flexibilities, and cloud entitlements that have genuine commercial value — but only if your organisation actively uses them. The most common failure mode is paying for SA across a large SQL Server estate while using only a fraction of its benefits, making the 25% annual cost difficult to justify.
For SQL Server specifically, there are five SA benefits that deliver meaningful value: version upgrade rights, passive HADR instance entitlements, License Mobility for cloud and third-party hosters, Azure Hybrid Benefit, and Extended Security Update eligibility. Understanding each — and whether it applies to your deployment scenario — is the foundation of a rational SA decision.
The Five Benefits That Matter for SQL Server
1. Version Upgrade Rights
SA grants the right to upgrade to any new SQL Server version released during the coverage period without additional licence purchase. For organisations that are actively keeping pace with SQL Server releases — moving from 2019 to 2022, for example — this benefit alone can justify a significant portion of the SA cost. A SQL Server Enterprise core licence costs approximately $14,256 per core. The right to upgrade to the next major version, which would otherwise require repurchasing that licence, represents a meaningful proportion of the SA premium over a standard 3-year SA term.
However, for organisations running stable SQL Server deployments with no planned version migration in the coverage period, upgrade rights deliver zero value. If you are running SQL Server 2019 and have no roadmap to upgrade to 2022 in the next three years, the upgrade right is not a financial benefit — it is a theoretical option you are paying for.
2. Passive HADR Instance Rights
This is one of the most financially significant SA benefits for SQL Server, and one of the most frequently misunderstood. Without SA, every SQL Server instance — including passive failover replicas and disaster recovery targets — must be separately licensed. With SA on Enterprise edition, you receive the right to run passive failover instances on a ratio of up to one warm standby for high availability plus two passive instances for disaster recovery, without additional licence purchase. This right applies retrospectively to SQL Server 2012 and later.
The financial impact depends entirely on your HA/DR architecture. An organisation running SQL Server Enterprise on 16 cores with an active-passive Always On configuration would need to licence the passive node separately without SA — at $14,256 per core, a 16-core passive node represents $228,096 in additional licence cost. With SA, that passive node is included. Over a 3-year SA term, the SA premium for a 16-core Enterprise licence is approximately $17,107 per year — the HADR benefit alone covers this many times over in the first year for a single active-passive pair.
3. License Mobility Through Software Assurance
SA enables two mobility rights that are otherwise unavailable. First, it removes the 90-day reassignment restriction — without SA, a SQL Server licence is tied to a specific physical host and can only be moved to a different host every 90 days. With SA, licences can be moved at any time. For organisations running virtualised SQL Server in dynamic environments — VMware, Hyper-V, or Nutanix clusters where workloads move frequently — this right is critical for maintaining compliance when VMs migrate across hosts.
Second, SA enables License Mobility to Authorised Mobility Partners, which includes most cloud service providers. This allows you to deploy your on-premises SQL Server licences in a hosted or cloud environment (including Azure, AWS, and Google Cloud) through the Bring Your Own Licence mechanism. Without SA, SQL Server can only be deployed in Azure using Microsoft's own marketplace images, which include licence costs and are typically significantly more expensive than BYOL pricing.
4. Azure Hybrid Benefit
Azure Hybrid Benefit (AHB) is available exclusively to organisations with active SA or SQL Server subscriptions. It allows on-premises SQL Server licences to be applied to Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VMs, eliminating the Azure SQL licence surcharge. The savings are substantial: AHB typically reduces Azure SQL costs by 30% or more compared to the standard pay-as-you-go rate that includes licence cost.
For organisations with cloud migration roadmaps or hybrid SQL Server deployments, AHB is one of the strongest financial arguments for maintaining SA. The 180-day dual-use right — which allows the same licence to run simultaneously on-premises and in Azure during the migration period — further enhances the value of AHB for organisations in active migration phases.
A practical point worth noting: Microsoft retired BYOL images from the Azure Marketplace. To use AHB for SQL Server on Azure VMs, you deploy standard marketplace images and enable AHB during or after deployment, rather than through a dedicated BYOL image. License Mobility verification must be reported to Microsoft within 10 days of deploying under this arrangement.
5. Extended Security Update Eligibility
For organisations running SQL Server versions approaching or past end of extended support, SA is a prerequisite for accessing Extended Security Updates (ESUs). ESUs provide security patches for up to three years beyond end of extended support, purchased in annual increments. Without active SA, ESUs cannot be purchased through volume licensing channels — though ESUs remain available through Azure Arc for workloads connected to Azure, on a pay-as-you-go subscription basis.
The ESU benefit is most relevant for organisations running SQL Server 2012 (end of extended support July 2022) or SQL Server 2014 (end of extended support July 2024). For these deployments, SA-eligible ESUs may be substantially cheaper than the migration investment required to move to a supported version within the support timeline.
SA Benefits by Deployment Scenario
| Deployment Scenario | Key SA Benefits | SA Value Assessment |
|---|---|---|
| Virtualised SQL Enterprise with HA/DR | HADR instances, VM mobility | Very high — HADR saves licence cost |
| Active Azure migration | AHB, 180-day dual-use right | High — AHB delivers 30%+ Azure saving |
| Static on-premises, single instance | Upgrade rights (if planned) | Low — unless version upgrade imminent |
| End-of-support version | ESU eligibility | Medium — depends on ESU vs migration cost |
| Cloud-hosted (BYOL) | License Mobility, AHB | High — required for BYOL in hosted environments |
The Decision Framework: Keep or Let SA Lapse?
The keep-vs-lapse decision should be made on a deployment-by-deployment basis rather than as a blanket policy across your entire SQL Server estate. Many organisations maintain SA on all SQL Server licences as a default, when in fact a significant portion of their estate — particularly Standard edition single-instance deployments with no cloud or HA footprint — would be adequately served by perpetual licences without SA.
The financial test is straightforward. Calculate the SA premium for the licences in question (25% of licence value per year). Then quantify the value of the SA benefits you will actually use during the coverage period: the licence cost of passive HADR nodes that SA covers, the Azure cost reduction from AHB, the licence cost of version upgrades you would otherwise purchase, and the ESU cost avoided. If the sum of benefit values exceeds the SA premium, SA is worth maintaining. If not, lapsing is the financially rational decision — accepting that you will lose those benefit entitlements.
Once Software Assurance lapses, it cannot be reinstated on existing perpetual licences. You would need to purchase entirely new licences with SA to regain coverage. Before allowing SA to lapse — particularly at EA renewal — ensure you have assessed the full downstream impact on your HADR, cloud, and mobility entitlements. We have seen organisations make this decision without proper analysis and face compliance issues and unexpected costs within 12 months.
Common Mistakes Enterprises Make With SQL Server SA
The most damaging mistake is cancelling Enterprise Agreements without assessing the impact on virtualised SQL Server estates. An organisation that has been running 30 physical servers each with 16 cores of SQL Server Enterprise, all in VMware clusters, relies on SA for two things: the 90-day reassignment exemption (so VMs can migrate freely between hosts) and HADR passive instance rights. Cancelling the EA and converting to perpetual-without-SA licences renders the entire virtualised estate non-compliant for licence mobility and requires separately licencing every passive failover node.
The second common mistake is failing to activate Azure Hybrid Benefit on Azure SQL deployments. Many organisations with active SA are paying Microsoft twice for SQL Server licences — once for the on-premises SA coverage and once implicitly through Azure's per-minute SQL licence charge. Enabling AHB on Azure SQL resources is a configuration change that takes minutes and can reduce monthly Azure SQL costs by 30% or more. We encounter this mistake regularly during licence reviews, particularly in organisations that have migrated SQL Server workloads to Azure but were not advised by their CSP or reseller to activate AHB at the time of migration.
Finally, the SQL Server 2022 mandatory SA requirement for Standard Edition on VMs per-core licensing catches organisations off guard. Standard Edition virtual machine deployments licensed on a per-core basis now require active SA — a requirement that did not apply to earlier SQL Server versions. Organisations upgrading to SQL Server 2022 in virtualised environments without budgeting for this requirement face an unexpected SA cost that can be substantial at scale.
Need an independent review of your SQL Server SA position?
Redress Compliance helps enterprises optimise SQL Server licensing costs and SA decisions across complex hybrid environments.Connecting SA to Your Broader Microsoft Strategy
SQL Server SA decisions do not exist in isolation. They are part of your broader Microsoft EA structure, and the SA coverage you maintain on SQL Server has implications for your Azure migration economics, your Microsoft 365 licensing, and your overall EA true-up exposure. Organisations approaching an EA renewal should review SQL Server SA as one component of a comprehensive Microsoft licensing analysis — not as a standalone decision. For broader guidance on software licence management strategy, see our Software Licence Management CoE Guide and our overview of SAM tools for 2026.