The Step-Up Mechanic: What It Actually Is
Step-up licensing is one of the most frequently misunderstood mechanisms in the Microsoft EA. It allows an organisation to upgrade a qualifying number of licences from a lower product edition to a higher edition during the term of an active EA — paying only the difference in licence price rather than the full price of the higher edition. It is, in principle, a commercially efficient way to upgrade without waiting for renewal and without paying for capability you already hold.
In practice, the step-up mechanic is structured in a way that typically favours Microsoft's commercial objectives over the customer's cost optimisation goals. Understanding the specific mechanics — how the differential is calculated, what pricing baseline is used, how volume tier applies to step-up licences, and when the clock resets — is essential before committing to a step-up at any scale.
This guide provides a complete technical and commercial analysis of EA step-up licensing, including worked examples of when step-up is commercially better than waiting for renewal, the negotiation framework for securing better step-up terms in your EA, and the five mistakes that cause organisations to overpay on step-up transactions.
Step-up is a commercial tool, not a product feature: The step-up mechanic is defined in your EA Enrolment and governed by your price sheet. Its availability, pricing, and conditions can be negotiated at the time your EA is signed. Most organisations accept default step-up terms because they do not know the terms are negotiable — and they pay the price at the point of upgrade.
Which Products Support Step-Up
Step-up is not available for all products in the Microsoft portfolio. The mechanism applies primarily to products that exist in clearly defined edition tiers where one edition is a functional superset of the other. The most commercially significant step-up paths in 2026 are:
| Step-Up Path | From | To | Differential (list) | Commercial Significance |
|---|---|---|---|---|
| M365 E3 to E5 | M365 E3 (~£28.10/user/month list) | M365 E5 (~£54.80/user/month list) | ~£26.70/user/month | Very High — largest step-up transaction in most enterprise EAs |
| O365 E3 to M365 E3 | O365 E3 (~£18.60/user/month list) | M365 E3 (~£28.10/user/month list) | ~£9.50/user/month | High — common legacy migration step-up |
| M365 E5 Security to E5 | M365 E3 + E5 Security add-on | M365 E5 | Varies — depends on add-on structure | Medium — requires careful differential calculation |
| Dynamics 365 Sales Professional to Enterprise | D365 Sales Professional (~£49/user/month list) | D365 Sales Enterprise (~£80.10/user/month list) | ~£31.10/user/month | Medium — common CRM growth path |
| SQL Server Standard to Enterprise | SQL Server Standard (per core) | SQL Server Enterprise (per core) | Varies — significant differential | Medium — on-premises data platform step-up |
| Windows Server Standard to Datacenter | Windows Server Standard (per core) | Windows Server Datacenter (per core) | Varies — significant differential | Medium — virtualisation-driven step-up |
How Step-Up Pricing Is Calculated
The step-up price is the difference between the price of the target edition and the price of the source edition — specifically, the prices from your EA price sheet at the time of the step-up transaction, not the prices at the time your original EA was signed.
This is the first and most important source of commercial risk in step-up transactions. Your EA price sheet reflects the list price of each product at the time of the transaction, with your negotiated platform discount applied. If Microsoft has increased list prices for M365 E5 since your EA was signed, your step-up differential is calculated against the new, higher list price — even though your original EA locked the price of E3. Your E3 price is protected; your E5 step-up is not.
The Step-Up Differential Calculation: Worked Example
Scenario: 1,000 users on M365 E3, EA signed in January 2024 with a 22% platform discount. You wish to step up 200 users to M365 E5 in March 2026.
Your locked E3 price: List £28.10 × (1-0.22) = £21.92/user/month.
Current E5 list price (after 2024–2025 price increases): £57.40/user/month (illustrative — list prices have increased since your EA was signed).
Your E5 price with 22% discount: £57.40 × (1-0.22) = £44.77/user/month.
Step-up differential per user per month: £44.77 − £21.92 = £22.85.
Annual step-up cost for 200 users: £22.85 × 200 × 12 = £54,840/year.
Compare this to what you would pay if you waited for renewal and negotiated fresh: with competitive leverage, your E5 renewal pricing might achieve £38–£42/user/month for the full E5 (not the step-up differential calculated against a higher current list). At £40/user/month for E5 at renewal, the annual cost for 200 users is £96,000/year — but you are paying for the full capability, not just the differential. The step-up approach means you are paying £21.92 + £22.85 = £44.77/user/month for the combined E3+step-up E5, versus a potentially negotiated £40/user/month at renewal.
The comparison is not always in the same direction — it depends on your specific EA pricing, the current list price trajectory, your renewal leverage, and how much of the EA term remains when you step up. This is why step-up decisions require specific modelling, not general-rule application.
Software Assurance and Step-Up Rights
Software Assurance (SA) includes step-up rights as one of its core benefits. SA step-up rights allow organisations with active SA on perpetual licences to step up to a higher edition using only a step-up licence — they do not need to purchase the full higher edition from scratch. This is one of the primary arguments for maintaining SA on perpetual licences, particularly for SQL Server and Windows Server.
The SA step-up mechanic differs from the subscription step-up mechanic described above. Under SA step-up: the organisation holds a perpetual licence for the lower edition with active SA coverage; the step-up licence covers only the differential capability; if SA lapses, the right to use the higher edition through the step-up licence is lost and the organisation retains only the base perpetual licence entitlement. For organisations considering dropping SA on server licences, understanding the step-up rights at stake is essential — see our analysis in the Software Assurance ROI guide.
When Step-Up Is Commercially Justified
The step-up decision is not binary. The financially correct answer depends on six variables: remaining EA term, the step-up differential calculation, the expected renewal negotiation outcome, the business value of accessing the higher-edition capability now vs at renewal, price escalation risk in the interim, and whether the step-up establishes a precedent that affects your renewal position.
Scenario 1: Step-Up Early in Term (12+ Months Remaining)
Step-up early in term is the scenario where the full three-year cost model matters most. If you step up 200 users from M365 E3 to E5 with 24 months remaining in your EA, you pay the step-up differential for 24 months. The total cost must be compared against: (a) waiting 24 months and negotiating fresh E5 pricing at renewal, and (b) the business value foregone by waiting 24 months to access E5 capabilities.
In most cases, stepping up early in term is commercially expensive. The differential is calculated against current list prices (potentially higher than when your EA was signed), you lose 24 months of renewal negotiation opportunity, and the total three-year cost of the step-up path is often 15–25% higher than a well-negotiated fresh E5 commitment at renewal. Unless the business value of immediate capability access is genuinely quantifiable and exceeds this cost premium, waiting is the better commercial decision.
Scenario 2: Step-Up Late in Term (6 Months or Less Remaining)
Step-up in the final six months of an EA term is a different calculation. You are paying the differential for a short period, and the step-up establishes a baseline for renewal. This can be commercially rational in two specific situations: (1) you need the capability within the term for a defined business requirement and cannot afford a six-month gap; and (2) stepping up within the term means your renewal starts from an E5 baseline, potentially avoiding the more disruptive conversation of moving from an E3 renewal to E5 adoption at renewal — though the latter point requires careful analysis, as it may be more commercially advantageous to negotiate the full E5 price at renewal from scratch.
Scenario 3: Step-Up for a Subset of Users
Targeted step-up — upgrading a specific user population to a higher edition while the majority remains at the base edition — is one of the most commercially efficient uses of the step-up mechanic. This aligns with best practice for M365 E3 vs E5 deployment strategy, which consistently shows that blanket E5 deployment for all users is commercially suboptimal in most organisations. Typical deployments justify E5 for 30–40% of users (compliance-intensive roles, executives, security-focused IT staff) while E3 or below remains appropriate for the majority.
Targeted step-up for this population — identifying the justified E5 users, stepping them up mid-term, and locking in a mixed-SKU commitment for renewal — is commercially intelligent when the alternative would be either accepting a uniform E5 offer at renewal or going through a protracted E5 justification conversation under renewal pressure.
| Situation | Step-Up Recommendation | Reasoning |
|---|---|---|
| >12 months remaining, uniform population | Wait for renewal | Differential calculated on current (potentially higher) list; better renewal leverage available |
| >12 months remaining, defined subset with business need | Step up for subset only | Captures justified population, avoids over-commitment, preserves renewal negotiation leverage |
| 6 months remaining, capability needed immediately | Step up — negotiate mid-term terms | Short differential period; establishes renewal baseline; small financial risk |
| SA-covered perpetual licences, upgrade available | Use SA step-up rights | SA step-up rights are a paid-for benefit — use them before SA lapses or renewal decision |
| Copilot deployment (all scenarios) | Do not use E3-to-E5 step-up | Copilot adds on top of E3; E5 step-up is not required for Copilot; step-up costs dwarf Copilot add-on savings |
Negotiating Better Step-Up Terms in Your EA
Step-up terms are negotiable at EA signature — but almost never revisited mid-term unless you have specific amendment leverage. The time to negotiate step-up terms is during initial EA or renewal negotiations, not at the point of a step-up transaction.
Negotiation Target 1: Step-Up Pricing Lock
Negotiate a step-up price lock provision: if you step up within the term, the step-up differential is calculated against the product prices that were in effect at the time your EA was signed — not against current list prices at the time of the step-up. This protects you against price increases between EA signature and step-up transaction. This provision has direct commercial value in an environment of regular Microsoft price increases; its value increases as the EA term progresses.
Negotiation Target 2: Volume Tier Application
Negotiate explicit confirmation that step-up licences count toward your volume tier for discount purposes. By default, step-up licences may be priced at a tier that reflects only the step-up count, not the total licences in your EA. If you are stepping up 200 licences in a 5,000-user EA, the step-up licences should receive tier pricing based on 5,000+ users, not 200 users. Ensure your EA amendment confirms the volume tier application mechanism for step-up transactions.
Negotiation Target 3: Step-Up Flexibility Provisions
Negotiate the ability to step down as well as up — particularly relevant for Copilot and E5 deployments where adoption rates may not justify the full committed population. A step-up commitment without a corresponding step-down right at annual review creates asymmetric risk. Most organisations accept step-up without step-down because the default EA terms do not offer it; it is available if negotiated explicitly.
Negotiation Target 4: Step-Up to Renewal Transition
If you step up within the term, negotiate explicitly how the step-up population is treated at renewal. The default Microsoft position is that stepped-up licences roll into renewal at the full higher-edition price — but the renewal discount applied to that population may not match the original EA discount or reflect the competitive leverage available at renewal. Establish in writing that stepped-up licences are subject to full renewal negotiation, not automatic renewal at the step-up-derived pricing.
The Copilot step-up misunderstanding: Microsoft's account teams frequently present M365 Copilot adoption as a reason to step up from E3 to E5 — arguing that certain E5 features (like Microsoft Purview data classification) are prerequisites for responsible Copilot deployment. In most cases, this is a commercial upsell, not a technical requirement. Copilot is an add-on to M365 E3 and does not require E5. If your account team is conditioning Copilot deployment on an E5 step-up, request written technical documentation of the specific E5 features that are technical prerequisites for your planned Copilot use case. In the majority of cases, E3 with targeted E5 Compliance for specific data governance scenarios is the commercially appropriate architecture — not a blanket E5 step-up.
Common Step-Up Mistakes
Mistake 1: Accepting the Default Step-Up Differential Without Independent Benchmarking
The step-up differential presented by your account team is calculated from the price sheet — which reflects list prices that may have increased since your EA was signed. Independent benchmarking of what comparable organisations are paying for E5, or what your renewal price for E5 would be, should inform whether the step-up differential represents fair value or a premium.
Mistake 2: Stepping Up the Full Population When Only a Subset Is Justified
Account teams present step-up as an all-or-nothing proposition because blanket step-up maximises revenue. It is not all-or-nothing. You can step up any subset of your licensed population. Define your justified E5 population before the step-up conversation, and negotiate for that subset only. Blanket E5 step-up for populations where E3 capability is sufficient is one of the largest single sources of M365 over-spend.
Mistake 3: Not Modelling the Full Three-Year Cost of Step-Up vs Renewal
A step-up that costs £22.85/user/month for 24 months costs £547 per user over the remaining term. A negotiated E5 fresh commitment at renewal might cost £40/user/month — £480 per user per year. At first glance, the step-up appears more expensive. But if the renewal price with competitive leverage would be £38/user/month, the annual delta widens. Model the full three-year cost of each path, not just the headline monthly rate.
Mistake 4: Treating Step-Up as a Commitment That Cannot Be Revisited
Step-up licences are subject to your EA's true-up provisions. If business conditions change and the stepped-up population no longer needs the higher edition, you can reduce the count at annual true-up (subject to your EA's count reduction provisions). This is not widely understood — and account teams rarely volunteer this information because it reduces their revenue certainty.
Mistake 5: Not Connecting Step-Up Decisions to Your EA Mid-Term Review
Step-up decisions should be made in the context of your EA mid-term review, not reactively in response to account team proposals. Your mid-term review should identify products where step-up is commercially justified based on utilisation data, business requirements, and renewal timeline — and position those step-ups as planned commercial transactions with pre-negotiated terms, not reactive responses to account team urgency.
EA Negotiation Intelligence — Weekly Briefing
Step-up mechanics, renewal tactics, true-up strategies — from 20 years of independent Microsoft EA advisory. Delivered weekly.
No spam. Unsubscribe at any time.
Frequently Asked Questions
Can I step up from M365 E3 to E5 for only some users in my EA?
Yes. Step-up is applied per user, not per EA. You can step up any number of users from the source edition to the target edition while keeping the remainder at the base edition. There is no minimum step-up count, though small counts may not achieve meaningful volume tier discounts. Define your justified E5 population before entering the step-up conversation — this is the single most important preparation step.
Does a step-up reset my EA term?
No. A step-up transaction does not reset your EA expiry date. The stepped-up licences are co-termed to your existing EA expiry. This is commercially significant: a step-up with 24 months remaining runs for exactly 24 months; if your renewal subsequently achieves better E5 pricing, you lose the flexibility to transition earlier because you have already committed to the step-up differential for the remaining term.
Is step-up available in CSP and MCA agreements?
CSP and MCA do not have a formal step-up mechanic equivalent to the EA. In CSP, you simply change the SKU — you pay the new SKU rate from the change date, without the EA's differential pricing structure. This is one area where the EA's step-up mechanism provides genuine optionality, but only if the terms are negotiated appropriately at EA signature.
How does step-up interact with my EA volume discount tier?
By default, step-up licences may be priced at the tier applicable to the step-up count alone, not your total EA volume. If you have 5,000 E3 licences and step up 200 to E5, the 200 step-up licences should receive Level C/D tier pricing based on the 5,000-user context — but this requires explicit negotiation. Verify your step-up price sheet reflects the correct tier before the transaction is processed.
If you are facing a step-up proposal from your Microsoft account team, engage our team for independent commercial analysis before committing. We provide detailed step-up cost modelling, renewal comparison, and negotiation support across all major step-up paths including M365 E3 to E5, O365 to M365, and server product upgrades.