Microsoft EA Mid-Term Review: How to Use the Annual Review as a Commercial Lever

The Annual Review as Missed Opportunity

The Microsoft Enterprise Agreement runs for three years. Most of the commercial attention — from both the customer and Microsoft's account team — concentrates at the beginning (renewal negotiation) and the end (the next renewal). The middle period is largely treated as passive: pay invoices, submit true-ups, manage support requests through the CSM. The mid-term annual review, where it happens at all, is typically a status meeting rather than a commercial engagement.

This pattern is expensive. In a three-year EA, the organisation's technology footprint, workforce, financial position, and product requirements change materially. An EA signed in year one may reflect a headcount, cloud consumption, and product mix that is significantly different from the organisation's actual position in year two. The gap between the contracted position and the current reality creates either waste (over-licenced for products no longer deployed) or risk (under-licenced for workloads that have grown). Neither resolves itself without active management.

The organisations that extract the most value from their Microsoft EA treat the mid-term review as a structured commercial process — not an administrative checkbox. They use it to reclaim wasted licence spend, identify amendment opportunities, build their renewal negotiating position, and signal commercial intent to Microsoft's account team. The result is measurably better commercial outcomes at renewal.

The Structure of the EA Mid-Term Period

A standard three-year Microsoft EA includes two formal commercial touchpoints beyond the annual true-up: the Year 1 anniversary review (approximately 12 months after signing) and the Year 2 anniversary review (approximately 24 months after signing). The Year 3 anniversary initiates the renewal process, which deserves its own preparation framework distinct from mid-term management.

The annual true-up is a separate process from the mid-term review, though they are often conflated. The true-up is a compliance process: you report licence consumption above the contract baseline and pay for the increment. The mid-term review is a commercial process: you assess what is working, what has changed, and what commercial adjustments are available.

The Year 1 anniversary review is the most underutilised of the two. It arrives when the EA is new and the perception is that renegotiation is premature. In reality, Year 1 is the highest-value mid-term review point: you now have 12 months of actual consumption data, your technology strategy has had time to develop, and you are 24 months away from renewal — enough runway to make meaningful amendments without panic-driven decisions.

What the Mid-Term Review Should Cover

An effective mid-term review covers five analytical areas, each of which generates actionable commercial outcomes.

1. Licence Utilisation vs Contracted Position

Analyse actual licence consumption against the contracted baseline across all product lines. For each product, determine whether the organisation is over-contracted (paying for licences not deployed), under-contracted (deploying beyond the contracted baseline ahead of true-up), or appropriately contracted. VLSC, M365 Admin Centre, and Azure Cost Management provide the raw data; the analysis requires correlating licence records across three sources.

Focus on the over-contracted products first. Microsoft will not proactively flag that you are over-paying — that analysis is your responsibility. Common over-contracted products in Year 1–2: M365 E5 accepted during renewal upsell without full deployment planning; Azure MACC commitments that outpace migration velocity; Dynamics 365 licences for a deployment that is running behind schedule; and Software Assurance benefits not being consumed (training vouchers expiring, unused step-up rights).

The financial impact of identifying £200,000 in over-contracted licences at the Year 1 review is a £400,000 saving across the remaining two years of the EA term (if the amendment is executed in time). The same discovery at the Year 2 review saves £200,000. Early identification of licence waste creates compounding savings across the term.

2. Technology Roadmap Alignment

Compare your current EA product mix against your technology roadmap for the next 18–24 months. Products you will deploy should be in the EA at the right tier now (or added via amendment to capture EA pricing rather than paying overage). Products you will not deploy should be candidates for reduction or removal.

The products most likely to create misalignment at the Year 1 review: Copilot (if licences were included speculatively at renewal), Azure commitments (if the MACC was sized based on optimistic migration timelines), Power Platform (if per-user vs per-app analysis was not completed at renewal), and Dynamics 365 (if the implementation timeline has slipped).

The products most likely to be missing from the EA at Year 1: security products that were not fully evaluated at renewal (Defender for Endpoint P2, Entra Governance), developer tools that have been adopted organically (GitHub Enterprise, GitHub Copilot), and compliance products triggered by regulatory changes during the term.

3. True-Up Trajectory Analysis

Project your licence consumption trajectory through to the Year 3 true-up. If consumption is growing at a known rate, what will the Year 3 true-up cost at current rates? This projection serves two purposes: it confirms whether the current contract baseline is sustainable, and it identifies products where the cumulative true-up cost may justify an amendment to increase the contracted baseline (often at better pricing) rather than paying annual overage.

For products with growing consumption, the economic comparison is: pay incremental true-up cost annually vs. negotiate a higher baseline in an amendment at better unit pricing. In our experience, organisations that accept annual true-up cost as fixed are leaving 8–15% on the table versus organisations that proactively renegotiate high-growth products into their contract baseline before they hit significant overage thresholds.

