Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Review

Software Assurance: What It Actually Buys and When to Skip It

12 min read Updated October 5, 2026 Microsoft Licensing Guides

Fix it now

Software Assurance is bought with a Volume Licensing agreement rather than bolted on later, and for some on-premises products it is now the only way to run them at all. Attach it when you will use one of its load-bearing rights during the term – new version rights, licence mobility, failover instances or step-up licences – and decline it when you will not.

  1. Attach it if a SQL Server design has any passive replica. Microsoft’s guidance is blunt: licences without SA, and non-subscription licences, do not include disaster recovery or high availability rights, failover clusters included.
  2. Attach it if anything is heading to Azure. Azure Hybrid Benefit needs on-premises core licences with active Software Assurance or qualifying subscription licences, and there is no other route to it.
  3. You have no choice on Exchange Server SE or SharePoint Server Subscription Edition. Both need active SA or a qualifying subscription to install and stay current, and SharePoint SE must be uninstalled if the coverage lapses.
  4. Skip it on a server with a fixed role, fixed hardware, no replica and no cloud plan. You would be buying version rights and mobility you will not exercise.
  5. Check the buying route first. SA comes only through Volume Licensing, at purchase or renewal, and is not available at all to Microsoft Customer Agreement or Microsoft Cloud Agreement customers.
  6. Do not buy it for free Azure Extended Security Updates. Those need no SA; Software Assurance is what Azure Hybrid Benefit requires, which is a different benefit.

The only attach window Microsoft publishes a number for is Windows Server OEM: those licences move onto Commercial Licensing terms only if Software Assurance is acquired within 90 days of purchase. Everywhere else the agreement’s own wording is the deadline.

If one of those rights is already in your design, the decision is made and you can stop here. Below is what each right grants, what Microsoft has retired, and the two products where coverage stopped being optional.

Why it happens

Software Assurance is not a support contract and it is not an insurance policy. It is a named set of rights that attach to licences bought under a Volume Licensing agreement, and the Product Terms list them individually. The four that move real money are new version rights, licence mobility, failover rights and step-up licences. Everything else people associate with it – training, planning help, discounted home use – is either retired or peripheral.

New version rights are the simplest: Microsoft’s wording is that the customer may upgrade to the latest version of an available product. Over a three-year term that spans a major release, that right can be worth most of the licence. Over a term where nothing ships, or where you would not deploy it anyway, it is worth nothing. That is the whole calculation, and it is one you can do in your head.

Licence mobility is the right that lets eligible server workloads run somewhere other than hardware you control, either across your own server farms or on a shared third-party host. Failover rights are what allow passive instances to sit ready without a full licence each. Step-up licences let you move to a higher edition without buying it outright. Those three are structural: if the design needs one, no amount of arithmetic changes the answer.

SQL Server with any standby instance

You have this one if An availability group, a log-shipped secondary, a warm standby in another site, or a DR copy in Azure.

  1. Read Microsoft’s own line first: licences without SA and non-subscription licences do not include disaster recovery or high availability rights, including use of failover clusters.
  2. With active SA or a subscription licence, the published entitlement is three passive replicas per licensed operating system environment – one for high availability in a separate OSE, one for disaster recovery in a separate OSE, and one for disaster recovery in a single virtual machine or instance on Azure.
  3. Price the alternative honestly: without coverage, every passive replica is a licence you buy in full, and one replica usually costs more than coverage on the primary.

Anything with an Azure destination

You have this one if A migration plan, a DR site in Azure, or a burst capacity conversation that keeps coming back.

  1. Azure Hybrid Benefit for Windows Server requires on-premises core licences from an applicable programme with active Software Assurance or qualifying subscription licences. There is no other qualifying route.
  2. Size it before you commit: a minimum of eight core licences per virtual machine, more for instances larger than eight cores, and one processor licence counts as sixteen core licences.
  3. Do not conflate this with free Extended Security Updates in Azure. Microsoft states plainly that Software Assurance is not required for free ESUs in Azure, but is required for Azure Hybrid Benefit.

