How to Calculate the ROI of Microsoft Software Assurance

Why Most SA ROI Analyses Are Wrong

Most enterprises that attempt a Software Assurance ROI analysis make the same mistake: they calculate the value of benefits they could use rather than benefits they will actually use. The resulting analysis invariably concludes SA is worth it, because the theoretical benefit list is broad enough to justify almost any cost if you assume full utilisation. In practice, SA benefit utilisation for a typical enterprise is 25–40% of theoretical maximum value.

The correct approach weights each benefit by your deployment-specific activation probability before calculating aggregate value. This guide provides a five-step framework for doing exactly that, with worked examples for a mid-size enterprise running SQL Server Enterprise and Windows Server Datacenter on hybrid infrastructure. For the complete SA context, see our Microsoft Software Assurance guide.

Step 1: Inventory SA-Covered Licences and Annual SA Cost

The starting point is a precise inventory of which licences carry active SA and what the SA premium is for each product category. Pull this from VLSC or your licensing summary report from Microsoft or your LAR (Large Account Reseller). Separate the inventory by product family: Windows Server (Standard vs Datacenter), SQL Server (Standard vs Enterprise), Office/M365 (perpetual only — SA on subscriptions is a different calculation), Exchange/SharePoint Server, and System Center.

For each product, note the annual SA cost — typically 25–29% of the initial licence value per year (negotiated SA rates vary). Sum the total annual SA cost. This is your cost baseline. For a concrete worked example, we will use: 200 SQL Server Enterprise cores + 500 Windows Server Datacenter 2-core packs, with SA costs of approximately $280,000 annually for SQL Server SA and $120,000 annually for Windows Server SA ($400,000 total).

Step 2: Azure Hybrid Benefit — Calculate Actual Azure Savings

AHUB is the dominant SA value driver for most hybrid enterprises and the most precisely calculable benefit. The calculation requires knowing which Azure VMs would be eligible for AHUB coverage from your SA-covered licence inventory.

SQL Server AHUB Calculation

Eligible cores: SQL Server Enterprise licences with SA allow AHUB application on Azure VMs at a 1:4 core ratio — each 4-core pack of SQL Server Enterprise on-premises with SA licences one 4-vCPU Azure VM for SQL Server Enterprise without paying the Azure pay-as-you-go SQL licence premium. In our worked example, 200 SQL Server Enterprise cores = 50 Standard_D4s_v5 equivalent Azure VM licences.

Azure cost delta per VM: A Standard_D4s_v5 running SQL Server Enterprise in East US at pay-as-you-go: approximately $3.20/hour all-in ($2,304/month). With AHUB (compute only): approximately $0.96/hour ($691/month). Monthly saving per VM: $1,613. Annual saving: $19,356.

If all 50 VM licences are utilised in Azure: $19,356 × 50 = $968,000 annually in AHUB savings. Compared to the $280,000 SQL Server SA cost, this is a 246% ROI even before other benefits. However, this assumes the full licence inventory maps to Azure IaaS VMs — if only 20 of 50 VMs are in Azure IaaS, the annual saving is $387,000, still comfortably positive at 138% ROI.

Windows Server AHUB Calculation

Eligible coverage: Windows Server Datacenter with SA covers all VMs on licensed physical hosts in Azure. For on-premises Datacenter Edition, AHUB in Azure requires mapping physical host licence coverage to Azure physical infrastructure — this is more complex than SQL Server AHUB. Practically, many enterprises use Windows Server Datacenter AHUB on Azure VM deployments where Windows Server is the dominant OS component.

A Standard_D4s_v5 running Windows Server at pay-as-you-go: approximately $0.58/hour ($418/month). With AHUB: approximately $0.19/hour ($137/month). Monthly saving: $281. Annual saving per VM: $3,372.

For 100 equivalent Windows Server VMs in Azure: $337,200 annual saving. Against $120,000 Windows Server SA cost, this is 181% ROI on AHUB alone.

Step 3: Licence Mobility — Quantify Hosting Cost Avoidance

If your organisation runs Microsoft server applications on third-party hosted infrastructure, Licence Mobility through SA avoids the additional licence cost that would otherwise be required. The calculation depends on your hosting arrangement — specifically, whether the hosting provider is an Authorised Outsourcer and whether licences would otherwise require purchase in the hosted environment.

Worked example: An organisation running 50 SQL Server Standard instances on managed hosting, where without Licence Mobility they would require 50 SQL Server Standard hosted licences at approximately $4,800 per licence (perpetual equivalent) or the inclusion of licence cost in the managed service contract. Hosting providers typically charge a SQL licence premium of $200–$500/server/month for licensed environments. Licence Mobility saves $10,000–$25,000 per month for 50 SQL Server Standard servers on managed hosting — $120,000–$300,000 annually.

For organisations without third-party hosting, this benefit value is zero and should not be counted in the ROI calculation. The temptation to include it as a contingency value skews the analysis. See our dedicated Licence Mobility Through Software Assurance guide for activation mechanics.

Step 4: Other Benefits — Apply Activation Probability Weighting

For benefits beyond AHUB and Licence Mobility, apply a probability weight to the theoretical maximum value based on your organisation's realistic activation likelihood. This is the step most enterprises skip — and the one that most dramatically improves accuracy.

Note the difference between theoretical maximum ($196,000) and probability-weighted value ($85,400). Using the theoretical number would overstate non-AHUB benefit value by 130%. This is why most SA ROI analyses that conclude "SA is clearly worth it" are wrong — they count benefits at 100% utilisation that are historically utilised at 15–25%.

Step 5: Aggregate ROI and Decision Rule

Sum total expected benefit value against total SA cost for the EA term (3 years). Apply a conservative and an optimistic scenario to bracket the outcome.

The worked example shows that Azure migration trajectory is the primary determinant of SA ROI for infrastructure products. In the conservative scenario (organisation is early in Azure migration), SA is marginally negative in ROI terms and the decision is a close call. In the base case (active hybrid deployment), SA is clearly positive. In the optimistic scenario, SA is highly positive.

Decision rule: If the base case SA ROI is positive by more than 15%, renew SA. If the base case ROI is negative or within a 10% margin, engage in SA scope negotiation — which licences should have SA removed, and can the SA rate be reduced on retained coverage. For the EA renewal process, this analysis should be completed 6–9 months before the agreement anniversary and used directly in commercial negotiations.