Microsoft EA Negotiation Preparation: 12–18 Month Game Plan

Microsoft EA Negotiation Preparation: 12–18 Month Game Plan

Introduction – Why Early Preparation Matters

Microsoft Enterprise Agreements (EAs) are high-stakes, high-cost contracts that can lock in your IT spend and capabilities for years.

Yet many organizations make the mistake of starting the renewal process too late, often scrambling in the final weeks.

The result? Leaving money on the table in the form of higher prices or unfavorable terms. Early preparation isn’t just helpful – it’s critical leverage.

Remember that Microsoft’s sales teams operate year-round.

They begin strategizing your renewal well in advance, aiming to upsell and secure commitments before you’ve even started planning. If you only begin serious preparations in the last 2–3 months, you’re essentially negotiating on Microsoft’s terms under intense time pressure.

In contrast, starting 12–18 months before your EA expiration puts you in control.

This long runway allows you to gather detailed usage data, align internally on goals, and methodically plan your approach without last-minute panic.

In this guide, we outline a 12–18 month game plan for Microsoft EA negotiations, covering early engagement steps, team setup, self-assessment, objective setting, timeline development, and checklists.

The tone is practical and strategic, with a healthy dose of skepticism toward Microsoft’s sales tactics. The goal is to empower CIOs, IT procurement leads, and finance executives to negotiate on their terms and achieve the best outcome for the business.

Start Early: 12–18 Months Before Renewal

Beginning your EA renewal planning a full year (or more) in advance is essential.

Microsoft will often engage you long before the expiry date, sometimes subtly by discussing future needs, and sometimes directly with early renewal offers.

There are several reasons why this early start is critical to your success:

• Avoid last-minute pressure: When you have ample lead time, you aren’t forced into accepting suboptimal terms just to meet a looming deadline. Microsoft can’t use the ticking clock against you if you’ve started well ahead of time.
• Thorough data gathering: A 12–18 month head start gives you time to conduct a detailed internal audit of your licenses and usage. You can identify where you’re overspending (and where you might need more), without rushing. This data becomes a powerful tool in negotiations.
• Internal alignment: Early preparation allows IT, procurement, finance, and executives to get on the same page. You can debate priorities and decide your must-haves long before Microsoft is at the table. By the time negotiations begin, your team presents a united front with clear goals.
• Leverage over Microsoft: Microsoft’s fiscal calendar and sales quotas mean they’re always looking to close renewals by certain quarter-ends. When you start early, you control the timeline. You can engage with Microsoft at the optimal moments (for example, when they might be more inclined to offer discounts) rather than scrambling to react to their schedule.

To illustrate the value of an early start, consider a high-level timeline for an EA renewal planned 18 months out. This timeline breaks the process into phases with key milestones:

This 18-month EA preparation timeline ensures no phase is rushed.

By the time you reach the last 90 days, most of the heavy lifting is done – you’re fine-tuning the deal, not scrambling to start planning.

Early engagement also lets you take advantage of any Microsoft fiscal-year incentives (for instance, if Microsoft’s year-end is approaching, they may offer better terms if you’re ready to sign, but you choose if the terms are right, not because time runs out).

Assemble Your Negotiation Team

A successful EA negotiation requires input from multiple corners of the organization. Assemble a cross-functional team 12–18 months before renewal, so everyone understands the plan and their role.

Key players on this team should include:

• IT and Software Asset Management: Your IT department (and any Software Asset Management specialists) will gather data on current license usage. They understand what software and cloud services are deployed, how many users actually use each product, and the technical requirements for the future. Their data is the foundation of your negotiation.
• Procurement/Purchasing: The procurement lead or sourcing manager will drive the commercial negotiation. They focus on pricing, discounts, and contract terms. They’ll coordinate communication with Microsoft’s sales reps or the reseller, and ensure that the negotiation strategy aligns with procurement best practices (like competitive bidding or benchmarking).
• Finance: A representative from Finance should be involved to establish budgetary guardrails and assess the financial implications of various deal scenarios. They will help determine what the organization can afford, validate cost reduction targets, and ensure that any long-term commitments are financially sound. Finance can also model the ROI of new products or the cost of not renewing certain components.
• Legal: Because an EA is a complex contract, consider having a legal advisor or counsel review the terms. Legal will ensure you address critical clauses (such as liability, data privacy, or the ability to reduce license counts mid-term). They also help draft or review any special amendments you negotiate, making sure Microsoft’s contract language matches the agreed-upon terms.
• Executive Sponsor: Assign a senior executive sponsor, typically the CIO, CTO, or CFO. This person isn’t in the day-to-day weeds of the negotiation, but they provide direction and support. Their role is to align the EA renewal with the broader business strategy and to step in when needed (for example, joining a high-stakes meeting with Microsoft to demonstrate to the vendor that your company is serious about certain demands). Executive backing also helps keep internal teams accountable and unified.

Many enterprises also choose to bring in an external advisor or licensing expert. An outside consultant who specializes in Microsoft licensing and negotiations can offer insights on Microsoft’s tactics, industry benchmarks, and “gotchas” to watch out for.

They can conduct a licensing optimization analysis and help formulate negotiation strategies that have worked for other companies.

While optional, this external perspective can be valuable, especially if your team hasn’t negotiated an EA recently or if you lack detailed licensing expertise in-house.

EA Team Setup Checklist:

• Cross-functional team appointed: All key roles (IT, procurement, finance, legal, executive sponsor) are identified and have agreed to participate.
• Roles & responsibilities defined: Each team member knows their duties. For example, IT will deliver the usage data by a certain date; legal will review all proposals for potentially risky language; and the executive sponsor will receive briefings at key milestones.
• Executive alignment secured: Top leadership is on board with the negotiation goals and timeline. There’s a clear mandate from the CIO/CFO that cost savings or other objectives are expected, which empowers the team to push back on Microsoft’s demands.

With the right team in place, you avoid the common pitfall of one department driving the renewal in a silo. A unified team ensures that all aspects are covered – including technical needs, financial constraints, contractual risks, and strategic business objectives.

Assess Current State

Before considering what to ask of Microsoft, conduct a thorough self-audit of your current EA. This assessment of your “current state” will reveal how well you’re using what you’re paying for and where you have leverage to negotiate.

Key steps include:

• Inventory your licenses and usage: Work with IT to document every product and service under your EA, and how many licenses of each you have. Then determine actual usage levels for each. For software, that might mean tracking active users, login counts, or server installations. For cloud services (such as Azure or Microsoft 365), check the admin portals or reports for consumption data. The goal is to identify gaps between what you’re entitled to and what’s actually being used.
• Identify shelfware and over-licensing: Shelfware refers to licenses you’ve paid for but aren’t using at all. Almost every organization finds some unused licenses – for example, 500 Visio licenses purchased for a department that only uses 100, or Office 365 E5 subscriptions given to employees who only use E3-level features. Highlight these as targets to eliminate or reduce at renewal. Over-licensing may also manifest as purchasing higher-tier products that aren’t fully utilized. This is wasted spend that gives you negotiating power (you can threaten to drop them if Microsoft doesn’t offer concessions).
• Spot under-utilization or shortfalls: On the flip side, see if there are areas where you might be under-licensed or under-utilizing features you pay for. Under-licensing (using more than you bought) is a compliance risk – if any exist, you’ll want to address them proactively to avoid a surprise audit penalty. Under-utilization means you have capabilities you’re not even leveraging – for instance, you have Microsoft 365 E5 security features available, but your IT hasn’t deployed them. That’s not directly costing extra, but it’s a value you’re not realizing. Recognizing these areas might shape your objectives (e.g,. you might decide to actually roll out a feature widely to justify its cost, or downgrade if you won’t use it).
• Review past true-ups and audits: Look at your last few annual true-up reports (the yearly adjustment where you inform Microsoft of any increases in usage). Were there big increases in certain license counts? That could indicate unplanned growth that you need to budget for this time. Also, consider any Microsoft audit activity in the past. If Microsoft’s compliance team has audited you, you know where the pain points were. Being prepared on compliance strengthens your position (you can confidently say you know your deployment, which makes Microsoft’s “compliance scare” tactics less effective).
• Prepare a baseline usage and spending report: Summarize all the data into a clear and concise baseline document. For example, “We have 1,000 Office 365 E3 licenses, of which 950 are assigned and 800 are actively used monthly. We have 200 Office 365 E5 licenses, but only 50 users are utilizing E5-only features, such as advanced analytics – indicating a possible downsizing opportunity. We spent $X last year on the EA, with these components…”. This baseline provides a factual foundation for planning. It also becomes evidence during negotiations – if Microsoft’s proposal includes 1,000 E5 licenses, but you know only 50 people truly need E5, you have the hard data to counter that part of the offer.

