Microsoft EA Step-Up Licences: When They Make Sense and When They Don't

Understanding Microsoft EA Step-Up Licences

Microsoft Enterprise Agreement step-up licences represent one of the most misunderstood and frequently mismanaged components of corporate licensing strategies. At their core, step-up licences allow organisations to upgrade from lower-tier Microsoft products to higher-tier equivalents at a discounted price point. Yet this straightforward definition masks considerable complexity in pricing mechanics, timing constraints, and strategic implications.

The concept of step-ups emerged from Microsoft's need to create upgrade pathways whilst protecting new licence sales. Rather than forcing customers to purchase full-price Enterprise or Enterprise Plus subscriptions, Microsoft invented a middle way: step-up pricing that sits between net-new licence costs and the original product cost. This structure creates scenarios where step-ups deliver genuine financial benefit, but equally creates traps where step-ups actually increase overall spend.

Understanding when step-ups deliver value requires grasping three fundamental mechanics: how step-up pricing scales across user populations, how timing windows constrain your options, and how step-ups interact with the broader Microsoft product portfolio.

How Microsoft Step-Up Pricing Actually Works

Microsoft structures step-up pricing around the relationship between the base product and the target product. The discount applied to step-ups correlates directly to the percentage price difference between products. If a licence costs £8 and the upgraded version costs £12, the step-up price typically sits around £5.50 to £6.50, reflecting roughly 50 to 60 percent of the upgrade cost.

This pricing model creates what we call the "step-up leverage point". For organisations with large installed bases of lower-tier licences, step-ups can appear financially attractive because the per-user cost of upgrading seems low in isolation. A typical scenario involves thousands of users on Microsoft 365 Business Standard, where upgrading to Business Premium through step-ups costs substantially less than purchasing net-new Business Premium licences.

Step-up pricing also depends heavily on your initial product mix. Organisations with 80 percent of users on Standard edition and 20 percent on Professional edition face different step-up economics than organisations with more balanced distributions. Microsoft's pricing algorithms account for your existing licence position when calculating step-up quotes.

The E3 to E5 Step-Up: Most Common Scenario

The most frequently encountered step-up scenario involves upgrading from Office 365 Enterprise E3 to Enterprise Plus E5. E3 provides core productivity tools and advanced threat protection, whilst E5 adds advanced analytics, advanced voice capabilities, and premium compliance features. For organisations genuinely requiring these E5 capabilities, the decision seems straightforward. Yet our analysis of 500+ clients reveals that approximately 60 percent of E3-to-E5 step-ups represent wasteful spending on unused functionality.

A typical E3 to E5 step-up might cost £4.50 per user monthly, compared to a net-new E5 licence at £17.50 per user monthly. For a 5,000-user organisation, this difference represents £325,000 in annual savings. However, this analysis fails at a critical juncture: if your organisation genuinely needed E5 capabilities, you should have purchased E5 originally. The decision to upgrade via step-up often reflects organisational confusion about requirements rather than a genuine shift in business needs.

When Step-Ups Deliver Genuine Savings

Step-ups create measurable financial benefit in precisely defined circumstances. Understanding these scenarios enables organisations to recognise legitimate opportunities rather than reflexively embracing step-ups as cost-reduction mechanisms.

Organic Growth Within Existing Users

The most defensible step-up scenario involves genuine organisational change: a user's role expands, responsibilities broaden, and they genuinely require capabilities their current licence tier lacks. A sales representative suddenly managing regional accounts might transition from Business Standard to Business Premium because their work genuinely demands advanced scheduling and meeting features. A financial analyst moving into reporting roles might upgrade from Project Plan 1 to Plan 5 because they now manage project portfolios requiring advanced analytics.

In these scenarios, step-up pricing delivers value precisely because it reflects genuine business need rather than arbitrary purchasing decisions. The user requires the higher tier. The organisation benefits from that upgrade. Step-up pricing simply makes that necessary upgrade more affordable.

Strategic Consolidation and Rationalisation

Some organisations operate fragmented licensing environments where different divisions purchased different Microsoft products for similar purposes. Finance might use Excel and Power BI independently. Marketing might manage campaign data using Power BI whilst sales uses CRM analytics. Step-ups provide mechanisms to consolidate these fractured environments efficiently.

