Microsoft EA Renewal Preparation Toolkit: Documents, Data, and Decisions Before You Negotiate

Why Preparation Is the Entire Negotiation

Enterprise Agreement renewals are not won in the negotiation itself. They are won in the preparation phase — in the quality of the data the organisation brings to the table, the clarity of its internal position, and the credibility of its alternatives. Microsoft's account team arrives at the renewal with months of preparation, using your own usage data, consumption trends, and product adoption metrics to build a proposal that maximises Microsoft's commercial outcome.

The organisations that achieve the strongest renewal results are those that complete their internal preparation before engaging with Microsoft — not those that begin preparation after receiving Microsoft's first proposal. This toolkit is structured to support that front-loaded approach. Work through each section methodically before your first renewal conversation.

The Renewal Team: Who Needs to Be in the Room

EA renewal decisions touch finance, technology, operations, and legal. Missing any of these functions from the renewal team creates coordination failures that Microsoft's account team will exploit. A well-structured renewal team has five core members, each with a defined role.

IT Asset Manager or SAM Specialist. Responsible for pulling and validating the license inventory, cross-referencing administrative portal data against ITAM records, and identifying the usage discrepancies that drive the SKU right-sizing analysis. This role owns the data foundation of the entire renewal.

Procurement or Sourcing Lead. Owns the commercial negotiation strategy, manages the relationship with Microsoft's account team, and is responsible for maintaining the competitive alternatives (BATNA) that provide negotiating leverage. This role needs to understand Microsoft's commercial model — EA structure, NCE pricing tiers, MACC mechanics — in sufficient depth to engage credibly.

Finance Representative. Responsible for the budget model, the three-year Azure consumption forecast, and the financial sign-off on the renewal terms. Finance input is essential for Azure MACC setting and for the cost-benefit analysis of SKU upgrade or downgrade decisions. Without Finance alignment, the renewal team cannot present a unified position to Microsoft.

Legal Counsel. Reviews the EA and Microsoft Customer Agreement terms, negotiates product use rights, data processing provisions, and price protection clauses. Legal review of Microsoft's standard terms identifies provisions that require amendment for the organisation's risk profile — a step that is frequently skipped and frequently regretted.

Executive Sponsor. Typically the CIO or CFO. The executive sponsor provides the escalation authority required to move the negotiation to higher levels within Microsoft when the field account team reaches the limits of their discount authority. Having a clearly identified executive sponsor also signals to Microsoft that the renewal is a senior commercial priority, which affects the quality of the team Microsoft assigns to the account.

Document Checklist: What to Gather Before You Start

Before any internal analysis can begin, the renewal team needs to assemble the source documents that provide the commercial and technical baseline. Missing any of these creates blind spots in the preparation that surface at the worst possible moment — during the negotiation itself.

Core EA Documents

Pull the current Enterprise Enrollment Agreement, including all amendments and addenda signed since the original execution. Review the enrolled products, committed quantities, pricing schedule, and any special terms negotiated at the last renewal — volume discounts, price lock provisions, True-Up adjustment clauses, and product substitution rights. These terms define the baseline from which the renewal negotiation starts.

Retrieve the Microsoft Volume Licensing Service Centre (VLSC) records or, for newer agreements, the Microsoft Admin Centre licensing inventory. This is the official Microsoft record of what is licensed under the EA — not always what the organisation believes it has. Discrepancies between the VLSC record and the organisation's internal ITAM records need to be identified and resolved before the negotiation begins.

Usage and Deployment Data

Export the M365 Usage Analytics report from the Microsoft 365 Admin Centre. This report provides, by product, the number of active users in the last 30, 90, and 180 days. The 90-day active user count is the most reliable indicator of genuine deployment: it excludes occasional or test usage while capturing users who use the product regularly.

Pull the Azure Cost Management usage and cost report for the last 12 months, broken down by resource group and service. This report provides the actual Azure consumption baseline that feeds into the MACC calculation. Export it in CSV format and retain it as a primary document — Microsoft's Azure consumption data presented during renewal negotiations may be formatted differently and should be validated against this source.

Extract the Entra ID (formerly Azure AD) user list, including last sign-in date, assigned licences, and account status. This is the primary source for identifying ghost accounts — former employees, test accounts, and inactive users who are assigned licences in the EA True-Up but generate no actual usage. Cleaning this list before the renewal baseline is set is one of the highest-return preparation activities in the entire process.

Financial Records

Retrieve the last three years of Microsoft invoice data, broken down by product category. This provides the true-cost baseline for the renewal and enables the comparison of Microsoft's renewal proposal against current spend on a like-for-like basis. Many organisations find that Microsoft's renewal proposal is presented relative to list price rather than current contracted price, making the discount appear larger than it is.

The SKU Analysis: E1, E3, E5, and E7

The M365 SKU right-sizing analysis is the single most commercially valuable exercise in the renewal preparation. The M365 stack runs E1, E3, E5, and E7 — the new top tier above E5 introduced in 2026. Each step up the stack costs significantly more per user: E3 typically costs 50 to 80 percent more than E1, E5 costs 50 to 80 percent more than E3, and E7 at $99 per user per month represents a further step above E5.

