Closing the Deal: Final Steps and Checks Before Signing Your Microsoft EA

Why the Pre-Signing Phase Is the Highest-Risk Moment in an EA Negotiation

Enterprise Agreement negotiations are won and lost before the commercial conversation starts — in the preparation phase, where benchmarks are built and leverage is created. But they are also lost at the very end, when organisations under time pressure accept documentation that does not accurately reflect their negotiated position. Microsoft's account teams are experienced closers. The final push for signature often comes with subtle friction: "We need this signed today to lock in this pricing," or "The quarter closes Friday and we can't guarantee this discount next week." These are standard account team tactics designed to reduce scrutiny at a moment when scrutiny is most necessary.

A standard Microsoft EA runs for three years and cannot be renegotiated mid-term. Every clause, every price point, and every commitment that enters the agreement at signing governs your Microsoft relationship for the full term. The cost of a missed price lock, an overlooked auto-renewal clause, or a misquoted seat count compounds across 36 months of active licensing. Organisations that invest an additional 48–72 hours in pre-signing verification consistently avoid the most expensive contract management problems that emerge in years two and three.

Check 1: Verify Every Price Point Against the Verbally Agreed Position

The first and most important pre-signing check is a line-by-line comparison between the pricing in the final quote document and every pricing commitment made verbally or via email during the negotiation. Microsoft's sales process involves multiple pricing iterations, and it is not uncommon for early-negotiation concessions to partially disappear in the final quote — either through administrative error or through deliberate late-stage price restoration.

Current EA discounts on M365 online services and Dynamics 365 now stand at 10–20% off list price, down from the 15–25% range available before 2024's volume discount elimination. Confirm that your final quote reflects your agreed discount rate for every product in scope. Confirm that any specific concessions negotiated — Azure credits, additional SKU discounts, promotional pricing, or waived Professional Services fees — appear explicitly in the documentation and not merely in email exchanges that carry no contractual weight.

Pay particular attention to M365 SKU assignments. In 2026, the stack runs E1, E3, E5, and E7, with Microsoft actively pushing E7 ($99/user/month) over E5 ($60/user/month) at renewal. Confirm that the final quote reflects the tiered SKU distribution you negotiated — E7 for the agreed power user population, E5 for knowledge workers with high security requirements, E3 for the broader knowledge worker base — and not a blanket E7 rollout that was corrected verbally but not in the documentation.

Check 2: Confirm the Price Lock Is Contractually Binding for the Full Term

A three-year EA with no price lock is not a three-year price commitment — it is a three-year commitment to purchase at whatever price Microsoft sets at each anniversary. Microsoft's standard language may allow for price changes on products added mid-term, on products that are re-bundled or re-SKU'd during the term, and on Azure Consumption that exceeds your committed level. Negotiate explicit contractual price lock language that covers every product included in your EA on Day 1 for the full 36-month term.

Under NCE (New Commerce Experience), monthly-term subscriptions carry no discount — they are priced at list price. Annual commitments with monthly billing carry a 5% surcharge above the annual upfront price. Only annual or multi-year upfront commitments deliver meaningful price protection. If your EA includes NCE-structured subscriptions, confirm that the term structure and billing frequency in the final document matches your negotiated position, and that the price lock language extends across the NCE term duration.

For the upcoming July 2026 M365 price increase, confirm that any multi-year commitment signed before July 1 explicitly preserves current pricing for the full term. An EA signed in May 2026 that does not contain explicit language protecting against the July increase may be exposed to pricing uplift at the first annual True-Up or renewal event.

Check 3: Read the Automatic Renewal and Exit Ramp Clauses

Microsoft EAs do not automatically renew in the same way that a subscription might — a standard EA expires at the end of the three-year term, and a new EA must be actively signed to continue. However, the agreement may contain language around notification periods for non-renewal, transition obligations, or pricing changes that apply if you extend beyond the term end date. Ensure you understand exactly what happens at the end of the term: what notice is required, what pricing applies during any extension period, and what data and service continuity provisions apply.

Separately, confirm that the agreement contains a clear exit ramp for the period before the end of the term in the event of extraordinary circumstances — significant corporate restructuring, M&A, or regulatory change. While Microsoft is unlikely to accept mid-term exit without penalty for commercial reasons alone, having the mechanism clearly documented is important for your legal team's due diligence obligations, particularly if you operate in a regulated industry or are considering a transaction.

Check 4: Validate the True-Up Mechanism and Reporting Obligations

The EA True-Up is the annual reconciliation process at which your organisation reports any increase in usage above the baseline set at the start of the EA term. The True-Up date is tied to the anniversary of your EA start date. In the final EA documentation, confirm the True-Up date explicitly, confirm which products are subject to annual True-Up reporting versus those with a different reporting cadence, and confirm the window within which True-Up payments must be completed.

Under the EA True-Up model, you pay for any additional licences required above your initial commitment at the time of reporting. Unlike NCE annual subscriptions where seat additions trigger immediate billing, the EA True-Up defers additional payment to the annual anniversary. This deferred payment mechanism is one of the key remaining commercial advantages of the EA over NCE/CSP for organisations with variable user populations — but it requires accurate reporting to function properly. Confirm in the final documentation that your True-Up obligations are clearly defined and that any partial-year proration rules are explicitly stated.

Check 5: Confirm Microsoft Copilot and AI Add-On Terms

If your EA includes Microsoft 365 Copilot — priced at $30 per user per month as a standalone add-on, or bundled in the new E7 tier — confirm several specific terms in the final documentation. First, is the Copilot price locked for the full EA term at the negotiated rate? Microsoft's standard EA language may allow AI product pricing to be adjusted at renewal or annual review. Second, does the documentation specify the user population to which Copilot is assigned? A Copilot deployment limited to 2,000 users should be documented as such, with explicit language preventing automatic uplift to the full user population. Third, are there performance commitments or adoption milestones attached to any Copilot promotional pricing? Promotional pricing conditioned on specific adoption metrics introduces budget risk if adoption falls short.

Check 6: Software Assurance Coverage Verification

Software Assurance (SA) included in the EA provides on-premises use rights, upgrade rights, and various benefit entitlements. In the final documentation, confirm that SA coverage is correctly specified for every on-premises product where it is required — particularly Windows Server, SQL Server, and any on-premises Office applications where SA underpins your virtualisation licensing rights. SQL Server without SA under the per-core model requires you to licence all physical cores on a VM host if SQL Server runs on that host — a significant cost exposure that SA prevents by enabling per-VM licensing flexibility.

Check 7: Azure Commitment Language

If your EA includes an Azure Consumption Commitment (MACC), confirm the exact structure: total committed amount, phasing across the three-year term, products that qualify to consume the commitment, overage rates above the committed level, and any credit mechanisms for unused commitment. MACC overcommitment — committing to more Azure spend than your projected consumption can absorb — is a common source of year-two and year-three budget problems. Confirm the commitment level against realistic Azure growth projections before signing.

Check 8: Currency and Foreign Exchange Provisions

For organisations outside the United States, Microsoft EA pricing is typically set in the local currency or USD at the time of signing. Confirm which currency your EA is denominated in. If pricing is USD-denominated for a non-USD organisation, confirm whether there are contractual provisions capping the impact of exchange rate fluctuations — or whether you bear full currency risk for the term. Organisations that signed USD-denominated EAs in 2022–2023 and experienced significant local currency depreciation subsequently saw effective cost increases of 15–25% beyond the agreed discount rate, with no contractual remedy. Negotiate currency protection language if this risk is material to your organisation.

Check 9: The Post-Signing Transition Plan

An EA negotiation that closes without a clear post-signing implementation plan typically leads to delayed deployment, unused licences during the early months of the term, and governance gaps that accumulate into compliance exposure. Before signing, confirm that your internal teams have been briefed: IT knows which licences are being activated and on what timeline, procurement has updated its tracking systems with the new agreement details and True-Up schedule, finance has set aside budget for the first-year payment and annual True-Up estimates, and legal has filed the executed agreement in your contract management system.

For organisations adding new M365 SKUs — particularly if moving from E3 to E5 or E7 for part of the user population — confirm that the deployment and change management plan is in place before signing. Licences that sit unused because the deployment plan was not resourced at signature represent direct budget waste with no commercial remedy under the EA structure.

The Final Hour Before Signing: A Practical Checklist

In the final hours before executing the EA, run through the following checks. Confirm that the product list in the agreement matches your negotiated scope — no additions, no substitutions, no missing products. Confirm that the seat counts for every product match your right-sized licence inventory, including any adjustments made during negotiation. Confirm that the discount rates for every product are at or above the agreed commercial position. Confirm that the price lock language covers the full three-year term for all Day-1 products. Confirm that Copilot user assignments and pricing terms are explicitly documented if M365 Copilot is included. Confirm that the True-Up date and mechanism are explicitly stated. Confirm that the Azure commitment amount and phasing match the agreed position. Confirm that there are no automatic renewal provisions that could extend the term beyond three years without an active decision. Confirm that exit and termination provisions are clearly defined. Confirm that currency denomination and any FX protection language are present if applicable.

If any item on this list cannot be confirmed against the final document, do not sign. Take the additional time to resolve the discrepancy before execution. The account team's urgency is their problem, not yours. Your obligation is to sign an agreement that accurately reflects your negotiated position and protects your organisation's interests for the full three-year term. Everything else is table stakes.

Conclusion

Closing a Microsoft EA is the culmination of months of preparation, negotiation, and commercial positioning. The value captured in that process can be fully or partially lost at the signing stage if the final documentation does not accurately reflect the agreed deal. Organisations that invest time in rigorous pre-signing verification — checking every price point, every clause, every commitment — consistently experience fewer cost surprises and governance problems during the EA term than those that sign under account team deadline pressure. Take the time. Read the contract. Engage Microsoft EA advisory specialists support if you need an independent second pair of eyes. The three years that follow are a direct consequence of what you sign today.