Microsoft EA Negotiation Checklist: Pre-Negotiation Readiness

Microsoft EA Negotiation Checklist: Pre-Negotiation Readiness

Introduction: Why a Pre-Negotiation Checklist Matters

Negotiating a Microsoft Enterprise Agreement (EA) is a high-stakes endeavor. These multi-year deals encompass hundreds or thousands of licenses and services, featuring complex terms and pricing that can significantly impact IT budgets.

Microsoft’s product landscape and contract language are notoriously intricate – missing even one preparation step could cost your company millions in unnecessary spend or unfavorable terms. Read our overview of Microsoft EA Negotiation preparations.

Going into an EA renewal unprepared is not an option. A pre-negotiation readiness checklist ensures your team enters discussions with clear data, aligned goals, and strategic leverage, rather than entering discussions with blind spots.

By completing each step of preparation before you sit at the table, you shift the power balance in your favor. With every critical element checked off in advance, you’ll be negotiating from a position of strength, not scrambling to react to Microsoft’s agenda.

1. Stakeholder Alignment

The first step is to rally and align your internal stakeholders. Microsoft’s sales team is adept at finding and exploiting internal misalignment, so you need a united front.

Identify an executive sponsor, typically a CIO or CFO, who will champion the negotiation and provide top-level support. Also, assemble a cross-functional core team involving procurement, IT, finance, and legal.

Everyone must share a unified vision of what a “good deal” means for your organization before talks begin.

Key stakeholders to involve:

• Executive Sponsor (CIO or CFO): Provides high-level backing and can make final decisions or approvals.
• Procurement Lead: Coordinates negotiation strategy and vendor communications to keep everyone aligned.
• IT Lead: Provides technical insights and usage data to ensure the deal meets actual technology needs.
• Finance Manager: Sets budget parameters and evaluates cost implications of any proposal.
• Legal Counsel: Reviews contract terms and flags risks in the fine print (especially important for compliance and term protections).

Once the team is in place, define your negotiation priorities together. What is your primary objective in this renewal – aggressive cost reduction, more flexibility for cloud services, improved contract terms to mitigate risk, or some mix of these? Document and agree on these priorities upfront.

For example, one priority might be cost savings (e.g., targeting a 15% lower total cost than your last EA). At the same time, another is flexibility (e.g., the ability to scale down users or switch to cloud services without incurring penalties).

Clarity here prevents internal disagreements later. If one department prioritizes adding new Microsoft features and another focuses on budget, you need to reconcile this now so that Microsoft hears a consistent message during negotiations.

Alignment also means setting clear limits. Agree on your “walk-away” points before negotiations start – in other words, the deal breakers. This could be a maximum total cost you’re willing to accept or non-negotiable terms (for instance, we will walk away if Microsoft won’t grant a cap on price increases).

Knowing your walk-away threshold keeps the team disciplined if Microsoft pushes you toward an unfavorable deal.

Similarly, establish an internal escalation path. Decide how the team will handle it if the negotiation stalls or if Microsoft tries end-running your team by appealing to a higher executive.

For example, your procurement lead might handle day-to-day discussions, but if Microsoft escalates to your CEO with pressure to sign, your designated executive sponsor (CIO/CFO) should be prepared to step in with full context and support the negotiation strategy.

This prevents the vendor from using divide-and-conquer tactics to undermine your position.

Stakeholder Alignment Checklist:

• The executive sponsor was identified, and all key stakeholders were aligned on goals
• Negotiation priorities (cost, flexibility, risk mitigation, etc.)are documented and agreed upon.
• Walk-away limits and an internal escalation plan have been established.

Read more, Microsoft EA Negotiation Team: Building the Right Cross-Functional Strategy.

2. Data Gathering

Before you even mention the word “renewal” to Microsoft, gather all relevant data about your current licensing and usage. Hard facts and figures are your greatest ally – they dispel vendor spin and arm you with evidence for every ask.

Begin by creating a detailed license inventory, documenting every Microsoft product, subscription, and entitlement your organization currently holds. Include purchase records from your last EA (and any mid-term additions) and note the quantities and license types. Dig up your EA True-Up reports from each year of the expiring agreement; these show how your license count evolved and reveal any over- or under-utilization patterns.