4. Contract Term and Amendment Opportunities

Review your EA terms and amendment history for mid-term improvement opportunities. Several EA provisions can be improved through amendments if the right commercial trigger exists.

The most valuable mid-term amendment targets are: true-up pricing lock (ensuring any products added at true-up price at the contracted rate, not the then-current list price); MACC underspend protection (negotiating remedies if Azure consumption runs below commitment); count reduction provisions (allowing licence count reduction below the Year 1 baseline if headcount has decreased materially); and price protection on products not yet in the EA but anticipated to be added.

Microsoft's account team will resist amendments that increase your pricing leverage at renewal. Frame amendment requests as administrative adjustments that reflect the current business reality, not as attempts to renegotiate the deal. The language matters: "We need to align the contract to our current operational position" is received differently than "We want to reduce our costs."

5. Azure MACC Performance Review

If your EA includes an Azure MACC commitment, the mid-term review must assess MACC consumption performance against the commitment timeline. MACC commitments have a consumption deadline — if you do not consume the committed Azure spend by the end of the commitment period, the unconsumed balance is forfeited.

The MACC review should answer: What is the current consumption rate? At that rate, will the MACC be consumed within the term? If not, what is the consumption shortfall projection? What actions — Azure migrations, expanded workloads, Azure-eligible Power Platform consumption — can accelerate consumption?

MACC underconsumption at mid-term is a negotiating signal, not a crisis. If you project a significant underconsumption gap, approaching Microsoft proactively with a modified consumption plan (extending the MACC term, adjusting the commitment level, adding eligible products) is more productive than waiting until the final six months when Microsoft has less incentive to accommodate adjustment.

See the Azure MACC guide for the full MACC commercial framework.

What Can Actually Be Changed Mid-Term

A common misconception is that the EA is fixed between renewals except for additions. It is not. Several commercial changes are achievable mid-term, with varying degrees of difficulty.

Change Type	Mid-Term Achievable?	Leverage Required	Best Timing
Add new products / licences	Yes — always	Low — Microsoft happy to add spend	Any time
Increase MACC commitment	Yes — welcome	Low — increases spend commitment	When Azure growth is clear
Add price protection provisions	Possible with leverage	Medium — requires commercial event	During expansion discussion
Reduce licence count below baseline	Possible with M&A/restructuring trigger	High — requires business event justification	Following headcount reduction, divestiture, or M&A
Adjust MACC commitment level	Possible — requires relationship capital	High — Microsoft prefers fixed commitment	At 18+ months remaining if underconsumption is projected
Renegotiate discount percentages on existing products	Rarely possible	Very high — requires competitive threat or escalation	Only with credible alternative vendor engagement
Extend EA term mid-cycle	Possible — Microsoft sometimes proposes	Medium — typically Microsoft-initiated for lock-in	Be cautious — early renewal often favours Microsoft
Change billing structure (annual vs monthly)	Possible via amendment	Low — administrative change	Any time with CFO approval

The Mid-Term Review as Renewal Foundation

Every commercial position established in the mid-term review contributes to the renewal negotiation. The Year 1 review should produce a documented understanding of your current utilisation, your technology roadmap, and the commercial adjustments you want at renewal. The Year 2 review validates and updates that position with 12 more months of data.

By the time you reach the 90-day renewal window, you should not be starting the commercial analysis from zero. You should have 24 months of tracked consumption data, a benchmarked view of your pricing vs market rates, a list of commercial improvements to target, and a documented set of alternative options (competitive products, CSP alternatives, hybrid model scenarios) that provide genuine leverage.

Organisations that approach renewal without this foundation consistently accept the first Microsoft proposal with minor modifications. Organisations that have managed the mid-term actively arrive at renewal with specific, documented requirements and the analytical backing to support them. The commercial difference at renewal between these two approaches is routinely 15–25% of total contract value.

See the EA renewal preparation guide for the full renewal process framework, and the EA pricing benchmarking guide for the methodology that transforms your mid-term data into renewal leverage.

Structuring the Mid-Term Review Meeting with Microsoft

The mid-term review with Microsoft's account team should be your meeting, not theirs. Account teams approach quarterly business reviews (QBRs) and mid-term check-ins as customer success activities designed to showcase product adoption, introduce new products, and begin building the renewal narrative. If you allow them to set the agenda, the conversation will focus on what you should buy next.

To run an effective mid-term review, send Microsoft your agenda in advance. Your agenda should lead with utilisation data — your analysis, not theirs. It should include specific questions about your contract terms (true-up mechanics, price protection provisions, MACC performance). It should not be dominated by product roadmap discussions unless you have a specific product decision to make.

Three rules for mid-term review meetings with Microsoft's account team. First, never share your technology roadmap in more detail than necessary — Microsoft uses roadmap information to time product proposals for maximum commercial impact. Second, if Microsoft raises early renewal at Year 2, defer without rejecting: "We're not in renewal mode yet, but we'll be in touch when we are." Third, document every commitment Microsoft makes in writing — verbal assurances in mid-term meetings rarely translate to written EA amendments without explicit follow-up.

The Information Asymmetry Advantage

Your mid-term review position is stronger than Microsoft's by one measure: you know your actual consumption data, your financial position, and your technology intentions. Microsoft's account team knows what you have told them and what their telemetry shows about your product usage. The gap between those two information sets is your commercial advantage.

Protect information that reduces your leverage: replacement vendor evaluations, budget pressures that create urgency, or internal decisions to move workloads off Microsoft platforms. Disclose information that increases your leverage: competitive deployments of alternative products, headcount changes that might reduce licence counts, or planned workloads that will require significant new Microsoft investment — all framed as requiring favourable commercial terms to proceed.

See the guide to managing your Microsoft account team relationship for the strategic framework governing what information to share and when.

The Five-Point Mid-Term Review Checklist

Execute this five-point checklist in the 30 days preceding each annual review:

1. Pull current consumption data from VLSC, M365 Admin Centre, and Azure Cost Management. Document actual consumption vs contracted baseline for every product line. Identify over- and under-contracted positions.

2. Reconcile Software Assurance benefits. List all SA benefits included in the EA. Confirm which have been activated and used. Identify expiring or unused benefits that should be consumed before loss (training vouchers, step-up rights, deployment planning services).

3. Benchmark your current pricing against available market data. If you signed your EA 12 months ago, your renewal window in 24 months gives you time to build competitive alternatives that validate or challenge your current unit pricing.

4. Review your MACC consumption trajectory. If Azure consumption is running below commitment pace, initiate a conversation with your account team about the path to full consumption — before the final 90 days when urgency weakens your position.

5. Update your renewal commercial brief. Document the specific commercial improvements you want at renewal: discount improvements, commercial protections, structural changes to true-up mechanics, or licence count flexibility provisions. Each year of data strengthens the argument for each item on this list.

For the complete framework governing EA negotiations from initial preparation through to signature, see the Microsoft EA negotiation complete guide. For the tactical framework for mid-cycle commercial actions, see how to negotiate Microsoft without an imminent renewal deadline.

Common Mid-Term Review Mistakes

Treating the true-up as the review. The annual true-up is a compliance process — it reconciles consumption with contract. The mid-term review is a commercial process. Conflating them means the commercial analysis never happens.

Accepting Microsoft's adoption narrative as the review agenda. Microsoft's QBR agenda typically focuses on product adoption rates and roadmap introductions. Neither serves the customer's commercial interests. Set your own agenda.

Waiting until Year 2 for the first review. Year 1 review is the highest-value commercial touchpoint in the EA term. The consumption data from Year 1 informs the entire remaining term. Skipping it effectively means making the renewal decision with one year of data instead of three.

Not documenting mid-term commitments. Account team commitments made verbally in mid-term meetings — pricing assurances, product availability representations, service commitments — must be captured in writing. Verbal commitments without EA amendment carry no commercial weight.

Using the mid-term review to surface issues rather than prepare positions. Issues (product gaps, performance problems, billing disputes) should be raised and resolved as they arise, not accumulated for the annual review. The review should focus on commercial improvement, not problem remediation.

Frequently Asked Questions

Can I reduce my EA licence count mid-term without a special event?

Standard EA terms do not permit mid-term count reduction below the contracted baseline without a qualifying business event such as a merger, divestiture, or significant headcount reduction. However, organisations approaching Year 2 with evidence of sustained over-licensing sometimes achieve count adjustments through escalation to Microsoft's deal desk, particularly when tied to a renewal commitment. Independent advisory support significantly improves the success rate of mid-term count reduction requests.

How often should we meet with our Microsoft account team mid-term?

Quarterly meetings with your Account Executive and Customer Success Manager are appropriate for most enterprise EA customers. The Year 1 and Year 2 anniversary reviews should be formalised and prepared with your commercial brief. The other two quarterly meetings can be less formal but should still have an agenda you set. Frequency matters less than quality of preparation and information discipline.

Should we include an independent advisor in mid-term reviews?

For organisations with EA values above £1M/year, independent advisory involvement in mid-term reviews is commercially justified. An advisor with current Microsoft commercial intelligence provides market pricing context, identifies mid-term amendment opportunities you may miss, and manages the information dynamic with Microsoft's account team. The cost of independent advisory support is typically recovered 5–10× in improved commercial outcomes across the EA term. See the independent vs aligned EA advisors guide for guidance on selecting the right advisor type.