By assessing your current state early (again, ideally completing this no later than 9 months before renewal), you turn vague debates into concrete discussions.

Instead of arguing in the abstract whether a license is needed, you’ll have numbers: “Product Y is 20% of our EA cost, but only 5% of our users rely on it – we intend to cut or replace it.” Microsoft’s team will realize you’ve done your homework, immediately improving your credibility at the negotiation table.

Set Objectives & Budget

With your baseline in hand, the next step is to define what a successful EA renewal looks like for your organization. Too often, companies go into negotiation with the sole aim of “paying less” but without clarity on priorities or limits.

Setting clear objectives and budget parameters 9–12 months out provides direction for both your team and signals to Microsoft what you value (and what you won’t compromise on).

Start by asking: What are our top priorities for this renewal? Common objectives include:

• Cost reduction: Perhaps your CIO or CFO has made it clear that this renewal must deliver savings. Define a target, e.g., reduce total EA spend by 10% or at least stay flat year-over-year despite adding new users. Having a quantifiable savings goal helps evaluate any Microsoft offer – does it meet our target for reduction or not?
• Optimizing license mix: Your usage audit may reveal opportunities to downgrade or remove certain licenses. An objective could be to increase efficiency by eliminating shelfware and right-sizing every user’s license. For example, migrate 300 users from E5 to E3 if they don’t need advanced features. This ties into cost reduction but focuses on efficiency rather than simply cutting for the sake of cutting.
• Adding new capabilities (within budget): Perhaps the business does want to adopt new Microsoft products – such as Power BI, Dynamics 365, or new AI/collaboration tools – but in a cost-effective manner. An objective could be to expand into XYZ service without exceeding the current budget or to secure promotional pricing for the new product ABC. This ensures that if you agree to spend more in one area, it’s deliberate and possibly offset by savings elsewhere.
• More flexibility: You might have felt locked in with the last EA. Objectives could include reducing license counts after year 1 or 2 (some EAs allow a one-time downward adjustment), or securing better terms for true-ups (such as fixed pricing for added licenses), or longer price protections if Microsoft is known to increase prices. Essentially, define any contract terms that are must-haves, such as a price cap on certain products, an exit clause for a particular service, or adding a clause for transferability or cloud migration rights.

Once your objectives are defined, align them with executive priorities.

For instance, if the company’s strategy is “cloud-first,” then adding Azure credits or certain cloud services might outweigh a strict cost-cutting goal – make sure the CIO/CTO prioritizes that appropriately. If the business is in a belt-tightening mode, then cost savings will take precedence over adding fancy new features.

This alignment is crucial: it prevents internal conflict later. There’s nothing worse than negotiating hard for a cost reduction, only for a business unit leader to later insist on adding a costly product that wasn’t originally planned. Get those decisions made early.

Additionally, establish your budget guardrails and walk-away options:

• Max budget tolerance: Work with Finance to determine the maximum you’re willing to spend on this EA. Microsoft will, of course, push for more, especially if it wants you to upgrade to higher-tier products. Know your ceiling if Microsoft’s proposals keep you under that ceiling (and meet other objectives), great. If they insist on something that breaks the budget, that’s when you consider dropping the scope or walking away.
• Must-have terms: List the terms or concessions you absolutely need. This could be a specific discount percentage, the inclusion of a particular product, or contract flexibilities as mentioned. These are your non-negotiables. If these aren’t met, you won’t sign – Microsoft’s team needs to eventually understand that.
• Walk-away alternatives: Plan out what you’ll do if negotiations stalemate or if Microsoft won’t meet your critical needs. This is essentially your BATNA (Best Alternative to a Negotiated Agreement). Examples: If the EA renewal is too expensive, you may consider extending the current agreement for 6 months (Microsoft sometimes allows a short extension, although it is usually at list prices – but it buys time). Or maybe you’ll move a subset of users to month-to-month subscriptions via a Cloud Solution Provider (CSP) instead of committing to a three-year EA, as a stopgap. In extreme cases, an alternative could be migrating some workloads from Microsoft to another vendor (for example, shifting certain services to Google Workspace or AWS for specific users) – even if you prefer not to. Having that analysis done means you could pivot if necessary. The point is to never feel like you have “no choice” but to accept a bad deal. If you have a viable Plan B (even if it’s temporary), you can negotiate with far more confidence.

By setting objectives and limits well ahead of formal negotiations, you essentially create a playbook for yourself. Share this information internally (especially with your executive sponsor) so that everyone agrees.

This prevents internal stakeholders from derailing the process later by introducing new goals or caving in too easily.

When Microsoft’s sales team comes back with their grand proposals, you’ll have a clear yardstick to measure against: Does this proposal achieve what we set out to do? If not, you have the rationale to push back and the unity to hold firm.

Build the Negotiation Timeline

To execute a successful negotiation, it’s not enough to start early – you also need a structured plan for how the negotiation will unfold over time.

Building an EA negotiation timeline involves breaking the process into clear phases and assigning tasks and deadlines to each phase.

This keeps your team on track and ensures Microsoft is engaged at the moments that maximize your leverage. Below is how you can structure the timeline (assuming you’ve started about a year out, adjust if you have 18 months):

• Internal preparation (12–9 months before renewal): This phase focuses on getting your affairs in order. It includes forming the negotiation team (if you haven’t already at 12+ months out), completing the current state assessment, and agreeing on objectives and budget (all the work we described in earlier sections). By the end of this phase, ideally around 9 months out, you should have all your data collected, a clear negotiation strategy, and executive buy-in. Essentially, you’re preparing an internal negotiation playbook. Also, ensure that you document an initial engagement checklist for when you first speak with Microsoft – e.g., have your baseline usage report ready, know your must-have list, and obtain internal approval on what you can propose or concede early. This preparation phase often goes unnoticed by Microsoft, but it’s where your leverage is born.
• Initial Microsoft engagement (9–6 months before renewal): Now it’s time to put out feelers to Microsoft – on your terms. Approximately 6 to 9 months before the renewal, contact your Microsoft account manager or reseller representative to inform them of your upcoming renewal plans. You don’t need to reveal your whole strategy; in fact, be cautious and strategic in what you share. The goal in this phase is to gather information and set the tone. Request an initial quote or a proposal from Microsoft. This early quote will not be their best offer (often, it’s quite high or loaded with upsells). Still, it gives you a baseline and insight into their approach (for example, if they immediately push everyone to E5 licenses, you know what their agenda is). Meanwhile, continue exploring alternatives: maybe issue a request for proposal to a few Microsoft resellers to see if they can offer better pricing, or get a quote for a different licensing program like a Microsoft Customer Agreement (MCA) or CSP. Microsoft will realize you’re shopping around, which is good – it puts competitive pressure on them. In this phase, you may have one or two meetings with Microsoft to discuss your needs at a high level. Keep these discussions professional,
  but don’t feel pressured to commit early. Microsoft may dangle “early renewal” incentive programs (like a slight discount if you sign before the end of their quarter). Note those, but commit only if it truly aligns with your objectives (and ensure any early signing is prorated so you’re not double-paying for overlapping months).