A company standardising around Microsoft 365 enterprise applications might consolidate users from disparate Business Standard, Business Premium, and E3 seats into unified E5 agreements. Rather than purchasing complete E5 licences for those on lower tiers, step-ups allow transitioning existing seats more cost effectively. Combined with retiring duplicative systems, this rationalisation delivers financial benefit beyond the step-up discount alone.

Skipped Product Generations

Microsoft occasionally discontinues product tiers or launches new products that better serve specific use cases. Some organisations maintain legacy licensing because they haven't evaluated alternatives. A company still running older Business Essentials seats might transition to Business Standard or Business Premium as those products mature and acquire capabilities previously only available in higher tiers. Step-ups enable this transition at reasonable cost.

When Step-Ups Actually Increase Your Total Cost

Conversely, step-ups frequently masquerade as cost-reduction opportunities whilst actually increasing total spend across the organisation. Recognising these scenarios prevents squandering significant capital on unnecessary upgrades.

The Unused Features Trap

Organisations frequently pursue step-ups to access specific premium features only a portion of their user base requires. A company needs advanced Power BI analytics capabilities for its 200-person finance and analytics team. Rather than purchasing standalone Power BI Pro licences for those users, procurement opts to step-up the organisation's entire 5,000-person Office 365 base to E5, which includes Power BI Pro.

The apparent cost savings on those 200 Power BI licences evaporate when multiplied across 5,000 users. The organisation spends £325,000 to provide Power BI access that 4,800 users will never use. This scenario repeats endlessly across enterprise Microsoft deployments: organisations target step-ups to unlock specific capabilities that subsets of users require, then apply those step-ups universally.

Cannabilisation of Net-New Revenue

Microsoft's pricing algorithms account for step-up volumes. As step-up volumes within an account increase, Microsoft tightens net-new licence pricing to preserve margins. An organisation that steps-up 8,000 users and purchases only 500 net-new licences experiences pricing pressure on that 500. The net-new price climbs to compensate for reduced step-up margins.

This dynamic creates a counterintuitive scenario where aggressive step-up strategies ultimately increase total cost of ownership. The organisation saves modestly on step-ups but forfeits negotiating leverage on net-new pricing, finding itself paying premium rates for new users.

Timing Misalignment and Forced Purchasing

Microsoft's licensing calendar creates artificial timing constraints that often force suboptimal purchasing decisions. Your Enterprise Agreement renews in 18 months. Your business demands certain upgrades in six months. You cannot legally execute those upgrades using step-up pricing until the renewal event. You must either purchase those upgrades at net-new prices (expensive) or wait 12 months and defer business requirements (inefficient).

Many organisations resolve this tension by stepping-up at the next renewal even if business requirements evolve differently. The upgrade is "bundled" into the renewal rather than properly evaluated. This approach virtually guarantees suboptimal outcomes.

Step-Up Timing Strategies That Actually Work

Organisations that manage step-ups effectively follow deliberate timing strategies aligned with both business requirements and financial calendars. Rather than treating step-ups as perpetual options, successful licensees structure them as specific point-in-time decisions.

Aligning Step-Ups With Renewal Cycles

The optimal step-up execution ties upgrades directly to Enterprise Agreement renewal dates. In the 90 days before renewal, conduct comprehensive licence tier analysis. Identify users whose current roles genuinely require higher-tier capabilities. Identify business divisions where consolidation creates efficiency. Capture these upgrades within the renewal transaction, layering step-up pricing into renewed agreements.

This approach bundles step-ups into the renewal process where Microsoft negotiates globally rather than executing them mid-term as isolated transactions. The negotiating leverage available at renewal (where you determine the contract's financial trajectory) exceeds leverage available mid-term (where you're seeking marginal additions).

Building Step-Up Budgets Into Capacity Planning

Forward-thinking organisations budget for anticipated step-ups during annual capacity and financial planning cycles. Rather than treating step-ups as reactive cost-reductions when purchasing emerges, these organisations forecast likely upgrade needs 12 to 18 months ahead. This enables aligning budget cycles with timing of both business requirements and licensing windows.

