Microsoft EA Multi-Year Roadmap: How to Plan and Optimise Your Enterprise Agreement Across the Full Term

Why Most EA Management Is Reactive

The default pattern for enterprise Microsoft EA management is: sign the agreement, pay the invoice, respond to the true-up request, scramble at renewal. In this model, Microsoft controls the commercial rhythm of the relationship entirely. The account team shows up when Microsoft has something to sell. The account team goes quiet when there is nothing commercially advantageous for Microsoft to discuss. You are an audience, not a negotiating counterparty.

The alternative is active, time-based management of the relationship — with a planned programme of activities across the three-year term designed to: extract value from what you have committed to, build the information and leverage position needed for the renewal, and ensure you are not surprised by cost items that should have been predictable.

This is the Microsoft EA multi-year roadmap. It has four phases across the three-year term, each with distinct objectives, activities, and commercial value.

Phase Structure Overview

Phase 1: Foundation (Months 1–6)

The first six months of an EA term contain the highest concentration of time-sensitive value. The activities in Phase 1 — if done well — deliver outcomes that compound through the remaining 30 months. If skipped or done poorly, they create problems (accumulating waste, unactivated benefits, governance gaps) that cost significantly more to address later.

Activity 1.1: Complete the Licence Entitlement Build

Within 60 days of EA signing, you should have a complete record of every licence entitlement in your agreement — every product, every count, every Software Assurance benefit, every MACC commitment. Store this in your SAM tool or procurement system. This record is your audit defence, your true-up baseline, and your renewal starting position. Organisations that do not build this record in Month 1 frequently cannot reconstruct it accurately later. The VLSC (now Microsoft 365 Admin Center and admin.microsoft.com) holds some records, but your own procurement system is the authoritative source.

Activity 1.2: Activate Software Assurance Benefits

Software Assurance benefits are time-dependent — Training Vouchers expire, Step-Up licences must be activated, Planning Services engagements must be scheduled. Many organisations sign EAs with significant SA value and allow it to lapse unused. The most commonly wasted SA benefits by type:

• Training Vouchers: Assignable to employees for Microsoft learning courses. Typically expire 12 months after EA signing. For a 2,000-user EA, training voucher value is often £20,000–£60,000. Unused = pure waste.
• Planning Services: Engagements with a Microsoft Partner to plan major deployments (Windows 10/11 migration, Azure migration, M365 deployment). Must be scheduled within the first 12 months. Available engagements depend on your SA product mix.
• Step-Up Licences: Rights to upgrade from a lower SA-covered edition to a higher edition. Activation window varies but is typically the first 12 months of the term. For SQL Server SA, for example, the right to step up from Standard to Enterprise may have time-limited activation.

For more detail on SA benefits, see our Software Assurance benefits guide.

Activity 1.3: Azure MACC Activation and FinOps Foundation

If your EA includes an Azure MACC commitment, the FinOps foundation — cost management tooling, tagging standards, Reserved Instance strategy, budget alerts — should be operational within 60 days of go-live. The cost of delayed FinOps implementation is direct Azure overspend that is preventable but not recoverable. Every month of Azure consumption without RI coverage is money left on the table. For the complete Azure FinOps guide, see our dedicated article.

Activity 1.4: Establish the Governance Framework

The licensing governance framework — policies, processes, roles, and operating cadences — should be established in the first 90 days. This includes: who owns the licensing relationship with Microsoft, who approves new licence additions, what the provisioning and de-provisioning processes are, and when the annual licence review will occur. Without this governance, licence accumulation starts from Day 1 and becomes exponentially harder to unwind.

Phase 2: Optimisation (Months 7–18)

Phase 2 is the operational optimisation phase. By Month 7, you have enough deployment data to make intelligent decisions about licence allocation. You can see which M365 features are used, which Azure workloads have stable resource requirements (and are therefore candidates for Reserved Instances), and where licence waste has begun to accumulate.

Activity 2.1: M365 Licence Harvest

The first structured M365 licence harvest should occur no later than Month 9. By this point, 30-day joiner-mover-leaver processes should be embedded enough to identify users with no recent activity. A systematic harvest — identifying and reclaiming licences from inactive accounts, leavers, and over-provisioned users — typically recovers 8–15% of M365 licences in the first pass. For a 2,000-user deployment, that is 160–300 licences at £28–£33/user/month = £53,760–£118,800/year reduction. For the full M365 licence harvesting guide, see the dedicated article.

Activity 2.2: Azure Reserved Instance Optimisation

After 6 months of Azure consumption data, workload stability patterns are visible. Run a Reserved Instance recommendation analysis in Azure Cost Management and implement RIs for workloads with stable resource requirements and high uptime. For most enterprise Azure deployments with 6 months of data, a first-pass RI commitment reduces compute costs by 25–40% compared to pay-as-you-go. The RI commitment is financially sound for stable workloads — the risk is only if workload requirements change significantly. For the Azure Reserved Instances guide, see the dedicated article.

Activity 2.3: Year 1 Annual Review

The Year 1 annual review is the highest-value governance activity in the EA management calendar. It occurs around the 12-month mark and should cover: licence utilisation versus commitment (identify waste), Azure consumption versus MACC trajectory (identify overage risk or underspend risk), Software Assurance benefit utilisation (recover unused value before expiry), and amendment opportunities (mid-term changes that improve your commercial position). For more detail on what the Year 1 review should cover, see our EA mid-term review guide.

Activity 2.4: Pursue Mid-Term Amendment Opportunities

