The ten questions before signing a Microsoft EA below are the buyer-side due-diligence checklist our advisory team runs in the final ten working days before legal close. Each question is a structural clause whose answer is in the final EA paper Microsoft sends for signature — not in the proposal slides, not in the LSP’s summary, not in the verbal commitments your account executive offered three months ago. Buyers who sign without resolving these ten questions consistently absorb 8–15% more 3-year TCV than the same renewal would have produced with the questions answered before signature. In the FY26 cycle the stakes are higher: the EA tier collapse, the July 2026 M365 price increase, the Unified Support 2026 amplifier, and the CSP grace-period elimination each have clause-level implications that show up in the final paper rather than the proposal.
The questions before Microsoft EA signature below are not the diligence questions you should be asking at T-12 or T-6 of the renewal cycle — those are covered in our EA negotiation pillar guide and the EA renewal checklist tool. These ten are the pre-signature gate: the questions whose answers must be reconciled against the legal-document language before the buyer signs, regardless of how settled the deal feels in the proposal cycle. Microsoft’s pre-signature paper consistently contains structural language that did not appear in the proposal stage; the buyer-side discipline is to verify each clause against the negotiated commercial position before signature.
Why these questions before the Microsoft EA matter at signature, not at proposal
Three reasons the pre-signature gate is structurally distinct from earlier-cycle diligence.
- Microsoft’s paper template carries default language the proposal did not surface. The proposal cycle is commercial; the legal document is contractual. The audit clause, the dispute-resolution language, the price-escalation default, and the use-rights inheritance are template defaults in Microsoft’s paper that almost never appear in the proposal slides. Buyers who treat the legal document as the formalisation of the proposal rather than as its own structural negotiation consistently miss material terms.
- The pre-signature window is the last leverage moment. Once the EA is countersigned the leverage is structural — the buyer is in the EA for the term and Microsoft’s commercial incentive shifts from closing the deal to expanding the footprint. The 5–10 working days before signature are the last window where Microsoft’s commercial incentive to close still pressures their side toward concession.
- The LSP’s summary materials are not the contract. Most buyers see the EA position through the LSP’s summary slide or summary PDF, not the Microsoft Business Agreement and amendments themselves. The summary materials are accurate at a high level but routinely omit clause-level mechanics that determine 3-year cost outcomes.
The ten questions before signing the Microsoft EA
The ten questions are sequenced by structural-cost impact, highest first. Each is a clause-level question. The answer should be visible in the legal document — the EA itself, the Enterprise Enrollment, the Server & Cloud Enrollment if applicable, the MACC if applicable, and the relevant amendments.
1. Is the price protection a contract clause, or only a commercial commitment?
The most common pre-signature trap. Microsoft’s account team frequently offers verbal or proposal-stage price protection (“the price will not change for the term”); the legal document carries a different default. The question to resolve before signature: does the EA Amendment explicitly include a price-hold clause with the per-SKU pricing schedule attached, or does it carry the default language that pricing is subject to the then-current Microsoft price list at each anniversary? In the 2026 cycle the gap matters more because the July 2026 M365 price increase is the forcing function Microsoft is using to compress decision timelines.
Why: a verbal commitment is worth zero at year-2 anniversary. A clause is worth the price differential across the entire EA term.2. Does the tier-band positioning match the EA’s pre-collapse or post-collapse math?
The 2026 EA tier collapse changes the discount-band differential. A buyer who negotiated their position assuming the pre-collapse band math may find the post-collapse band differential delivers materially less benefit than expected. The pre-signature question: does the discount schedule in the legal document reflect the band the buyer was promised, and is the band differential structured against the new (collapsed) or old (pre-collapse) tier-band table? See the EA tier collapse pillar for the structural mechanics.
Why: a 1-band mis-positioning on a $30M EA is typically $900K–$1.8M of 3-year TCV.3. Is the true-up scope contractually defined, or open-ended?
The true-up clause defines what Microsoft can bill at anniversary. The pre-signature question: does the clause enumerate the SKUs subject to true-up, or does it use the open-ended “Enrolled Products” or “Additional Products” framing that lets Microsoft expand the true-up scope at anniversary? The open-ended framing is the default in Microsoft’s paper. The buyer-side counter is to enumerate the SKUs explicitly and require that any addition is by amendment rather than by anniversary reconciliation. See our true-up defence service for the audit-side parallel.
Why: an open-ended true-up clause is the single most common cause of mid-term cost surprises.4. Is the audit clause the standard Microsoft Verification clause, or a negotiated variant?
Microsoft’s default audit clause grants verification rights, a 30-day cure period for any identified shortfall, and back-billing at retail prices. A negotiated audit clause typically extends the cure period to 60–90 days, caps back-billing at EA-discounted prices rather than retail, and requires reasonable advance notice. The pre-signature question is whether the audit-clause language in the legal document reflects the negotiated variant or the standard. Our audit defence pillar guide walks the clause-level mechanics.
Why: a standard audit clause on a deployment with even 3–5% shortfall risk is materially worse than the negotiated variant.5. Does the Unified Support proposal land in the EA, or is it separated?
Microsoft frequently positions Unified Support to land alongside the EA close, even when the Unified Support cycle is calendar-misaligned. The pre-signature question: is the Unified Support engagement separated from the EA legal document, on its own renewal cycle, and modelled on its own ratio? The Unified Support 2026 guide walks the structural separation argument. Bundling Unified Support into the EA close removes the buyer-side ability to renegotiate the support deal on its own cycle.
Why: a bundled Unified Support adds 8–12% structural amplifier to the EA cost and is the hardest line-item to renegotiate mid-term.6. Does the Copilot scope match the modelled deployment, or the optimistic deployment?
The Copilot scope in the EA proposal is frequently sized to the “aspirational” deployment rather than the modelled deployment. The pre-signature question: does the Copilot for M365 seat count in the legal document reflect the realistic 12–24 month adoption curve, or the aspirational target? Aspirational sizing is one of the largest sources of EA over-spend in 2026; the seats are billed regardless of activation. Use the Copilot ROI calculator to model the realistic adoption curve before signature.
Why: 30% over-sizing on Copilot at $360/seat/year is $108K per 1,000 seats per year.7. Are the anniversary mechanics defined for both true-up and true-down?
Microsoft’s default EA anniversary mechanics are asymmetric: true-up additions are permitted, but true-down reductions are not. A negotiated EA can include partial true-down rights (typically 5–10% per year on subscription components) or scoped reduction rights for specific SKU families. The pre-signature question: does the legal document include the negotiated true-down or reduction language, or does it carry the asymmetric default?
Why: true-down rights are the only structural way to recover from over-sizing without waiting for renewal.8. Is the MACC growth-discount curve structured against the buyer’s realistic ramp?
The MACC growth-discount model rewards Azure consumption growth above the committed baseline. The pre-signature question: is the MACC baseline structured against the realistic ramp, or against the Microsoft-recommended ramp? An over-committed MACC baseline produces consumption shortfall (which Microsoft does not refund); an under-committed MACC baseline forfeits the growth-discount tier. See our MACC negotiation guide for the curve mechanics.
Why: a 20% MACC over-commitment on a $10M annual MACC is $2M of consumption shortfall over the term.9. Is the exit clause structured to allow MCA-E transition or successor-EA negotiation?
The EA exit and successor-document language determines what happens at end-of-term. The pre-signature question: does the EA include explicit language that the buyer may transition to MCA-E at renewal without forfeiting price protection or discount-band continuity? Microsoft’s default end-of-term language frequently assumes EA-to-EA continuation; an explicit MCA-E transition clause is a negotiated addition.
Why: the MCA-E transition is the buyer-side optionality that preserves leverage at the next renewal. Without an explicit clause, the buyer is in a single-vendor end-of-term negotiation.10. Are the verbal commitments documented in the legal paper?
The pre-signature catch-all. Every material verbal commitment from the account team or the LSP — bespoke training credits, dedicated account-management hours, accelerated deployment workshops, executive briefings, named partner-architect support — must be documented in writing, either as a side letter, an amendment, or a clause in the EA. Verbal commitments not in writing are unenforceable at year-2 when the account team has rotated. This is the single highest-incidence pre-signature gap in our practice.
Why: account-team rotation rates at Microsoft mean year-2 staff have no obligation to honour year-0 verbal commitments. The contract is the only durable record.Inside the final 10 working days before an EA signature?
30-minute scoping call. Pre-signature gate review is a standard advisory track.
How to run the questions-before-signing-microsoft-ea gate in practice
Four practical disciplines for running the 10-question gate.
- Run the gate on the legal document, not the LSP summary. The LSP summary materials and proposal slides are not the contract. The legal document is the EA, the relevant amendments, the enrollment paperwork, and any side letters. The gate questions need to be reconciled against the actual paper.
- Allocate 5–10 working days for the gate. The gate cannot be run in 48 hours. Microsoft’s pre-signature pressure is to compress the legal-review window; the buyer-side discipline is to allocate the gate days in the calendar before the signature week, not during it.
- Use the EA-day-before-signature window for the highest-impact clauses. Questions 1, 3, 5, and 10 are the four with the highest TCV impact and the highest typical pre-signature gap. If gate time is constrained, prioritise these four.
- Document the gate outcomes in a memo before signature. The gate produces a memo that documents each question, the clause language in the final paper, and the buyer-side acceptance or open issue. The memo is the audit trail for year-2 enforcement.
2026-specific additions to the pre-signature gate
Five 2026 inflection points add clause-level questions to the gate.
- EA tier collapse — verify the band positioning matches the post-collapse table.
- July 2026 M365 price increase — verify the price-hold clause is documented and scoped per SKU.
- E7 Frontier Suite — if E7 is in scope, verify the suite-component licensing is enumerated, not bundled by reference. See the E7 pillar.
- Agent 365 — if Agent 365 is in scope, verify the per-user vs per-control billing model. See the Agent 365 pillar.
- Copilot Studio four-mechanism — if Copilot Studio is in scope, verify which of the four billing mechanisms applies (PAYG / Capacity Packs / CCCU / ACU) and whether the EA captures the right one. See the Copilot Studio 2026 pillar.
The most common single mistake in the pre-signature window is to trust the LSP’s assurance that “the paper matches the proposal.” In our practice, the paper matches the proposal in roughly 60% of pre-signature reviews; in 40% there is at least one material clause-level gap. The 10-question gate is the structural discipline that catches the 40%.
The Microsoft Negotiations briefing
Monthly. Pre-signature playbooks, EA negotiation moves, audit defence, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the pre-signature gate next
The 10-question gate pairs with the broader renewal-cadence framework. The EA renewal preparation landing page walks the T-12 / T-9 / T-6 / T-3 cadence; the Q4 EA negotiation checklist walks the FY-end cadence; the EA amendment request playbook covers post-signature changes when a gate question surfaces an issue after close. For buyers in the final 10 working days, the free EA assessment is the direct entry point.