23%Average value left on table at close due to process failure
28Critical checklist items for the final 30 days
90 daysMinimum notice required to avoid EA auto-renewal trap
Why the Final 30 Days Determine Your Commercial Outcome
Most enterprise organisations approach the final month of EA negotiation in a reactive posture — responding to Microsoft's proposals, managing internal approvals, and trying to hit a signature date that someone agreed to prematurely. This posture is commercially costly. The final 30 days should be an offensive phase, not a defensive one.
The problem is structural. Microsoft's account teams operate on quota timelines. The closer you get to Microsoft's fiscal quarter end — or to your own EA expiry date — the more pressure accumulates. That pressure is real from Microsoft's side, but it is often artificially amplified for the buyer. Account executives present deadlines that are flexible, price increases that are conditional, and offers that are not as final as described.
Organisations that enter the final 30 days with a systematic checklist — and the resolve to use it — consistently achieve better outcomes than those who treat close as an administrative exercise. The difference is not negotiating harder. It is negotiating more precisely, on the right items, in the right sequence.
This checklist is organised into five sections: pricing and commercial terms (items 1–8), contract documentation (items 9–14), amendment provisions (items 15–21), close mechanics and authority (items 22–25), and post-signature obligations (items 26–28). Work through each section in order. Never allow the sequence to be driven by Microsoft's preferred timeline.
The single most expensive close mistake: Signing the Enrolment Agreement before reviewing the complete Price Sheet. We have seen organisations sign EAs with price sheet errors — wrong product configurations, incorrect list price bases, missing discount rows — that cost £50K–£200K over the three-year term. The price sheet is legally binding. Errors discovered after signature are contractually your problem, not Microsoft's.
Facing an EA deadline in the next 30 days?
Our advisors have reviewed hundreds of EA proposals at the final stage. We identify pricing errors, missing amendment provisions, and commercial terms that cost organisations real money over the EA term. A final review engagement typically identifies 8–15% in additional savings or contractual improvements — often in under a week.
Book a Final Review Call
Download the EA Playbook
Section 1: Pricing and Commercial Terms (Items 1–8)
Item 01
Verify the Price Sheet Against Your Negotiated Position
Request the final Price Sheet (Schedule A) and verify it line by line against every pricing concession agreed during negotiation. Check: the list price baseline (which Microsoft price list version is being used), the platform discount applied, any product-specific discounts, step pricing structure if committed to volume growth, and MACC line items. A common error is that verbal discount commitments do not appear on the price sheet — they exist only in email threads or meeting notes that are not contractually binding. If it is not on the price sheet, it does not exist in contract law.
Item 02
Confirm Which Price List Version Governs Your Deal
Microsoft updates its price list monthly. The price list version that governs your EA is typically fixed at the date of submission, not the date of signature. If your negotiation has run long — particularly across a fiscal quarter or calendar year boundary — the underlying list prices may have changed, altering the actual discounted rate you achieve even if the discount percentage has not changed. Confirm the governing price list date in writing and verify that no price list update has affected your effective pricing since negotiations began.
Item 03
Verify the Licence Count and SKU Configuration in the Enrolment
Review the Enrolment Agreement's product and count table against your internal licence inventory. Check for: products you agreed to include that are missing, products that appear but were not agreed, incorrect unit counts (which affect volume tier and effective pricing), and SKU configurations that differ from what was discussed (e.g., M365 E3 with Device listed as M365 E3 without Device). Count errors at this stage directly affect your EA pricing tier and three-year cost. Cross-reference against your most recent licence inventory and the independently validated licence count your team produced during
renewal preparation.
Item 04
Confirm Azure MACC Commitment Value and Annual Draw-Down Structure
If your EA includes an Azure Monetary Commitment (MACC), verify the committed amount per year, the draw-down schedule (annual or flexible), the eligible product list for MACC consumption, the underspend treatment (carry-forward or forfeit), and the overage pricing mechanism. MACC errors at this stage are common and expensive. Check that the MACC value is netted from your EA invoice correctly and that the Azure products you plan to consume (compute, storage, Sentinel, Defender for Cloud, Arc services) are eligible for MACC offset. See our
MACC leverage guide for the full mechanics.
Item 05
Validate the True-Up Pricing Basis
True-up pricing — the price applied to licences added above your initial commitment during the EA term — defaults to the then-current list price at the time of addition unless you have negotiated a price lock. Verify whether a true-up pricing lock is included in your amendment. If it is, confirm the specific language: it should fix pricing at the EA signature price list for all additions during the term, not merely for the first anniversary period. If no true-up price lock exists, your effective pricing for growth will be whatever Microsoft's price list says at the time you grow — including any price increases. Review our
true-up clauses guide for the clause language that provides real protection.
Item 06 — High Risk
Identify Auto-Renewal Provisions and Confirm Non-Renewal Notice Deadline
The standard EA auto-renews unless the customer provides written non-renewal notice — typically 60 to 90 days before expiry, though the exact period varies by Enrolment. If your organisation intends to renegotiate, restructure, or transition at renewal, missing the non-renewal notice window locks you into another term under Microsoft's standard conditions. Identify the exact notice deadline for your agreement, confirm the required notice method (written, to which address, with what reference), and calendar this date as a hard milestone. This is one of the most expensive administrative omissions in enterprise Microsoft management — the consequences are a full additional year at current terms with no re-opening of commercial positions.
Item 07
Confirm Payment Terms and Invoice Schedule
Verify the invoicing trigger (anniversary date, not order date — a frequent source of cash flow surprises), the payment due date, the late payment provisions, and whether any upfront discount has been applied correctly. If you negotiated an upfront multi-year payment in exchange for an additional discount, confirm the discount appears on the price sheet as a separate line item and that the invoicing terms reflect the single-payment structure. Review our
EA payment terms guide for the full payment mechanics and typical upfront discount ranges by EA value.
Item 08
Run a Three-Year Total Cost Model on the Final Price Sheet
Build a three-year cost model using the final price sheet, your expected true-up additions (based on headcount forecast), MACC draw-down schedule, and any step pricing triggers. Compare this model to your initial negotiation target and to the independent benchmark you used during preparation. The goal is not to reopen negotiation at this stage — it is to confirm that the deal you are signing delivers the commercial outcome you set out to achieve, and to document the delta for your post-signature review process. Organisations that skip this step often discover six months after signature that the signed deal differs materially from what the negotiation narrative described.
Section 2: Contract Documentation (Items 9–14)
Item 09
Obtain and Review All Six EA Documents
A complete EA consists of: (1) the Enrolment Agreement, (2) the Microsoft Business and Services Agreement (MBSA), (3) the Price Sheet, (4) the Product Terms, (5) the Online Services Terms / Data Processing Addendum, and (6) any Amendments. Many organisations sign the Enrolment without reviewing the MBSA — the document that contains audit rights, payment terms, termination provisions, and liability limits. The MBSA governs the commercial relationship in the scenarios that matter most (dispute, audit, breach, termination). Not having reviewed it is not a defence when it is invoked. See our detailed
guide to reading your Microsoft EA for a clause-by-clause breakdown.
Item 10
Review the Affiliate and Subsidiary Coverage Definition
Confirm how affiliates are defined in your Enrolment — whether by named schedule or by definition (typically entities with >50% ownership). If you have recently completed or are in the process of completing an acquisition, verify that the acquired entity falls within the affiliate definition or that a transitional licence mechanism exists. Affiliates operating outside EA coverage generate compliance exposure from Day 1 of any acquisition. Our
EA affiliate licensing guide details the definition mechanics and acquisition grace period provisions worth negotiating.
Item 11
Confirm the Product Terms Governing Date
Microsoft's Product Terms update monthly and govern usage rights for all products in your EA. The version in effect at the time of EA signature does not lock — Product Terms updates apply to your existing EA as they are published. This is one of the most under-appreciated risks in enterprise Microsoft licensing. Verify whether your Amendment includes any provisions protecting against mid-term Product Terms changes that materially diminish usage rights. If not, document the current Product Terms version for your records so that any future audit can reference the rights that applied at the time of the disputed usage.
Item 12
Verify the Enrolment Start Date and Term Length
Confirm the exact EA start date, end date, and anniversary dates. If you are co-terming — aligning multiple EA Enrolments to a common end date — verify that the term length is correctly calculated for each Enrolment and that the effective pricing reflects the adjusted term. A co-terming error that extends an Enrolment by six months can add significant cost without any incremental value. See our
EA co-terming guide for the commercial mechanics and how to use co-terming as negotiation leverage.
Item 13
Confirm the VLSC Administrator Access Configuration
Verify that your Volume Licensing Service Centre (VLSC) administrator accounts are correctly configured, that licence keys for all products are accessible, and that Software Assurance benefit activation pathways are documented. VLSC access problems discovered after signature create deployment delays and SA benefit forfeiture. Confirm that the account used for VLSC matches your corporate identity governance requirements and that at least two administrators have access to prevent single-point-of-failure.
Item 14 — High Risk
Review Audit Rights Clause in the MBSA
Section 6 of the Microsoft Business and Services Agreement governs Microsoft's right to audit your licence compliance. The standard clause is broad. Verify the audit notice period, the methodology Microsoft is entitled to use, the scope of data access, the cost allocation for audit activities, and whether the clause has been modified by your Amendment. The audit rights clause as written gives Microsoft significant latitude. Negotiations at this stage have secured meaningful limitations — audit frequency, scope restrictions, methodology pre-approval requirements — that substantially reduce your audit exposure. If this clause has not been addressed and your EA involves complex deployments (virtualisation, multi-entity structure, development environments), it warrants attention before signature.
Section 3: Amendment Provisions (Items 15–21)
Amendments are the mechanism through which non-standard commercial positions are documented in the EA. They are legally binding modifications to the standard terms. Not all amendment provisions are achievable for every customer — scale, strategic importance, and the strength of the negotiation all affect what Microsoft will agree to. But the following provisions are material enough that they should be explicitly pursued before close, and the outcome — approved or declined — documented.
Item 15
True-Up Pricing Lock Amendment
The most commercially significant amendment for most enterprise EAs. Fixes the price for all products added during the EA term at the price list in effect at signature, regardless of any price increases during the term. Given Microsoft's history of 15–25% price increases, a three-year pricing lock on an EA with significant headcount growth can represent material protection — often £200K–£500K for a 3,000-user organisation growing at 10% per year. Document the outcome of your request and the specific language if approved.
Item 16
Licence Count Reduction Provisions
Standard EAs do not allow downward count adjustments during the term. You are committed to your initial licence count for three years. Count reduction provisions — allowing you to reduce licences at anniversary date if headcount declines — are achievable for large EAs (>1,000 seats) but require specific Deal Desk approval. The provision typically includes a reduction cap (e.g., maximum 10–15% annual reduction), a minimum floor, and a notice period. If your organisation has headcount volatility or is planning restructuring during the EA term, a count reduction provision is commercially important.
Item 17
MACC Underspend Protection
Standard MACC terms result in forfeiture of unspent committed amounts at the end of each year. If your Azure consumption falls short of the MACC commitment — due to migration delays, project re-scoping, or FinOps optimisation — the uncommitted balance is lost. MACC underspend protection provisions allow carry-forward of unspent amounts (typically up to 25% of annual commitment) to the following year. This provision is relevant for any EA with a MACC component above £500K/year where Azure consumption visibility is uncertain. See our
MACC leverage guide for negotiation context.
Item 18
EA-to-CSP Transition Rights
The ability to transition products from EA to CSP during the term — or to migrate entirely from EA to CSP at renewal without penalty — is a provision that creates future optionality. As CSP economics and NCE pricing have evolved, some organisations may find mid-term transition commercially advantageous. An amendment provision that pre-approves transition mechanics, transfer of licences, and treatment of SA benefits eliminates the need to renegotiate these terms under time pressure mid-term. See our
EA-to-CSP migration guide for the mechanics this provision needs to address.
Item 19
Renewal Pricing Commitment
A renewal pricing commitment locks in that your next EA renewal will be conducted at no worse than current pricing — typically expressed as "pricing at renewal shall not exceed the pricing applicable under this Enrolment at the date of renewal initiation." This provision is rarely offered without being asked for and is commercially significant given the pace of Microsoft price increases. It does not lock in a specific discount level for renewal negotiation — it prevents renewal proposals that use a higher list price base as the starting point for a nominally similar discount.
Item 20
Audit Scope Limitation Amendment
A modification to the standard audit rights clause that limits the frequency, methodology, and scope of Microsoft's audit rights. Achievable provisions include: maximum one audit per 12-month period, 60-day notice requirement, customer's right to conduct internal discovery before granting external access, limitation of audit scope to products actually licensed under the EA, and exclusion of development and test environments from scope. The difficulty of achieving specific provisions varies. The important principle is that the standard clause as written is worse than any of these modifications — requesting them has no downside.
Item 21
Divestiture Transition Licence Provision
If your organisation has any likelihood of divesting a business unit or subsidiary during the EA term, a divestiture transition provision is valuable. It pre-authorises a defined period (typically 12–18 months) during which the divested entity can continue to use Microsoft licences under the parent EA while establishing its own licence agreement. Without this provision, a divestiture creates immediate licence compliance exposure for the divested entity from Day 1 of separation — which is commercially and logistically impossible to resolve quickly. See our
EA affiliate guide for the divestiture mechanics this provision should address.
Section 4: Close Mechanics and Authority (Items 22–25)
Item 22 — High Risk
Confirm All Verbal Commitments Are Documented in Writing
This is the most frequent source of post-signature disputes. Verbal commitments — additional discount percentages, included professional services, MACC credits, complimentary pilots — made by account executives during negotiation are not legally binding unless they appear in the signed EA or a signed supplementary agreement. Before signature, compile a written summary of every commitment made outside the contract documents and request written confirmation from the account executive. Any commitment that cannot be confirmed in writing should be treated as non-existent for planning purposes.
Item 23
Verify the Microsoft Signatory Has Appropriate Authority
For standard EA renewals at AE level, Microsoft's standard signatory process is typically sufficient. For EAs that include Deal Desk-approved terms, non-standard contract provisions, or significant discount levels, verify that the Microsoft signatory has authority to bind Microsoft to the terms in the amendment. An EA signed by an account executive who lacked authority to approve the non-standard terms can create post-signature disputes about whether those terms are enforceable. Request confirmation of the signatory's authority for any agreement that deviates materially from Microsoft's standard terms. Our
Deal Desk guide covers authority levels and signatory requirements.
Item 24
Confirm Your Internal Signature Authority and Approval Process
Verify that the internal signatory for your EA has the corporate authority to commit to the value and term being signed. Many organisations have procurement policies that require CFO, board, or legal approval above certain contract values — policies that were set before the current EA value and that have not been updated. Signing an EA without proper internal authority can create legal and governance problems that surface during audit or acquisition due diligence. Confirm the approval chain, allow adequate time for it, and do not let Microsoft's close deadline pressure compress your internal governance process.
Item 25
Establish a Post-Signature Documentation Archive
Before signing, establish the document archive that will store all EA materials for the three-year term and beyond: the signed Enrolment, MBSA, Price Sheet, Amendments, the Product Terms version at signature, all negotiation correspondence, and the VLSC licence key records. This archive should be accessible to legal, finance, IT, and procurement. The most common problem in audit defence is not the compliance position — it is the inability to locate documentation. Organisations that cannot produce their own EA in an audit are at an immediate disadvantage. Assign a named owner for EA document retention before the ink is dry.
Our advisors review final EA documentation at close and identify errors, missing provisions, and commercial opportunities that organisations miss under deadline pressure.
Get a Final Review
Section 5: Post-Signature Obligations (Items 26–28)
The EA signature is not the end of the process. The 60 days immediately after signature are when the commercial value of the EA is either activated or left dormant. The following items should be in your execution plan before you sign — not discovered as action items six months later.
Item 26
Activate Software Assurance Benefits Immediately
Software Assurance benefits — training vouchers, deployment planning services, New Version rights, Home Use Programme, License Mobility — expire if unused. Many organisations do not activate these benefits until renewal year, by which time they have forfeited the equivalent of 12–18 months of value. Assign a named SA benefits owner before signature, establish an activation calendar for each benefit type by product, and set 90-day activation targets for the high-value items. Our
SA benefits guide maps the full benefit set and activation priorities.
Item 27
Launch the Azure FinOps Foundation
If your EA includes an Azure MACC, the FinOps foundation should launch in the first 30 days after signature — before consumption patterns are established and before the first Azure invoice arrives. Establish the tagging taxonomy, enable Azure Cost Management with budget alerts, run the Reserved Instance analysis (after 30 days of baseline data), and activate Azure Hybrid Benefit for eligible workloads. Organisations that launch FinOps in Month 1 consistently achieve better three-year Azure economics than those that address it in Year 2 when patterns are entrenched. See our
Azure FinOps guide for the foundation framework.
Item 28
Calendar the EA Multi-Year Governance Milestones
Before you close the negotiation file, set the calendar milestones for the full three-year EA term: the Year 1 anniversary review date, the Year 2 annual review, the 24-month pre-renewal analysis start date, the non-renewal notice deadline, and the M365 licence harvest cycle (quarterly). Organisations that calendar these milestones at signature are twice as likely to enter their next renewal with comprehensive data and a developed negotiation position. Organisations that do not calendar them typically discover their next renewal window two or three months before expiry — which is too late for any serious commercial outcome. See our
EA multi-year roadmap for the full governance calendar.
Terms You Should Never Accept Under Deadline Pressure
The following are positions that appear in EA close processes and should not be accepted regardless of the pressure to sign:
| Proposed Term |
Why to Refuse |
Alternative Position |
| "Price sheet finalised — take it or leave it" |
Price sheets always have errors. An error discovered after signature is your cost, not Microsoft's. |
Require 3–5 business days to verify all line items before signing. Non-negotiable. |
| "This offer expires at end of quarter" |
Microsoft offers rarely expire as described. The commercial position rarely changes by 24–48 hours. |
Accept the timeline for close but not the pressure to sign without completing your checklist. |
| Verbal amendment commitments only |
Verbal commitments have zero enforceability. Account executives who commit verbally and cannot confirm in writing may not have authority for what they offered. |
Any commitment not in writing is a commitment that does not exist. Period. |
| Signing before legal review of MBSA amendments |
The MBSA governs audit rights, liability limits, and termination — the most commercially consequential clauses in the relationship. These warrant legal review. |
MBSA review is a fixed prerequisite. Build it into the timeline, not as a post-signature action item. |
| "We can sort the VLSC setup after you sign" |
VLSC setup problems after signature create deployment delays and SA forfeiture. All VLSC administrator accounts should be verified before signature. |
VLSC administrator configuration confirmed as a pre-signature condition. |
The Independent Advisor Role at Close
The final 30 days is the period in which an independent advisor typically delivers the highest concentration of value in an EA engagement. The advisor role at close is specific: verify the price sheet against negotiated positions, identify documentation gaps, confirm amendment language against the agreed scope, and provide an independent view on whether the commercial outcome meets the objectives set at the start of the negotiation.
This is distinct from the negotiation support role earlier in the process. By the close phase, the commercial parameters are largely set. The value at close is verification, documentation, and preventing the administrative errors that erode 5–10% of negotiated value. A four-to-six-hour final review engagement focused on the 28 checklist items above typically returns five to ten times its cost in identified issues.
See our guide to independent vs. aligned advisors for why the distinction between independent and partner-aligned advisors matters most during the close phase, when commercial interests can diverge from yours most sharply.
The Microsoft Licensing Insider
Weekly intelligence on EA negotiation tactics, pricing changes, and licensing developments. Trusted by 4,000+ enterprise IT and procurement leaders.
Frequently Asked Questions
How long should the final EA review process take?
For a standard EA renewal without complex amendments, allow five to seven business days for price sheet verification, documentation review, legal review of amendments, and internal approval. For complex EAs with significant Deal Desk-approved terms or multi-entity structures, allow ten to fifteen business days. Any close timeline that does not accommodate this review period is a timeline set in Microsoft's interest, not yours.
What happens if we find a price sheet error after signing?
Errors discovered post-signature are governed by the standard EA contract terms. Microsoft's standard position is that the signed price sheet is correct as agreed. Remediation requires a formal amendment process — which Microsoft has no commercial incentive to expedite — and often results in a negotiation over whether the error is credited, corrected prospectively, or disputed. Prevention through pre-signature verification is the only reliable approach. We have not seen a single post-signature price sheet error that Microsoft volunteered to correct without significant commercial pressure from the customer.
Can we reopen negotiation on specific items in the final 30 days?
Yes, though the scope of what is achievable narrows significantly as you approach signature. Items that involve pricing changes require AE or Deal Desk approval and may require re-submission to Microsoft's approval process. Contract term amendments — particularly those involving MBSA modifications — require legal review on both sides. The most productive final-30-day reopen items are: price sheet corrections (errors, not negotiated improvements), amendment provisions that were agreed in principle but not yet documented, and VLSC configuration items. Attempting to reopen fundamental pricing positions in the final 30 days is rarely productive and can damage the account team relationship without improving commercial outcomes.
Should we have legal counsel review the full EA at close?
For EAs above £500K total value, or where non-standard amendments have been negotiated, yes. Legal review should focus specifically on the MBSA (audit rights, liability, termination), the amendment provisions (enforceability of non-standard terms, clarity of language), and any data processing addendum provisions. Legal review of the standard Enrolment Agreement and Price Sheet typically adds less value — these are standardised Microsoft documents — but the MBSA and amendments are where consequential terms live. Engage counsel with specific Microsoft licensing contract experience rather than general commercial counsel unfamiliar with Microsoft's licensing construct.
Want an expert to run through this checklist with you?
Our advisors have completed final reviews on EAs from £200K to £80M. We typically complete the review in three to five business days and identify issues that organisations consistently miss under deadline pressure. The engagement pays for itself in the first item we find.
Book My Free Proposal Review →
See Client Results
Related EA Negotiation Resources