The best time to negotiate mid-term amendments is around the Year 1 anniversary, when Microsoft is motivated to have a commercial conversation (true-up billing, product additions) and you have leverage from demonstrated deployment success or expansion plans. Amendment targets in Phase 2:

• True-up pricing lock if not obtained at signing
• MACC underspend protection if Azure consumption is tracking below commitment
• Count reduction provisions if headcount is lower than projected
• Product addition agreements at current term pricing

Phase 3: Preparation (Months 19–30)

Phase 3 is where the renewal outcome is actually determined. Organisations that begin renewal preparation in Month 31 (three months before expiry) are building their negotiating position on a foundation of no data, no leverage, and no time. Organisations that begin in Month 19 enter the renewal with 12 months of preparation advantage.

Activity 3.1: Build the Renewal Data Foundation

The renewal data foundation consists of: 24 months of utilisation data across all products, a validated entitlement record, a three-year cost trajectory model, and a competitive analysis of alternatives. This data takes 6–12 months to build properly. Starting in Month 19 means you have it complete by Month 30 — before Microsoft initiates the renewal conversation.

Activity 3.2: Define Your Renewal Architecture

Before Microsoft proposes a renewal structure, define your own. The renewal architecture specifies: which products you want to keep, which products you want to retire or reduce, what your Azure MACC target is for the next term, and whether you want to maintain the EA structure or transition workloads to CSP or MCA. Defining this architecture in advance means you evaluate Microsoft's renewal proposal against your plan — rather than Microsoft's plan becoming your plan by default.

Activity 3.3: Develop Leverage Position

Leverage in Microsoft negotiations comes from four sources: competitive alternatives (genuine evaluation of Google Workspace, AWS, alternative security vendors), deployment commitment (ability to expand to new products in the renewal), timing (controlling when you engage, not when Microsoft wants to), and authority escalation (the ability to involve senior Microsoft executives if the account team cannot deliver). Each of these leverage sources requires development time — they cannot be manufactured at Month 31.

Activity 3.4: Benchmark Current Pricing

Obtain independent pricing benchmarks for your current product mix 12–18 months before renewal. Benchmarks deteriorate in value as Microsoft pricing changes — a benchmark from 24 months ago may be materially stale. The benchmark should cover: your current effective prices versus market comparables, and the pricing you should target for the renewal. For detail on the EA pricing benchmark methodology, see our dedicated guide.

Phase 4: Renewal (Months 31–36)

If Phases 1–3 have been executed well, Phase 4 is execution, not preparation. You know what you want, you have the data to support it, and you have the leverage to pursue it. The renewal negotiation in Phase 4 should take 8–12 weeks from first formal proposal to signature. Organisations that have not done the Phase 3 preparation typically spend 16–24 weeks in reactive negotiations — and achieve materially worse outcomes.

Phase 4 Milestones

The non-renewal notice at 90 days is non-negotiable. This is not a signal that you are ending the relationship — it is a procedural step that preserves your right to negotiate rather than triggering an auto-renewal at non-negotiated terms. Every enterprise customer should send this notice as standard practice. For the complete EA renewal preparation guide, see the dedicated article.

The Independent Advisor Question

Whether to use an independent licensing advisor is a decision that should be made in Phase 3, not at the start of Phase 4. The value of independent advisory is highest in Phases 3–4, where benchmark data, negotiation tactics, and authority-level relationships determine outcomes. The case for using an independent advisor:

• Information access: Independent advisors have transactional data across hundreds of EA negotiations. Microsoft's account team has negotiated with you — a sample of one. The information asymmetry is significant.
• Leverage: Independent advisors are not dependent on the Microsoft relationship for their income. They can recommend competitive alternatives and escalation tactics without the conflict of interest that an LSP or aligned partner faces.
• Negotiation mechanics: Experienced independent advisors have navigated the specific counter-positions Microsoft uses in renewal negotiations. They know which positions are immovable and which are negotiable with the right approach.

The ROI on independent advisory is consistently 5:1 to 10:1 based on our engagement data — £40K in advisory fees delivering £200K–£400K in improved renewal terms. For the full analysis on independent versus aligned EA advisors, see our dedicated guide.

The EA Management Calendar

A practical EA multi-year roadmap is implemented through a recurring management calendar. At minimum, this should include:

Frequently Asked Questions

What if we signed the EA a year ago and have not done any Phase 1 activities?

Start immediately. Every month of delay compounds the cost. The entitlement build can still be done — pull records from VLSC, Microsoft 365 Admin Center, and your procurement system. The SA benefit activation window may have partially or fully closed — audit what remains. The licence harvest and FinOps foundation are not time-sensitive beyond the month you delay starting. Do not let the fact that you missed the optimal window prevent you from starting now.

How do we handle an EA renewal where we are already 6 months from expiry?

Focus the available time on the highest-value activities: build the utilisation data you have, develop at least one credible competitive alternative, establish a clear renewal architecture, and send the non-renewal notice immediately. An experienced independent advisor can compress preparation into a much shorter window than a fresh engagement — because they bring benchmark data and negotiation experience that would take months to build internally.

Can we use the EA multi-year roadmap with a CSP or MCA model?

The roadmap is structured around an EA, but the principles apply broadly. For CSP, the renewal is annual rather than triennial, making Phase 3/4 preparation a 6-monthly rather than 18-monthly activity. For MCA, the leverage and preparation phases are more limited because MCA provides fewer negotiating levers — but governance, FinOps, and licence management are equally important. For more on EA to cloud transition planning, see the dedicated guide.