Next, map this inventory against actual usage. Usage data helps identify shelfware – licenses you pay for but aren’t actively using. For each major product (Office 365, Dynamics, Windows, Azure services, etc.), determine how many users or workloads are truly active. If you have 2,000 Office 365 E3 licenses allocated but only 1,600 active users, that’s 400 licenses of potential savings or reallocation.

Similarly, check for unused Azure credits or underused cloud services. Usage analytics from admin portals or internal monitoring tools are critical evidence when you negotiate to remove or downsize certain line items. Microsoft will be less able to push unwanted products if you can show data that you aren’t using them.

On the flip side, identify if you are under-licensed anywhere (for example, more SQL Server installations than you have licenses for) – you’ll want to know that better than Microsoft does and have a plan, rather than being caught in a compliance bind.

Another piece of the puzzle is your current spend baseline.

Tally up everything you currently pay Microsoft in a year, not just the EA itself. This includes your annual EA payments, any à la carte or additional licenses purchased outside the EA, cloud consumption spend (e.g., Azure pay-as-you-go or other subscriptions), and support costs, such as Microsoft Unified Support.

Having a 360° view of your Microsoft-related spending allows you to evaluate any Microsoft offer holistically. For instance, Microsoft might propose a discount on licenses but plan an increase in Unified Support fees – you want to see the net effect on your total spend.

Also, gather data on your support usage and performance. If you’re on Microsoft’s Unified Support plan (or a Premier Support legacy plan), pull records of how many support tickets your organization opened, of what severity, and how responsive Microsoft was. This will inform your stance on support renewal and whether you might negotiate that separately or consider alternatives.

Every data point you collect now can become a leverage point later. If your data indicates low support usage, you may consider advocating for a lower support cost. If it shows high growth in Azure consumption, you may want to request additional cloud credits or price locks.

To organize this effort, assign owners to your team for each data area and set deadlines for collecting the data.

Often, data is scattered – some in procurement files, some in IT asset tools, some in the Microsoft Admin Center. The process may take several weeks, so it’s best to start early. The table below outlines key data categories to compile:

Collecting this data is a significant undertaking, but it lays the foundation for a fact-based negotiation. When Microsoft’s offer arrives, you will have your own numbers to compare against their claims.

You’ll know exactly what you have, what you use, and what it costs – leaving little room for Microsoft to inflate your needs or hide upsells in fine print.

(No checklist box for this section, since the entire section itself is a data checklist.)

3. Market Research

Internal data is only half the equation; the other half is understanding the market and Microsoft’s current tactics. Before you engage with Microsoft’s reps, do your homework on external benchmarks and industry trends. Knowing what deals similar companies are getting arms you with realistic targets and exposes any bluff if Microsoft claims an ask is “unheard of.”

For example, find out the typical discount percentages organizations of your size and industry have secured on Enterprise Agreements. If peers in your industry are getting 20% off their Microsoft 365 E5 licenses, you should be aware of this baseline.

You can gather benchmarks through informal networking (e.g. industry user groups or peers), or by engaging independent licensing advisors who see many deals. Even publicly available case studies or webinars might drop clues about discount ranges or special terms others achieved.

Stay up-to-date on Microsoft’s own licensing changes and announcements as well. Microsoft frequently adjusts its pricing and program rules – you need to incorporate any impending changes into your strategy.

As of 2025, for instance, Microsoft has been eliminating volume-based discount tiers for online services in Enterprise Agreements.

This means you can no longer rely solely on having a larger user count to automatically secure a better price tier; instead, discounts will be based more on your commitment and the specific products you bundle.

Such changes could significantly impact your negotiation: if volume discounts are gone, you’ll focus more on commitment-based discounts or seek alternative avenues (like CSP pricing) for savings.

Likewise, note any announced list price increases for products you use. Microsoft often telegraphs price hikes (e.g., a 10% increase on certain Microsoft 365 plans, or rising Azure unit costs). If you know these are coming, you might consider pushing to execute your renewal before they take effect, or demand price protections.

Another angle is to research alternative licensing routes that companies are exploring. Microsoft now offers the Microsoft Customer Agreement (MCA) and Cloud Solution Provider (CSP) programs as alternatives or supplements to an EA. Understand how competitors or other organizations are leveraging these.