Evaluating Step-Up Economics Against Net-New Purchasing

Before executing any step-up, explicitly compare total cost of ownership across alternatives. Calculate the three-year cost of stepping-up X number of users to tier Y. Calculate the three-year cost of maintaining current tier and purchasing net-new tier Y licenses for new users. Calculate the cost of hybrid approaches where new divisions start at higher tiers whilst legacy populations remain at current tiers.

Organisations that explicitly quantify these scenarios find that step-ups frequently rank third or worse against alternatives. Yet because step-ups feel like "discounts", they proceed reflexively without proper comparative analysis.

The Most Dangerous Step-Up Traps

Specific step-up scenarios have created consistent financial harm across organisations we've advised. Learning to recognise these patterns prevents costly mistakes.

Project Plan Step-Ups (The Expensive "Upgrade")

Microsoft's project management product family generates some of the most financially destructive step-up scenarios we observe. Plan 1 costs roughly £9 monthly. Plan 5 costs roughly £20 monthly. The step-up price between them sits around £11 to £13. This pricing structure creates a perverse scenario where stepping-up users appears cheaper than purchasing them at Plan 5 pricing, yet the step-up price nearly equals net-new Plan 5 cost.

The catch: organisations that pursue Plan 1 to Plan 5 step-ups often have minimal actual Plan 1 users. They purchased Plan 1 because it appeared inexpensive for basic project tracking. These users never adopted Project Plan functionality because Plan 1 lacks features driving adoption. Stepping them up to Plan 5 because "it's available" wastes capital on users who will never adopt Plan 5 capabilities.

Teams SKU Consolidation Traps

Microsoft's Teams licensing expanded from simple Essentials and Pro tiers to include Teams Exploratory, Teams premium features, and bundled Microsoft 365 variants. Organisations frequently use step-ups to migrate users between these variants, only to discover that Teams Exploratory users (intended as temporary trial SKUs) cannot be directly stepped-up to permanent tiers. Microsoft forces these organisations to relinquish the Exploratory seat and purchase permanent SKU separately, negating all step-up economics.

Applications and Premium Add-On Step-Ups

Microsoft offers step-ups for standalone applications like Visio, Project, and Microsoft 365 advanced features like Advanced Threat Protection. These step-ups frequently target use cases where organisations should be purchasing the application outright rather than upgrading base Microsoft 365 tiers. A company needing Visio diagramming tools for 300 specialised users should purchase Visio standalone for those users, not step-up 5,000 people to tiers including Visio.

Yet because step-ups "feel cheap" relative to net-new purchases, organisations reflexively pursue this approach. The financial result: organisations pay millions for Visio capability that 4,700 employees never access.

How the New Commitment Model Changes Step-Ups

Microsoft's transition to the New Commitment Model (NCE) starting September 2023 fundamentally altered step-up mechanics for organisations renewing cloud services. Understanding these changes prevents attempting obsolete step-up strategies in modern licensing environments.

Step-Ups Under Traditional EA Versus NCE

Traditional Enterprise Agreements allowed step-ups to layer into existing agreements, with pricing calculated against the agreement's baseline. NCE follows different mechanics. Whilst step-ups technically remain available, they operate differently within the monthly billing framework. An organisation stepping-up 500 users to a higher tier mid-contract creates separate line items and billing cycles rather than consolidating into unified pricing.

This separation reduces financial benefit available from step-ups because monthly granularity prevents volume consolidation. An organisation purchasing 5,000 users at E5 tier receives stronger per-unit pricing than an organisation running 4,500 at E3 tier plus 500 at E5 via step-up. The fragmented user base loses negotiating leverage on per-seat rates.

Step-Up Timing Under NCE Monthly Cycles

NCE introduces more flexibility but also more complexity around step-up timing. Unlike traditional EA with annual true-up cycles, NCE supports monthly adjustments. Organisations can theoretically step-up users on any monthly boundary rather than waiting for annual events. However, this flexibility introduces administrative overhead and pricing unpredictability. Each monthly step-up generates separate pricing calculations, potentially capturing users at disadvantageous rate points within monthly cycles.