The product is no longer sold without it

You have this one if On-premises Exchange or SharePoint on a current release.

  1. Exchange Server SE requires an active qualifying entitlement – active SA on existing Exchange Server Standard or Enterprise licences, or a qualifying Microsoft 365 subscription – to install, run and stay current.
  2. SharePoint Server Subscription Edition requires active SA on both the server licences and the CALs, or a subscription licence. If it lapses you must uninstall the Subscription Edition software and may only install and use SharePoint Server 2019.
  3. Treat this as a running cost of the platform rather than an optional extra, and budget the renewal at the same time as the initial purchase.

One server, one job, one lifetime

You have this one if A file server, a domain controller or a line-of-business host that will run the version you bought until the hardware is replaced.

  1. Skip the coverage. There is no replica to license, no cloud destination and no upgrade you intend to take.
  2. Be honest about the second half of that, though: if an application vendor controls your support matrix, they may force a version move you did not plan.
  3. Revisit the decision at hardware refresh rather than mid-term. Coverage is attached at the agreement, so mid-life regret has nowhere to go.

Full reference

What the Product Terms actually list

Benefit Status What it gives you
New version rights Current Upgrade to the latest version of an available product for the term of the coverage
Licence mobility across server farms Current Move eligible server licences between your own farms under the published conditions
Licence Mobility through Software Assurance Current Deploy eligible server workloads on authorised shared third-party hosting
Failover rights Current Run passive fail-over instances for SQL Server under licence mobility rights
Step-up licences Current Move to a higher edition without buying the higher edition outright
Workplace Discount Program Current The renamed successor to the Home Use Program
Training vouchers Retired 1 February 2021 Nothing. Do not price it in
Planning services Retired 1 February 2021 Nothing. Do not price it in

Software Assurance Benefits are not available to Microsoft Customer Agreement or Microsoft Cloud Agreement customers. If that is how you buy, the conversation is about subscription licences instead, not about attaching coverage.

Where the choice has already been made for you

Two on-premises products moved from optional coverage to mandatory entitlement, and they are the ones most likely to be sitting in a small estate. Exchange Server Subscription Edition needs an active qualifying entitlement to install, run and stay current: active Software Assurance on existing Exchange Server Standard or Enterprise licences, or a qualifying Microsoft 365 subscription. SharePoint Server Subscription Edition is stricter still – the coverage has to be active on server licences and CALs, and if it lapses Microsoft’s stated position is that you uninstall the Subscription Edition software and may only install and use SharePoint Server 2019.

That is a genuine change in kind. A perpetual licence that stops working as a licence when the coverage stops is not a perpetual licence in the way anybody used the word. If either product is in your estate, the renewal is not a discretionary line and should not be treated as one during a budget squeeze.

The Azure benefit, and the one people confuse it with

Azure Hybrid Benefit lets you carry Windows Server licences into Azure and pay a reduced compute rate, and it needs on-premises core licences from an applicable programme with active Software Assurance or qualifying subscription licences. The sizing is published: a minimum of eight core licences per virtual machine, so eight are still needed for a four-core instance, more for larger instances, and a processor licence counts as sixteen core licences.

Free Extended Security Updates in Azure are a separate thing and do not need Software Assurance. Microsoft’s lifecycle FAQ states it directly: for ESUs in Azure, Software Assurance is not required for free ESUs, but Software Assurance is required for Azure Hybrid Benefit. Buying coverage to obtain free Azure ESUs is buying something you already have.

Deciding without a price list

You can settle this on your own quote in four lines. Take the coverage figure for the term. Against it, put the cost of the things you would otherwise buy: the next version, if a release lands during the term and you would deploy it; a full licence for every passive replica in the design; and the higher edition at full price if a step-up is likely. If the second column is larger, attach the coverage. If it is empty, do not.