For example, mid-sized enterprises with a certain number of seats might forgo an EA and use CSP resellers for greater flexibility.

Some large enterprises adopt a hybrid approach: keeping an EA for core products but buying additional Azure services through an MCA to gain monthly flexibility and avoid true-up constraints.

The more you know about these trends, the more credible your threats and choices become. Telling Microsoft “we’re evaluating moving our Azure workload to an MCA for monthly flexibility” is a concrete leverage point if it’s based on real moves others have made.

Finally, assess Microsoft’s broader strategic pushes in the market. Are they heavily promoting a new product (like Power Platform, security bundles, or AI add-ons like Copilot)? If so, there may be promotional deals or additional discounts available if you show interest.

Conversely, if a product is being phased out or replaced, you’ll want to avoid being stuck with it. Market research will reveal these insights.

Market Research Checklist:

• External pricing benchmarks gathered (industry discount percentages, peer contract insights)
• Microsoft licensing changes and upcoming price increases noted (e.g., removal of discount tiers, new product packages)
• Alternative program options (MCA, CSP, or hybrid licensing trends) were reviewed for leverage

4. Risk Review

Before finalizing what you’ll ask for, take a hard look at your risks – both licensing compliance risks and contract term risks. Microsoft negotiations aren’t just about dollars; if you overlook a risk area, it can cost you dearly later or weaken your negotiation stance.

Start with a compliance gap analysis. Review where you might be out of compliance with your current licenses. Common trouble spots include Microsoft SQL Server, Windows Server CALs, and indirect usage scenarios (such as a third-party app accessing a Microsoft system indirectly, which may require a license). If you suspect any shortfall – for example, database servers deployed without proper licenses or users with access who aren’t licensed – document that now.

You have a choice: remediate it before the EA (by purchasing the necessary licenses in a true-up or via cleanup) or plan to address it in the new agreement. Importantly, you don’t want Microsoft to be the one to point out a compliance issue during negotiations or, worse, in an audit – that puts you on the back foot.

Knowing your own gaps means you can either quietly resolve them or at least anticipate Microsoft’s moves. Keep in mind that Microsoft often conducts Software Asset Management engagements or full audits around renewal time; being proactive can help reduce this risk.

Next, scrutinize your current contract and upcoming renewal for contractual pitfalls. Enterprise Agreements have clauses that can bite you if not managed. One example is auto-renewal. Does your EA automatically renew for a year if you don’t give notice? Many companies have been caught off guard by auto-renewals, losing the opportunity to renegotiate and instead being stuck with the same terms for another year. Mark your calendar well in advance if a notice is required to prevent auto-renewal, or negotiate to remove or modify that clause in the new contract if possible.

Another contractual area to review is downgrade rights and license entitlements. If you plan to downgrade some users from Office 365 E5 to E3, are there provisions in place that allow you to use older versions or lower editions?

Similarly, if you have on-premises software with Software Assurance, confirm what rights you have to older versions or to transition to cloud services. Microsoft sometimes narrows these rights over time, so you may need to insist on keeping certain privileges.

Consider scenarios that pose risks under the current terms. What if you need to significantly reduce the number of users (as in a divestiture or downsizing)? In a standard EA, you generally cannot reduce your baseline count until the agreement term ends – this rigidity is a risk if your headcount drops.

Mitigation might be negotiating a one-time flexibility clause or at least planning your quantities conservatively. What if Microsoft raises prices on a product mid-term or at renewal?

Ensure you have price protection terms: ideally, your EA locks pricing for the term, and you negotiate caps on any renewal increase (for instance, no more than X% increase on core products). What if your company is acquired or split? You’d want clauses that allow transferring or splitting licenses without penalty.

Establish your red lines based on this risk review – these are terms you absolutely need or absolutely cannot accept. For example, a red line could be “No agreement to any automatic price uplift year-over-year – any increases must be negotiated or capped.” Another might be “Must include clause allowing license transfer in event of merger or divestiture.”

If Microsoft’s standard contract omits these, you plan to insert them.

