What Step-Up Rights Are and How They Work
Software Assurance step-up rights allow an enterprise to upgrade from a lower edition of a Microsoft product to a higher edition mid-term, paying only the price difference between the two editions rather than the full cost of the higher edition. This is materially different from version rights (which give access to newer versions of the same edition) and upgrade rights (which allow downgrading). Step-up is specifically about moving from a lower-tier SKU to a higher-tier SKU within the same product family — for example, from SQL Server Standard to SQL Server Enterprise, or from Windows Server Standard to Windows Server Datacenter.
The economic logic is straightforward: if you have already paid for SQL Server Standard licences with SA, and a workload now requires SQL Server Enterprise capabilities (Always On, advanced HA, unlimited virtualisation), step-up pricing means you pay approximately the difference between Enterprise and Standard list price — not the full Enterprise price from scratch. This can represent savings of 35–55% compared to purchasing Enterprise licences outright, depending on the product and the current edition pricing differential. For the broader SA context, see the Microsoft Software Assurance guide.
Products with Step-Up Rights
Not all Microsoft products include step-up rights under SA. The benefit applies to specific products where Microsoft has defined a clear edition hierarchy with a price differential. The most commercially significant step-up paths are in the server infrastructure and data platform categories.
| Product | From Edition | To Edition | Key Capability Unlocked | Step-Up Value |
|---|---|---|---|---|
| SQL Server | Standard | Enterprise | Always On AG, unlimited virtualisation, advanced analytics | High |
| Windows Server | Standard | Datacenter | Unlimited VM rights on licensed hosts | High |
| Exchange Server | Standard CAL | Enterprise CAL | Unified Messaging, DLP, Archiving | Medium |
| SharePoint | Standard CAL | Enterprise CAL | Business Intelligence, InfoPath, Visio Services | Medium |
| Skype for Business | Standard CAL | Plus CAL | Desktop client, E1 UC | Low (largely replaced by Teams) |
| System Center | Standard | Datacenter | Unlimited managed OSEs | High |
Products where step-up rights are not available or not meaningful include most Microsoft 365 SKUs (where the transition from E3 to E5 is managed through licence amendments rather than SA step-up mechanics), Azure services (cloud consumption is metered separately from SA), and standalone Microsoft 365 Apps. For the E3-to-E5 decision framework, see our M365 E3 vs E5 guide.
How Step-Up Pricing Is Calculated
Step-up pricing under SA is not defined by a single formula — it is governed by the specific SA agreement terms and the current edition price differential at the time of step-up. The general principle is that the step-up fee equals the difference between the annual SA cost of the target edition and the annual SA cost of the current edition, pro-rated for the remaining term of the current SA agreement.
In practice, for an Enterprise Agreement customer stepping up SQL Server Standard to Enterprise: the customer pays the SA renewal price differential for the Enterprise versus Standard editions, applied to the number of licences being stepped up, for the remaining EA term. If there are 18 months remaining on a 3-year EA and the SA differential for Enterprise versus Standard is $800 per core pair per year, the step-up cost for 50 core pairs would be approximately: 50 × $800 × 1.5 years = $60,000. Compare this to purchasing 50 Enterprise core pairs at list price ($3,717 per 2-core pack × 25 packs = ~$93,000 for perpetual licence alone), and the step-up saving is immediately apparent.
Actual pricing requires a formal quote from your Microsoft licensing specialist or EA reseller, as the exact differential is subject to your EA discount tier and current programme pricing. This is an area where independent advisory adds direct value — see our EA negotiation service for how we approach edition mix optimisation.
Step-up pricing is negotiable at EA renewal in the same way that base licence pricing is negotiable. Most enterprises accept Microsoft's initial step-up price without benchmarking it against market rates or applying competitive leverage. Our advisors consistently identify 10–20% improvement on step-up pricing through EA renewal negotiation — do not treat the initial quote as fixed.
The SQL Server Standard to Enterprise Step-Up: The Most Important Case
The SQL Server Standard-to-Enterprise step-up is the most commercially significant step-up right in most enterprise environments, for two reasons. First, the price differential between SQL Server Standard and Enterprise is substantial — Enterprise is priced approximately 4–5x Standard on a per-core basis. Second, the capability requirements that necessitate SQL Server Enterprise are increasingly common: Always On Availability Groups for high availability, columnstore indexing for analytics workloads, Resource Governor for multi-tenant environments, and unlimited virtualisation for Hyper-V or VMware deployments are all Enterprise-only features that growing organisations regularly encounter as workloads scale.
The step-up decision point typically arises when a Standard-edition deployment needs Always On AG configured beyond the basic availability group limits, or when a virtualisation platform is expanding to the point where Standard's two-VM limit per licensed host becomes a constraint. At this juncture, enterprises face three paths: (1) use SA step-up rights to upgrade affected licences to Enterprise edition, (2) restructure the deployment to avoid Enterprise requirements, or (3) migrate the workload to Azure SQL, where the Standard/Enterprise distinction is replaced by service tier-based pricing.
The step-up path is typically the lowest-cost option when the remaining SA term is 18 months or longer and the workload is confirmed as long-term on-premises. For workloads with a credible 24-month cloud migration timeline, Azure SQL migration may produce a lower total cost of ownership — see our Azure SQL licensing guide for that calculation.
Windows Server Standard to Datacenter Step-Up
The Windows Server Standard-to-Datacenter step-up is driven almost entirely by virtualisation density. Windows Server Standard licences provide rights to run 2 virtual machines per licensed physical host (using the full core licence count). Windows Server Datacenter provides unlimited VM rights on the licensed host. For virtualised environments running more than 2 VMs per host — which is the majority of enterprise server infrastructure — Standard licensing creates either a compliance exposure or a significant per-VM licence cost that Datacenter licensing eliminates.
The step-up economics for Windows Server are typically straightforward. Standard licensing at high VM density creates a per-VM cost that exceeds Datacenter pricing once a host runs more than 8–10 VMs. At 6–8 VMs per host, the break-even point varies based on core count and SA pricing tier. The step-up calculation compares: (current Standard SA cost per host × remaining term) + projected Standard licence additional stacks to cover VM density versus (step-up differential to Datacenter × remaining term). For most enterprise environments running modern hypervisor densities (10–20+ VMs per host), the Datacenter step-up pays back within 12–18 months.
Azure Hybrid Benefit (AHUB) interaction is also relevant here: Datacenter licences with SA provide Azure Hybrid Benefit for unlimited Azure VM rights (both Standard and Datacenter tier VMs in Azure), while Standard with SA provides AHUB for Standard-tier Azure VMs only. This makes the Datacenter step-up doubly valuable for enterprises with a hybrid on-premises/Azure deployment model.
When Step-Up Rights Make Sense — and When They Don't
Step-up rights are not always the right answer when a higher-edition capability is needed. Three conditions must hold for step-up to be the optimal path.
Condition 1 — Remaining SA term justifies the investment: Step-up pricing is applied for the remaining EA term. If you have only 6 months remaining before renewal, the step-up cost saving versus outright purchase is minimal. Step-up is most valuable when there are 18–36 months remaining on the current EA — long enough for the price differential to produce material savings, short enough that you are not committing to perpetual Enterprise licensing before confirming the workload trajectory.
Condition 2 — The workload is confirmed on-premises for the step-up term: Paying for a step-up to Enterprise edition only to migrate the workload to Azure within 12 months produces negative ROI. Step-up is appropriate for workloads with a confirmed multi-year on-premises deployment horizon. For workloads with active cloud migration timelines, quantify the Azure alternative before committing to the step-up.
Condition 3 — The capability requirement is genuine: Some Enterprise capabilities are purchased reactively, without confirming that Standard's limits are actually binding. Before executing a step-up, document the specific technical requirement driving the upgrade — for SQL Server, which workload needs Always On beyond Standard limits? For Windows Server, what is the actual VM density per host triggering the Datacenter requirement? Confirming genuine need prevents step-up expenditure on capabilities that will not be activated, which is a form of licence waste equivalent to the overspend patterns we describe in our M365 optimisation service.
Step-Up Rights in EA Renewal Negotiations
Step-up requirements provide negotiating leverage at EA renewal. If your organisation anticipates needing to step up a significant number of licences during the next EA term, this represents a known future spend that Microsoft wants to capture. Use this anticipated step-up volume as leverage to negotiate better pricing on the target edition at renewal rather than mid-term — locking in Enterprise or Datacenter pricing at renewal-time discounts rather than paying step-up premiums mid-term.
Conversely, if you have SA on Standard editions with no credible path to needing Enterprise capabilities, this is an argument for dropping SA coverage on those licences at renewal. Paying SA on Standard licences primarily to preserve step-up optionality — when the probability of stepping up is low — is a form of insurance premium for a risk that may never materialise. See our guide to dropping SA for the decision framework.
For a complete SA benefit assessment including step-up rights, version rights, Licence Mobility, and SATVs, see the full Software Assurance guide. Our EA advisory team models step-up economics as part of every pre-renewal engagement.