The trap in that sum is the passive replica, because it is easy to leave out of a design document and impossible to leave out of a licence count. A SQL Server availability group with one secondary is not one licence and a spare; without coverage it is two full licences. Count the replicas before you price the coverage.

How SA reaches you at all

Software Assurance is only available through Volume Licensing, and it is purchased when you buy or renew an agreement. It is included with Enterprise Agreement and Enterprise Subscription Agreement, with Enrollment for Education Solutions, and with Open Value and Open Value Subscription. It is an optional purchase under the Microsoft Products and Services Agreement. That is the practical answer to ‘can I add it later’: the question is really ‘when does my agreement next renew’.

The one documented after-the-fact window is narrow and specific. Windows Server OEM licences move onto Commercial Licensing terms only where Software Assurance is acquired within 90 days of purchase. Do not generalise that 90 days to other products or channels – Microsoft does not publish a universal grace period, so read the wording on the agreement in front of you rather than working from a number somebody remembers.

When a licence is the actual fix

The honest version of this recommendation is that Software Assurance is worth attaching when a specific right in your design needs it, and worth declining when none does. Arco will quote the same licences with and without coverage so the difference sits on one page, and will say which of the four rights – new version, mobility, failover or step-up – your design actually exercises. Where the answer is none of them, we will quote without it. Where the product is Exchange Server SE or SharePoint Server Subscription Edition, there is no version of the quote without it, and we will explain why before you see the number.

Questions people ask about this

Can I add Software Assurance to licences I bought last year?

Generally not on their own. Software Assurance is only available through Volume Licensing and is purchased when you buy or renew an agreement, so the realistic answer is at your next renewal. The one published exception with a number attached is Windows Server OEM, which moves onto Commercial Licensing terms only if Software Assurance is acquired within 90 days of purchase.

Does Software Assurance include technical support?

Support appears in the Product Terms benefit list, but it varies by programme and it is not the reason to buy. Two of the benefits people still ask for – training vouchers and planning services – were retired from Software Assurance on 1 February 2021. Buy coverage for version rights, licence mobility, failover rights and step-up licences, and price support separately.

Do I need Software Assurance to get free Extended Security Updates in Azure?

No, and this is the most expensive misunderstanding in the area. Microsoft’s lifecycle FAQ states that Software Assurance is not required for free ESUs in Azure. Software Assurance is required for Azure Hybrid Benefit, which is a different benefit that reduces the compute rate on the virtual machine. Do not attach coverage in order to obtain something Azure already gives you.

What exactly do failover rights give me on SQL Server?

With active Software Assurance or a subscription licence, three passive replicas per licensed operating system environment: one for high availability in a separate OSE, one for disaster recovery in a separate OSE, and one for disaster recovery in a single virtual machine or instance on Azure. Without coverage, Microsoft’s guidance is that the licences do not include disaster recovery or high availability rights at all, failover clusters included.

Is there a cheaper route to the same rights?

Subscription licensing carries the equivalent entitlements for as long as you pay and needs no perpetual purchase, which suits organisations that would rather treat this as an operating cost. For Exchange Server SE it is one of the two accepted routes outright. It is not automatically cheaper over a long life, so run the comparison on your own quote rather than assuming either direction.

We buy under a Microsoft Customer Agreement. Does any of this apply?

Not directly. The Product Terms state that Software Assurance Benefits are not available to Microsoft Customer Agreement or Microsoft Cloud Agreement customers. If that is your buying route, the equivalent conversation is about subscription licences, and about which of your workloads still needs an on-premises entitlement at all.

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Review SQL Server Standard vs Enterprise: The Features That Force the Upgrade Review E3 Plus Add-Ons or Straight to E5? Building the Cheaper Security Stack Review Planner and Project Plans 1, 3 and 5: Which Licence Matches How You Run Projects Review Visio and Project: Perpetual Licence or Subscription Plan in 2026?
โ† Back to Knowledge Base