Conversely, a red line could be refusing any language that would prevent you from using existing versions (e.g., you won’t accept a cloud contract that forces immediate upgrades and retires older version rights you still need).

Knowing these non-negotiables in advance helps you focus your negotiation on more than just price – you’re also negotiating the terms that protect you.

To organize, consider a risk register or table to track each risk, its impact, and how you plan to address it in negotiation:

This kind of risk review ensures you’re not only chasing savings but also closing loopholes that Microsoft could exploit later.

Bring these concerns into the negotiation: Microsoft won’t volunteer to fix these issues, but they often will agree if you ask, especially if it’s important to closing the deal. An EA that saves money upfront but contains hidden risks is not a good deal in the long run; therefore, make risk mitigation a core part of your checklist.

(No separate checklist box for this section; the table above and discussion serve as the risk checklist.)

5. Negotiation Materials

With stakeholders aligned, data in hand, research done, and risks understood, the next step is to prepare your negotiation arsenal. This includes all the materials and plans you’ll use to execute a successful negotiation.

First, build a detailed financial model for the renewal. This model should project your costs under multiple scenarios: for instance, (a) if you simply renew the EA as-is with Microsoft’s initial pricing, (b) if you optimize by removing shelfware or downgrading certain licenses, (c) if you migrate some services to alternative licensing like CSP or third-party solutions, and (d) your best-case negotiated outcome with target discounts. Include three-year or five-year total cost of ownership comparisons to illustrate the long-term implications.

The financial model helps you identify your limits and priorities in dollar terms. It will quickly reveal the value of each negotiation concession. For example, how much do you save if Microsoft agrees to a 5% bigger discount, or if you cut 200 unused licenses?

Knowing this helps you quantify your asks (“This clause is worth $500K to us over three years, Microsoft, so we need something of equal value in return”). Don’t forget to factor in things beyond license fees, such as support costs or potential cloud overage fees-the goal is an apples-to-apples comparison of all options.

Next, prepare a negotiation playbook or plan. This is an internal document (or slide deck) that outlines your tactics, primary asks, and fallback positions. List out all the concessions and terms you intend to request from Microsoft, ranked by priority.

Typical “asks” might include: a larger discount on key products, flexible payment terms (e.g., annual payments instead of upfront), the inclusion of certain free training or consulting days, an adjustment to a contract term you flagged in the risk review (like adding a clause for merger flexibility or price cap), etc.

Be specific in your asks – for example, not just “we want a discount,” but “we want a 20% discount on Office 365 E5 licenses and price lock for the 3-year term.” Alongside each ask, note your ideal outcome and your fallback.

Perhaps you aim for 20% off, but will settle for 15% if other aspects of the deal are sweetened. Or you prefer a 3-year term but could accept a 4-year term if it comes with fixed pricing. Having these decisions made in advance prevents knee-jerk reactions under pressure.

Your playbook should also script how you plan to conduct the negotiation meetings. Decide on roles: who will lead discussions, who will cover which topics, and who will take notes.

Anticipate Microsoft’s likely tactics and questions. For instance, if you’re asking for a big discount, Microsoft will ask for a larger upfront commitment or addition of new products – plan how you will counter or what you might offer in exchange (maybe you’re willing to consider adding a product if the price is right, but only if it’s genuinely needed per your earlier priorities). Essentially, rehearse the negotiation within your team: “If Microsoft does X, we will respond with Y.” This preparation means fewer surprises.

Don’t neglect the governance process on your side. Identify who ultimately must approve the deal and at what stages of the process. Nothing is worse than reaching a verbal agreement only to have your CFO or legal say they need two more weeks or have issues with terms. To avoid this, loop in the approvers early.

For example, ensure your finance leader signs off on the budget envelope, and your legal counsel reviews any non-standard terms before you give final acceptance to Microsoft.

Plan the timeline for internal approvals so that when Microsoft sends the final paperwork, you can turn it around promptly, or at least you know exactly how long you need. This will also allow you to use time as a tactic.

Suppose you know your board meeting for approval is on a certain date. In that case, you can manage Microsoft’s expectations and counter any “you must sign by X date” pressure with “we have an approval meeting scheduled on Y date and can sign immediately after if terms are acceptable.”

