The SA Benefits Most Enterprises Never Claim
Software Assurance includes more than a dozen distinct benefit categories, yet the typical enterprise claims fewer than four of them in any given three-year EA term. The rest expire unutilised — paid for in full, delivered in zero. This guide maps every active SA benefit for 2026, explains activation requirements precisely, identifies common activation failures, and flags which benefits have changed or been deprecated since the prior EA cycle.
The starting point for any SA benefits programme is the Volume Licensing Service Centre (VLSC). SA benefits must be activated through VLSC by a designated SA administrator — they are not automatically provisioned. Failure to assign an SA administrator, or assigning one who is unaware of the benefit portfolio, is the primary reason enterprises pay for SA without extracting value. Visit the complete SA guide for the overall ROI framework.
Category 1: Deployment and Usage Rights
Deployment rights are the most commercially significant SA benefits and the ones most directly tied to infrastructure strategy.
Azure Hybrid Benefit (AHUB)
What it provides: The right to run SA-qualified Windows Server and SQL Server licences in Azure without paying the base VM rate that includes the OS or database licence. This dramatically reduces Azure compute costs for IaaS workloads. A Standard_D4s_v5 VM with SQL Server Enterprise standard pricing runs at approximately $3.20/hour in East US; with AHUB applied, the compute cost excluding the SQL licence is approximately $0.96/hour — a 70% reduction.
Activation: AHUB is activated at the Azure subscription or individual resource level through the Azure portal or Azure CLI. It does not require activation through VLSC — it is applied directly to Azure resources. This means AHUB can be activated at any time, not just at SA renewal. Enterprises that are not applying AHUB to eligible Azure resources are leaving their most valuable SA benefit completely unused. See our detailed SQL Server AHUB strategy guide.
Eligibility requirements: Active SA on Windows Server or SQL Server licences (by edition and core count corresponding to the Azure VMs). Licences under active SA only — licences where SA has lapsed are not eligible. Normalisation rules apply to SQL Server core editions in Azure (minimum 4 cores per VM).
Common failure pattern: Azure environment built before SA administrator communicates AHUB rights to the cloud infrastructure team. Azure VMs running with Pay-as-You-Go licensing despite on-premises SQL Server SA coverage. An audit of Azure resource licensing configuration against SA licence inventory typically reveals $50,000–$300,000 in unclaimed AHUB savings for a mid-to-large enterprise.
Licence Mobility Through Software Assurance
What it provides: The right to run SA-qualified server application licences (SQL Server, Exchange Server, SharePoint Server, System Center, and others) on shared server hardware — including third-party hosting environments and co-location facilities — without paying an additional licence. Without Licence Mobility, running a Microsoft server application on infrastructure shared with other tenants would require a separate licence. Full details at Licence Mobility Through Software Assurance.
Activation: Requires a formal agreement between the enterprise and the authorised outsourcer — the hosting provider must be a qualified "Authorised Outsourcer" under Microsoft's partner framework. The enterprise submits a Licence Verification Form to the outsourcer, and the arrangement must be documented. This multi-party process is where most activations fail: the internal licence administrator initiates the request but the outsourcer paperwork stalls.
Unlimited Virtualisation Rights (Windows Server Datacenter)
What it provides: Windows Server Datacenter Edition licences with active SA include the right to run unlimited virtual machines on the licensed physical host running the current or previous version of Windows Server. Without SA, Datacenter Edition licences cover virtualisation rights for the version at the time of purchase — renewing SA maintains access to unlimited VM rights on new versions as they release.
Activation: No formal activation required. Rights are implicit with active SA on Datacenter Edition licences and the licensed host. Document SA coverage in your licence inventory for audit defence purposes.
Disaster Recovery Rights
SA includes passive disaster recovery server rights for SQL Server, Exchange, and SharePoint. A passive failover server — one that is only activated in disaster recovery scenarios and does not serve active production workloads — does not require a separate licence where the primary server is SA-covered. Detailed mechanics at Disaster Recovery Rights Under Software Assurance.
Category 2: Version and Upgrade Rights
SA includes the right to deploy new major versions of covered Microsoft products released during the active SA term at no additional licence cost. In practical terms, this means that if Windows Server 2025 or SQL Server 2026 releases while your SA is active, you can deploy those versions without purchasing new licences.
The financial value of this benefit has declined relative to the 2000s and early 2010s for two reasons. First, Microsoft's release cadence for on-premises server products has slowed significantly — major Windows Server and SQL Server releases now occur every 3–5 years rather than every 2–3. Second, cloud migration reduces the relevance of on-premises version currency for many workloads. For organisations on active on-premises upgrade programmes, version rights retain meaningful value; for stable on-premises estates with no planned upgrades in the current EA term, this benefit is rarely activated.
Step-Up Rights: A related but distinct benefit — SA on a lower edition grants step-up rights to upgrade to a higher edition at the differential price rather than full replacement cost. SA step-up is available for M365 E3 → E5, SQL Server Standard → Enterprise, and other edition transitions. See EA step-up licensing for detailed mechanics.
Category 3: Training and Professional Development
Software Assurance Training Vouchers (SATVs)
What they provide: Vouchers redeemable against Microsoft Official Curriculum (MOC) instructor-led training courses delivered by Microsoft Learning Partners. SATVs can cover technical certifications, role-based training, and technology transition courses. SATV value is denominated in "training days" — a typical large enterprise receives 40–150 training days annually depending on SA coverage.
Activation and expiry: SATVs must be activated through VLSC and assigned to a designated SATV administrator. They expire annually on a rolling basis aligned with the EA anniversary — typically July 31 for standard anniversary dates. Unactivated or unused SATVs do not roll over and do not generate credits or refunds. Full guide at Software Assurance Training Vouchers.
Activation failure pattern: SATVs require the enterprise to (1) activate the benefit in VLSC, (2) identify eligible courses from the Microsoft Learning Partners catalogue, (3) coordinate with L&D or HR to register employees, and (4) complete the training within the eligibility window. Each step represents a failure point. Most organisations that miss SATV redemption do so because no single owner spans all four steps.
E-Learning Entitlements
SA includes access to Microsoft's online learning library through the SA e-learning benefit — self-paced courses covering Microsoft technology. This benefit has declined significantly in value with the proliferation of free Microsoft Learn content and paid-but-accessible platforms like LinkedIn Learning (which many M365 E5 licences now include). For most enterprises, this is a low-priority benefit to activate.
Category 4: Support and Planning Benefits
Planning Services Credits
What they provide: Credits for Microsoft Planning Services engagements — pre-packaged professional services deliverables delivered by Microsoft's services team or authorised partners. Services include cloud migration assessments (Desktop Deployment Planning Services, Azure migration planning), security assessments, and deployment planning workshops for specific Microsoft products.
Activation: Planning Services credits are activated through VLSC and must be assigned to a specific engagement. Engagements must be requested and scheduled — they do not automatically generate deliverables. The number of Planning Services days available depends on the SA coverage scope, typically ranging from 5 to 50 days for enterprise agreements.
Value assessment: For organisations in active technology transitions (cloud migration, major product upgrades), Planning Services engagements provide genuine value. Equivalent Microsoft consulting engagement rates run $2,000–$4,000 per day. For a 20-day planning services entitlement, this represents $40,000–$80,000 in consulting credit. For organisations not in active transitions, this benefit goes unclaimed in approximately 60% of EA terms.
24x7 Problem Resolution Support
SA includes access to Microsoft's problem resolution support line for critical and high-severity incidents. For enterprises with Premier or Unified Support contracts, this benefit is largely redundant — Premier/Unified Support provides broader coverage, dedicated technical account management, and faster response SLAs than SA-level support. The SA support benefit has real value primarily for smaller enterprises that would not otherwise have a support contract, but this segment rarely holds large EAs where SA costs are significant.
Complete SA Benefits Quick Reference
| Benefit | Activation Method | Expiry | 2026 Value |
|---|---|---|---|
| Azure Hybrid Benefit | Azure Portal / CLI | None (active while SA active) | High |
| Licence Mobility | Outsourcer agreement | None (while SA active) | High (for hosted workloads) |
| Unlimited VM (Datacenter) | Implicit | None | High (for virtualised hosts) |
| Disaster Recovery Rights | Implicit (document for audit) | None | Medium (traditional DR only) |
| New Version Rights | VLSC activation | SA term end | Medium (depends on upgrade plans) |
| Step-Up Rights | EA amendment | SA term end | Medium (edition transitions) |
| Planning Services | VLSC → Microsoft scheduling | Annual (varies) | Medium (active transition only) |
| SATVs | VLSC + L&D coordination | Annual (July 31) | Low (high activation friction) |
| E-Learning | VLSC | SA term end | Low (free alternatives available) |
| Home Use Programme | Employer portal | Annual | Low (M365 includes personal install) |
| 24x7 Support | Support contract activation | SA term end | Low (Unified Support overlap) |
Before your next EA renewal: (1) Pull the SA benefit utilisation report from VLSC for the current term. (2) Audit Azure resources for AHUB application against SA coverage — use the Azure Cost Management portal's licence optimisation recommendations. (3) Assign an SATV administrator and schedule any remaining training vouchers before the July 31 expiry. (4) Confirm Planning Services days have been scheduled if your organisation is in an active technology transition. (5) Document DR right usage against licenced server inventory. The result of this exercise gives you both the ROI evidence for SA renewal decisions and the negotiation data for SA scope adjustments.