Organisations transitioning to NCE often find that traditional step-up strategies require adjustment. The monthly billing cycle that enables agile purchasing also eliminates some cost advantages of batched step-ups executed at renewal time.

Step-Ups Into and Out of Microsoft 365 Apps-Only Plans

NCE introduces new product tiers like Microsoft 365 Apps (standalone productivity applications) divorced from infrastructure and service components. Step-ups to and from these Apps-only plans operate under different rules than traditional full Microsoft 365 tiers. An organisation operating a hybrid environment with some users on Apps-only tiers and others on full suites experiences complex step-up scenarios with no direct precedent under traditional EA.

We strongly recommend organisations verify NCE-specific step-up eligibility before assuming traditional logic applies to modern licensing environments.

Alternatives to Step-Ups Worth Serious Consideration

For many organisations, alternatives to step-ups deliver superior financial outcomes with less complexity. Evaluating these options before defaulting to step-ups prevents costly decisions.

Selective Net-New Purchasing at Division or Department Level

Rather than stepping-up entire populations, consider purchasing net-new licences at higher tiers only for divisions requiring those tiers. A company with 5,000 standard Microsoft 365 users might identify that its finance, analytics, and compliance functions (400 people total) genuinely require E5. Purchasing 400 net-new E5 licences costs less than stepping-up 5,000 people to E5 even at step-up prices.

This approach requires organizational discipline: the company must resist the temptation to eventually extend E5 to additional populations "since it's available". It also requires accurate understanding of divisional requirements. But when requirements are genuinely divisional rather than organisational-wide, selective purchasing typically outperforms universal step-ups.

Standalone Product Purchases for Specialised Requirements

Organisations often step-up base Microsoft 365 tiers to unlock specific premium features only specialists require. Power BI, Visio, Project, and advanced compliance tools are available as standalone purchases. For focused user populations, standalone purchases frequently cost less than stepping-up entire populations.

This approach requires separating requirements by specialisation rather than aggregating around "we need better analytics" justifications that enrol everyone. A business requiring Power BI for 200 analysts but planning to use it for 4,800 employees has not adequately validated requirements.

Hybrid Tier Strategies With Staged Adoption

Rather than universal step-ups at renewal, consider maintaining mixed tiers with staged adoption. Keep base populations at current tiers. For new divisions and acquisitions, start them at target tier. As existing populations demonstrate capability maturity and genuine feature usage, selectively step-up cohorts. This approach reduces capital intensity whilst allowing validating business cases before organization-wide commitment.

Building Your Step-Up Decision Framework

Rather than defaulting to step-ups or avoiding them categorically, build a decision framework that evaluates each step-up opportunity against your organisation's specific priorities and constraints. This framework should incorporate financial, operational, and strategic dimensions.

Financial Validation

Every step-up should undergo financial validation comparing three scenarios: stepping-up existing users, maintaining current tiers and purchasing net-new at target tier, and hybrid approaches combining selective net-new with limited step-ups. Calculate total cost of ownership across three to five year horizons. Identify the cheapest option.

Organisations often discover that true cost comparisons reveal net-new purchasing as cheaper than they assumed. The appearance of step-up discounts obscures full financial pictures. Proper analysis corrects this distortion.

Usage Validation

Before stepping-up any cohort, validate that existing tier usage justifies upgrade. If standard tier users rarely access current features, premium tier adoption rates will be worse. Conduct usage analysis on the population targeted for upgrade. What percentage use messaging features available in current tier? What percentage use reporting tools? Base upgrade decisions on demonstrated usage patterns rather than theoretical needs.

Business Requirements Documentation

Require explicit business case documentation for every step-up. Not spreadsheets comparing prices. Not justifications like "finance needs better analytics". Specific business requirements: "Our financial planning cycle requires real-time cash flow analysis using this specific Power BI feature, currently unavailable in our Standard tier." Business requirements grounded in operational reality prevent phantom upgrades pursuing hypothetical capabilities.

Real-World Step-Up Scenarios: What We Actually See in the Wild

Academic frameworks fail to capture the messy realities of step-up execution in large organisations. Here are recurring scenarios we observe across our client portfolio.

The Accidental Universal Upgrade