It’s often valuable at this stage to consult external experts or advisors. An independent Microsoft licensing expert or negotiation consultant can provide a fresh perspective and validate your strategy.

They might spot a missing piece in your plan or suggest an additional concession to pursue (for instance, they might know Microsoft has a promotion for Azure credits if you commit to Windows 11 Enterprise – something you hadn’t considered).

If you use such experts, involve them in reviewing your license inventory analysis, your financial model assumptions, and your contract terms wish list.

However, be cautious to maintain control; external advisors should support your goals, not steer you into a cookie-cutter approach. Use their knowledge to double-check that you haven’t missed anything and to role-play negotiation scenarios.

Negotiation Materials Checklist:

• Comprehensive financial model prepared (EA renewal vs. optimization vs. alternatives cost scenarios)
• Internal negotiation plan/playbook drafted, including prioritized asks and fallback positions
• Internal approval process mapped (who approves what, and timeline for sign-offs)
• External licensing advisor or expert consulted for review (if applicable)

6. Timeline & Internal Readiness

Timing can make or break your negotiation leverage, so build a detailed timeline that aligns with your EA expiration and internal decision-making cadence.

Work backwards from the EA end date to set key milestones.

For a major EA renewal, starting preparations 6–12 months in advance is common (with larger enterprises often closer to a year out). This lead time is crucial: it gives you space to gather data, conduct the internal alignment and approvals we discussed, and engage with Microsoft without last-minute panic.

Map out when you ideally want to receive your initial proposal from Microsoft, when counteroffers should be exchanged, and a target date to finalize the terms. Include internal deadlines, such as “Complete data gathering by X date,” “Executive sponsor review of negotiation plan by Y date,” and “Final management approval by Z date.”

Ensure you allocate sufficient buffer time for potential delays and contingencies. Microsoft’s sales cycle often coincides with quarter-end or fiscal year-end pushes, which can work to your advantage if you time it right, but it can also create crunches.

Built into Slack: for example, aim to finish negotiations a month before your drop-dead date, so if Microsoft drags their feet or an unexpected issue arises, you aren’t forced into an extension or a poor deal under duress.

It’s not uncommon for Microsoft to stall on giving its best offer until late in the cycle – if you have time, you can afford to wait them out. Internally, also consider that your key approvers or lawyers may be unavailable at times (e.g., vacations, quarter-end busy periods for finance). Scheduling buffer ensures that a key person’s unavailability doesn’t derail the timeline.

Another important aspect is preparing for pressure tactics as the clock ticks down. Microsoft is known to employ tactics such as setting artificial deadlines (“This discount is only valid if you sign by next week”) or escalating the negotiation to higher-level executives on both sides.

Have a plan for how to respond. For example, if Microsoft says the deal expires at the end of the quarter, be willing to let it roll past that date if the terms aren’t right – often the deal (or better) will still be there after, because their urgency is real, but so is your resolve.

If you receive an email from a Microsoft VP to your CEO, implying urgency, ensure your executive sponsor is prepared to respond or support the negotiating team’s stance.

The goal is to control the pace of the negotiation. Use your timeline to project calm confidence: you know when a decision truly must be made on your side, and you won’t be rushed into a subpar agreement just to meet Microsoft’s sales timeline.

Additionally, line up your internal communication and escalation plan. Keep executives updated at key milestones so there are no surprises. Suppose negotiations reach a stalemate on a major issue (say, pricing or a contract term).

In that case, you should know in advance which internal meeting or which executive discussion will resolve your position. For instance, if Microsoft won’t budge on a 10% price hike, will your CFO accept it or approve an alternative plan (like dropping a product)?

Discuss these what-ifs internally ahead of time and note who has the final say. That way, if high-pressure tactics come into play, your team can respond swiftly because you’ve already gamed it out.

Timeline & Readiness Checklist:

• Negotiation timeline created and aligned with EA expiration (including key milestones and a buffer before the deadline)
• Internal review and approval steps scheduled (no last-minute surprises with legal or C-suite sign-off)
• Plan in place for vendor pressure tactics (team knows how to respond to deadline pressure or executive escalations)

Read more about our Microsoft EA Negotiation Service.

Would you like to learn more about our Microsoft EA negotiation services?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit