An SA step-up licence is a Microsoft-published SKU that upgrades a Software-Assurance-covered base licence to a higher edition at the price difference (delta) between the two editions, rather than at full new-licence price. Step-ups are available across the M365 family (E3 to E5, E3 to E7, F3 to E3), the Office Pro Plus family, the Windows Enterprise family (E3 to E5), and the server families (Windows Server Standard to Datacenter, SQL Server Standard to Enterprise). Step-ups require active SA coverage on the base licence and convert with retroactive SA continuation. The 2026 amplifier is the M365 E7 (Frontier Suite) step-up framework, which prices E7 as a step-up over E5 rather than at standalone-purchase pricing for SA-covered estates. The buyer-side discipline is timing — step-ups generally are most economic at the EA anniversary or new EA enrolment rather than mid-cycle, and the delta pricing on step-up SKUs is itself negotiable inside the EA discussion. The companion M365 pillar covers the SKU map; the E7 pillar covers the 2026 Frontier Suite step-up specifically.
The starting position with the SA step-up mechanic: it is the structural reason an SA-covered estate is more economic to modernise than an un-covered estate. Microsoft maintains a price-list of step-up SKUs that allow an organisation to move from E3 to E5, from Standard to Datacenter, from Pro Plus to E3 — and now from E5 to E7 — at the delta between the two editions rather than re-purchasing the higher edition at the standalone price. The step-up SKU prices at roughly the difference between the editions plus a modest SA premium on the delta. For organisations on the modernisation track (M365 E3 to E5 to E7, security uplift, Copilot-eligibility), step-ups are the dominant economic mechanic; for organisations without SA, the same modernisation requires a full re-purchase at list price.
The SA step-up licence mechanic
A step-up licence is a Microsoft VLSC / NCE SKU that combines two operations into one purchase: it retires the base SKU as a redundant item on the licensing position, and it activates the target SKU's usage rights against the existing perpetual licence record. The transaction price is the published step-up delta between base and target editions plus the SA premium calculated on the higher edition for the remaining term. The original SA coverage on the base licence continues against the target licence through the remaining term of the EA or SA agreement; there is no SA-renewal interruption at the step-up moment.
The mechanic preserves the perpetual licence record. After a step-up from M365 E3 to M365 E5 (or Office Pro Plus to M365 E3), the perpetual rights on the base licence transfer to the target licence; if the SA lapses post-step-up, the organisation retains perpetual rights to the target edition rather than the base. The mechanic differs from an outright re-purchase, where the base SKU continues to count on the licensing position and the new SKU lands as a separate purchase.
The common SA step-up paths in 2026
Six step-up paths recur across enterprise-scale licensing estates in 2026.
| Base SKU (with SA) | Target SKU | Typical use case | Step-up notes |
|---|---|---|---|
| M365 E3 | M365 E5 | Security uplift (MDO/MDE/MDI/MDA, Defender for Cloud Apps), Power BI Pro, Phone System, Teams Premium | Most common step-up. Step-up SKU price approximately the E5/E3 delta plus SA premium on delta. |
| M365 E3 | M365 E7 (Frontier Suite) | Direct E3-to-E7 for Copilot-eligible estate; combines E3-to-E5 and E5-to-E7 in one transaction | 2026 framework. Step-up SKU prices the full delta in one motion. |
| M365 E5 | M365 E7 (Frontier Suite) | Frontier Suite uplift (Copilot for M365 included, Defender enhancements, Purview enhancements) | The 2026 amplifier. Pricing structured to incentivise E5-covered estates onto E7. |
| Office Pro Plus | M365 E3 | Office-only estate moving to full M365 (Teams, Exchange Online, OneDrive, EMS, Windows Enterprise) | Step-up SKU bundles the EMS and Windows components Office Pro Plus did not include. |
| Windows Server Standard | Windows Server Datacenter | Workloads with unlimited VOSE rights (typically virtualised host environments) | Step-up SKU per core. Step-up economic at virtualisation density above ~14 VMs per host. |
| SQL Server Standard | SQL Server Enterprise | Workloads requiring Enterprise-only features (Always On AG, advanced analytics, Polybase, hot-patching) | Step-up SKU per core. Step-up economic where Enterprise-only features are deployed. |
| Microsoft 365 F3 | Microsoft 365 E3 | Frontline worker stepping up to knowledge-worker tier | Step-up SKU bundles the desktop apps, full Exchange mailbox, and full storage components. |
SA step-up pricing discipline
Step-up SKUs price at a published delta on the Microsoft Product Terms; the EA-level discount applied to the base licences also applies (at the same level) to the step-up SKUs. Three negotiation dynamics shape the actual paid price.
First, the published delta is not the negotiated delta. Step-up SKUs are negotiable on the same EA-renewal table as the base licences; an organisation negotiating a 32 percent EA-level discount on M365 E5 also negotiates the same 32 percent on the E3-to-E5 step-up SKU. The discount is structural, not gifted. The buyer-side discipline is to insist that the step-up SKU discount track the base SKU discount at the EA-renewal table; Microsoft account teams occasionally treat step-ups as a "low-discount" category that escapes the EA discount tier, which is not contractually required and is renegotiable.
Second, the SA premium on the delta is itself a negotiation point. The SA premium on a step-up SKU calculates against the higher edition's licence value; for E3-to-E5, the SA premium is the standard ~25 percent on the E5 licence value minus the equivalent for E3, applied to the delta. The premium is published; it is also adjustable inside the EA discussion for organisations modernising across a meaningful share of the estate. Step-ups at scale (e.g., 5,000+ seats from E3 to E5) routinely carry a custom-priced step-up against the renewal.
Third, the step-up timing affects the pricing. Step-ups executed at the EA anniversary or new EA enrolment carry the EA discount and the full remaining-term SA premium. Step-ups executed mid-cycle as a true-up or mid-term amendment may not carry the EA discount unless that's negotiated explicitly, and the SA premium calculates against the remaining term only. The buyer-side discipline is to consolidate step-ups at the anniversary or renewal rather than process them as mid-term amendments.
The buyer-side step-up timing discipline
Five operating practices recur in mature step-up programmes.
Build the step-up plan as part of annual licence-position planning
The step-up plan should be a standing artefact in the annual licence-position review. The team identifies the SKUs eligible for step-up (E3 to E5, Pro Plus to E3, Standard to Datacenter), the volume of seats / cores that justify the step-up, and the business case for the higher edition. The plan feeds into the renewal-cycle preparation and the anniversary true-up motion. Organisations that treat step-ups as ad hoc requests pay structurally higher step-up prices than organisations that consolidate them.
Consolidate step-ups to the EA anniversary or renewal rather than mid-term
Step-ups executed at anniversary or renewal carry the full EA discount; step-ups as mid-term amendments do not by default. The buyer-side timing discipline is to identify step-up candidates 90 to 120 days ahead of the anniversary and process them through the anniversary order rather than through a mid-term amendment. The exception is a step-up where the SA premium math under the remaining-term mid-cycle execution is materially better than waiting to the anniversary; that case is rare but does occur (typically late-cycle, where the SA premium calculates against only 2 to 4 remaining months).
Confirm step-up SKU pricing carries the EA discount tier
The most common contractual oversight is step-up SKUs landing on the order form at undiscounted price-list rates while the base SKUs carry the negotiated EA discount. The buyer-side discipline is to verify on the order form that the step-up SKU pricing reflects the EA discount tier; if not, that is a single-clause amendment to the order form before signature. The discount is structural to the EA; it is not a separate gift.
Align the step-up to a documented business case for the higher edition's value
The step-up should be justified by the consumed value of the higher edition's features, not by Microsoft account team encouragement. M365 E3 to E5 is justified by deployed Defender for Office 365 P2 / Defender for Endpoint P2 / Defender for Identity / Defender for Cloud Apps, deployed Power BI Pro at scale, deployed Phone System, and deployed Teams Premium. M365 E5 to E7 is justified by Copilot for M365 at scale, Defender enhancements, Purview enhancements, and the Frontier Suite-included features. The buyer-side discipline is to align the step-up to the deployment plan and to defer step-ups for which deployment is not actually planned.
Plan the reversal path before executing the step-up
Step-ups are not easily reversed. The perpetual rights now sit on the target SKU; reverting to the base SKU requires a separate negotiation and may require re-purchasing the base. The buyer-side discipline is to step up only when the business case is solid; partial step-ups (subset of the user base) are preferable to wholesale step-ups where deployment intent is not yet clear. The 2026 EA dynamics make this discipline more important: the tier-collapse and lock-in dynamics tighten the cost of reversing a step-up decision made under sales-team pressure rather than deployment-team intent.
Step-up SKUs hitting the order form at undiscounted price-list rates? That is a renegotiable clause.
30-minute scoping call. Step-up SKU discount-tier alignment is standard advisory work.
The 2026 M365 E7 (Frontier Suite) step-up framework
The 2026 introduction of M365 E7 (Frontier Suite) is structurally a step-up framework rather than a new standalone SKU. Frontier Suite bundles M365 E5 plus Copilot for M365 plus Defender / Purview enhancements; the published Frontier Suite price is set as an E5-to-E7 step-up plus the bundled Copilot value. The framework rewards SA-covered E5 estates with a step-up economic that is meaningfully better than purchasing E5 + Copilot separately.
Three dynamics shape the 2026 E7 step-up decision.
- Copilot consumption profile. The E5-to-E7 step-up math depends on the Copilot for M365 deployment plan. Organisations with full-estate Copilot rollouts capture the Frontier Suite economic; organisations with sub-estate Copilot rollouts (e.g., 30 percent of seats) may find the per-seat Copilot SKU plus E5 economic better than blanket E7. The buyer-side discipline is to model both pathways and select against the actual deployment plan.
- Defender / Purview consolidation. Organisations using third-party security stacks (CrowdStrike, SentinelOne, Okta) where Microsoft Defender / Purview is not the deployed stack may find the Frontier Suite consolidation enhancements ride on infrastructure they do not use. The buyer-side discipline is to inventory the actually-deployed security and compliance stack and weigh the Defender / Purview enhancements against the deployment reality.
- Step-up timing against the tier collapse. The 2026 EA tier collapse changes the underlying base price on E5 against which the E7 step-up calculates. Organisations renewing into the post-tier-collapse pricing should run the step-up math under both pre- and post-collapse pricing; the case for E7 step-up tightens in some pricing scenarios and improves in others depending on the organisation's size and prior tier.
The least-understood step-up motion is the Office Pro Plus to M365 E3 step-up for organisations that originally licensed Office Pro Plus standalone with SA. The step-up to M365 E3 is mechanically cleaner than retiring Office Pro Plus and purchasing M365 E3 outright; the step-up SKU bundles the EMS and Windows Enterprise components and preserves the perpetual rights on the Office component. Organisations with legacy Office Pro Plus SA-covered estates of meaningful scale (>2,000 seats) should evaluate this step-up specifically at the next EA renewal; the Microsoft account team typically positions the move as a re-licence, which costs more and forfeits the SA-covered perpetual rights structure. The contractual right to step up rather than re-licence is a buyer-side leverage point at the order-form review.
The Microsoft Negotiations briefing
Monthly. SA-benefit capture, step-up timing, EA negotiation, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the step-up discipline next
The step-up discipline pairs with the broader SA-benefit framework and the EA-renewal cycle. The M365 licensing pillar covers the broader SKU map; the E7 pillar covers the Frontier Suite step-up specifically; the deployment planning article covers the highest-dollar SA benefit; the e-learning article covers the training entitlement; the HUP article covers the consumer-facing employee benefit; the M365 optimisation service is the productised step-up engagement; the EA strategy service is the broader renewal-cycle engagement; the Q4 negotiation checklist covers the timing of step-up consolidation. For organisations approaching renewal, the scoping call is the direct engagement channel; for broader scoping, the free EA assessment is the broader channel.