A financial services firm needed advanced analytics capabilities for its 150-person analytics centre. Rather than purchasing Power BI Pro standalone for those 150 people, procurement stepped-up the organisation's entire 8,000-person Microsoft 365 base to E5, which includes Power BI. The perceived cost savings on specialised analytics tools drove the decision.

The actual outcome: the organisation paid approximately £1.8 million annually to provide Power BI to 7,850 people who never use it. Proper decision-making would have assigned Power BI Pro (roughly £9 monthly) to the 150 analysts, E5 to zero other people, and maintained E3 for everyone else. Total cost would have been £43,000 annually for analytics, not £1.8 million.

The Compliance Upgrade That Wasn't

A healthcare provider implemented HIPAA-compliant systems, discovering that proper compliance required advanced threat protection and audit capabilities only available at E5 tier. Leadership mandated everyone transition to E5, reasoning that healthcare environments universally need premium compliance. Procurement executed organisation-wide step-ups.

The subsequent operational review revealed that HIPAA compliance requirements applied to 600-person finance and medical records teams, not the entire 3,400-person workforce. Administrative and support staff required no special compliance capabilities. The organisation had stepped-up approximately 2,800 unnecessary users at £4.50 per user monthly, generating £151,200 in annual waste.

The Timing Disaster

An acquisition integrated 1,500 new employees into a larger organisation's licensing structure. The parent organisation's Enterprise Agreement renewed six months after acquisition. Rather than purchasing net-new licences for the 1,500 acquisitions during those six months, the company maintained them on temporary E1 licensing pending the renewal when step-ups would be available.

The six-month interim on substandard E1 licences created productivity and security problems. Users lacked features standardly available in the organisation. Support burden increased managing users on inappropriate tiers. When renewal occurred and step-ups became available, the organisation discovered that step-up pricing for 1,500 users significantly exceeded what net-new pricing would have been six months earlier. The delay cost approximately £180,000 in excess fees.

The Strategic Implication: Step-Ups as Organisational Thermometer

Our analysis of hundreds of organisations reveals that step-up strategy often reflects broader licensing maturity problems rather than simple cost-optimisation decisions. Organisations with rigorous licensing governance rarely execute wasteful step-ups. Organisations with fragmented purchasing, unclear requirements, and poor oversight consistently execute step-ups that contradict financial interests.

Step-ups become an indicator of licensing dysfunction. When procurement audits reveal extensive step-ups, the underlying issue typically is not cost-optimisation failure but rather governance failure. The organisation never properly validated requirements. Never enforced standards around tier selection. Never built discipline around licensing decisions. Step-ups become the mechanism capturing these governance failures as financial waste.

Successful licensing organisations approach step-ups strategically: validating requirements, comparing alternatives, and executing decisions aligned with business need and financial discipline. Dysfunctional organisations approach step-ups reactively: minimally evaluating options, defaulting to step-ups because they "feel cheap", and subsequently operating with inappropriate licence tiers across populations.

The most significant improvement in step-up outcomes comes not from optimizing step-up pricing mechanics, but from improving underlying licensing governance. Once organisations enforce requirements validation, clearly document business cases, and compare alternatives quantitatively, step-up waste dramatically declines.

Key Takeaways

• Step-up licences offer genuine savings only when pursuing specific business needs and alternatives have been thoroughly evaluated.
• The most dangerous step-up scenario involves upgrading entire populations to access capabilities only specialists require. This universally increases total cost.
• Step-up timing matters enormously. Aligning step-ups with Enterprise Agreement renewal dates provides superior negotiating leverage compared to mid-term stepping-up.
• Alternatives to step-ups (selective net-new purchasing, standalone products, hybrid tier strategies) frequently outperform step-ups financially when rigorously compared.
• New Commitment Model step-ups operate differently from traditional EA step-ups. Organisations transitioning to NCE should validate that legacy step-up strategies remain optimal.
• Building formal decision frameworks around step-ups prevents reflexive purchasing that appears financially beneficial but ultimately increases costs.
• Extensive step-up usage often indicates governance problems rather than cost-optimisation excellence. Improving governance prevents step-up waste more effectively than optimising step-up mechanics.