Microsoft field teams are actively pushing E5 customers toward E7 at renewal, positioning it as the natural next step for organisations deploying Copilot. E7 bundles AI and security capabilities that were previously sold as separate add-ons above E5, including Microsoft 365 Copilot at $30 per user per month. The E7 decision should be evaluated on concrete, funded deployment plans — not Microsoft's standard upsell pitch.

Building the User Segmentation Model

Map every user in the organisation to the features they actually use, drawing from the M365 Usage Analytics data. The objective is to identify the minimum SKU that covers each user's genuine needs. Common segmentation outcomes include: knowledge workers who use Exchange Online, Teams, and Office apps who require only E3; compliance and legal team members who require E5 Compliance features; security team members who require E5 Security; and frontline workers who require only E1 or F-series licensing.

The segmentation model should produce a proposed SKU mix — for example, 60 percent E3, 20 percent E5 Security add-on, 10 percent E5 Compliance add-on, 10 percent F3 — that covers every user's genuine requirements at lower total cost than blanket E5 deployment. This model becomes the quantity and SKU position the organisation presents to Microsoft at renewal.

Azure MACC Modelling

The Microsoft Azure Consumption Commitment is the variable in the EA renewal that generates the most financial exposure. Too high, and the organisation carries a committed Azure spend it cannot consume. Too low, and it forfeits the commercial credits and flexibility that MACC commitments unlock.

Build the MACC model from the Azure Cost Management data pulled in the document preparation phase. Use the last 12 months of actual Azure consumption as the baseline. Apply a conservative growth factor based only on confirmed, funded workloads planned for the next three years — not aspirational cloud adoption roadmaps or migration timelines that may slip. A baseline figure of 70 to 80 percent of projected consumption is appropriate for most organisations; the remaining 20 to 30 percent is the negotiation buffer that provides flexibility without creating a consumption shortfall.

Separate committed workloads — production applications running on fixed Azure resource types — from variable or exploratory spend. Committed workloads should be modelled with Reserved Instances or Azure Savings Plans to optimise their cost within the Azure MACC. Variable workloads should be excluded from the MACC calculation or modelled conservatively with overage flexibility terms negotiated into the EA.

The Benchmarking Requirement

No EA renewal preparation is complete without independent pricing benchmarks. Microsoft's renewal proposals are constructed to appear competitive without necessarily being competitive relative to the market. Without benchmarks, the renewal team has no objective basis for evaluating whether Microsoft's initial proposal, escalated proposal, or final offer represents market terms.

Current market benchmarks for EA renewals as of 2026: M365 E3 discounts of 15 to 20 percent off list; M365 E5 discounts of 12 to 18 percent off list; Azure MACC discounts of 8 to 15 percent above list RI rates for committed volume; Unified Support negotiated at 20 to 30 percent below standard percentage-of-contract-value calculation. These ranges are informed by our experience across 200+ Microsoft EA renewals, and will vary based on seat count, Azure commitment, and the competitive context of the specific renewal.

Internal Decision Points Before First Contact

Several strategic decisions need to be made and aligned internally before the first commercial conversation with Microsoft. Arriving at the negotiation without these decisions creates confusion and inconsistency that undermines the organisation's bargaining position.

Commitment term decision. Will the organisation commit to a three-year EA, request a shorter term, or explore the MCA-E structure? The term decision affects pricing, flexibility, and leverage. Three-year EAs provide maximum pricing certainty but minimum flexibility to adjust the SKU mix or Azure commitment mid-term. One-year or two-year terms provide flexibility but typically carry less favourable pricing. The MCA-E structure provides the most flexibility but the least structural pricing protection unless specific terms are negotiated.

E7 evaluation outcome. Has the organisation evaluated the E7 SKU for the user populations where Microsoft will likely propose it? Does the organisation have a confirmed Copilot deployment plan that would make E7 economically advantageous over E5 plus standalone Copilot? The E7 position needs to be decided before Microsoft proposes it — not in response to the proposal.

Unified Support scope. Will the organisation renew Unified Support at the same level, negotiate a different tier, or evaluate third-party support alternatives? Unified Support is a significant cost (10 to 16 percent of total EA contract value) and is routinely under-negotiated because it is treated as a given rather than a variable.

Copilot and AI add-ons. Is there a funded, approved plan to deploy Microsoft 365 Copilot across some or all users? Or is Copilot currently exploratory, with no confirmed budget or adoption target? The answer directly determines whether Copilot licensing should be included in the renewal, and at what scale.

The Preparation Timeline

Structuring the preparation work across the available time window prevents the compression of critical analysis into the weeks before the negotiation deadline. A realistic timeline for a well-prepared EA renewal runs as follows.

At 12 months before expiry, assemble the renewal team, assign document collection responsibilities, and set the internal deadline for the preparation phase to complete. At 10 months, complete the document and data collection phase, begin the SKU segmentation analysis, and initiate the Azure MACC modelling. At eight months, complete the SKU analysis and MACC model, obtain external pricing benchmarks, and complete the True-Up cleanup to establish an accurate licence baseline. At six months, align all internal stakeholders on the commercial position and begin formal engagement with Microsoft. At four months, enter intensive negotiation with a prepared counter-proposal. At two months, complete legal review and finalise execution logistics to ensure the signed agreement reaches Microsoft before the expiry date.

Organisations that compress this timeline — starting preparation at six months or less — consistently achieve worse outcomes. Not because leverage is unavailable, but because preparation quality determines how much of the available leverage is actually deployed.