• Draft proposals and back-and-forth (6–3 months before renewal): As you enter roughly the final two quarters before expiration, negotiations should heat up. At about six months out, you should have Microsoft’s initial offer in hand, along with perhaps alternative quotes. Now, formally counter Microsoft’s proposal. This could be achieved through a written counter-proposal or a meeting where you outline the necessary changes (such as price reductions, product mix adjustments, or contract terms). Expect multiple rounds of back-and-forth. Use each round to inch closer to your targets. For example, if Microsoft offers a 5% discount and your goal is 15%, you might counter with 20% to anchor at a higher level. Present data-driven arguments – show where their proposal doesn’t match your usage or how you can’t possibly get value out of certain components at their price. Around 3–4 months out, consider engaging higher-ups on both sides if needed: your executive sponsor might call a Microsoft regional director or VP to push for better terms, especially on big-ticket items. Microsoft’s reps will be increasingly eager to close by now (they have their own timelines and quotas), so use that to your advantage. Also, be mindful of any known Microsoft price increases or product changes announced for the upcoming year – if, say, Microsoft declared that prices for a certain product will rise 10% next year, you have a window to negotiate a renewal before that kicks in, effectively saving that 10% by acting early.
• Final negotiation & contract signature (last 3 months): In the final 90 days, you should be concluding negotiations, not starting them. By this point, ideally, all major terms are agreed in principle. The focus shifts to ironing out the details and ensuring that the contract documents accurately reflect the terms of the deal. However, this period can also be where the last bit of brinkmanship occurs. Microsoft knows time is almost up, and they might make a final push – for example, offering “if you can sign this week, we’ll throw in 500 Azure licenses for free” or, conversely, trying the scare tactic “your prices will reset to list if this isn’t done.” With your preparation, you can cut through these tactics. Stay firm on any unresolved must-haves. If you’ve met your goals, you can use these weeks to make one last concession (for instance, ask for a slight extra discount in exchange for signing by a certain date, as they want closure). Ensure your legal team conducts a line-by-line contract review to verify that every concession (such as a special discount or flexible term) is properly documented. It’s common for contracts to accidentally omit something agreed verbally – don’t let that slip. Once all is verified, obtain final executive sign-off and execute the agreement. Plan an internal announcement or meeting to inform stakeholders of any changes (like, “we’re adding Teams Phone for all users starting next quarter,” or “we’ve eliminated product X – those users will move to product Y”). Also, set up governance for the new EA – schedule check-ins (maybe quarterly) to track usage against what you purchased, so you remain in control throughout the EA term and are even more prepared when the next renewal eventually comes.

By breaking the process into these phases, you create a roadmap that keeps everyone accountable and ensures a clear understanding of the tasks at hand.

You can literally mark these phases on a calendar, ensuring, for example, that by six months out, you have at least one solid offer on the table and by three months out, you’re just fine-tuning terms and completing paperwork.

It prevents the common scenario of waking up 30 days before expiration with a significant amount of work still to be done. In short, a clear negotiation timeline helps you negotiate steadily and confidently, rather than in a panic.

Related articles

• Microsoft EA Negotiation Checklist: Pre-Negotiation Readiness
• Microsoft EA Negotiation Team: Building the Right Cross-Functional Strategy
• Setting Goals and Leverage for Your Microsoft EA Negotiation
• Internal Audit: Assessing Your Current Microsoft Licensing

EA Negotiation Timeline Checklist:

• Internal data collection complete: All inventory and usage analysis done; you know exactly what you have and use (no later than T–9 months).
• Objectives and limits agreed upon: Your negotiation goals, budget cap, and must-have terms are documented and approved internally (approximately 9 months before the start of the project).
• Microsoft engagement initiated: You’ve had your first discussion or exchanged information with Microsoft or partners, signaling that you’re approaching renewal deliberately (by ~T–6 months).
• Draft proposals reviewed: You have received and analyzed Microsoft’s proposal, and you’ve provided a counteroffer. Multiple proposal drafts have been evaluated by your team (between T–6 and T–3 months).
• Final terms negotiated: All major deal points are settled in principle before the last-minute crunch. The contract is in the final review stage, with signature on track to be completed ahead of the expiration date (by T–0).

Each item above corresponds to a major milestone in your EA negotiation timeline. If you can check all these off, you’re in excellent shape heading into the renewal.

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