Why Right-Sizing Matters Before Renewal

Microsoft's EA renewal process creates a natural pressure towards licence expansion — account teams earn quota credit on new seats and upgrades, not on right-sizing. If you enter the renewal conversation without an independent licence census, Microsoft's proposal will be based on your current committed seat count, inflated by any mid-term additions, and Microsoft will propose further growth. The result is a renewed EA at a higher base than your actual requirement. This article is part of our Microsoft Enterprise Agreement Negotiation: Definitive Guide.

Right-sizing before renewal achieves three things: it reduces the base on which Microsoft's pricing is applied; it gives you credible data to challenge Microsoft's seat count proposals; and it demonstrates to Microsoft's account team that you are a structured, data-led buyer — which changes the commercial dynamic in the negotiation.

Typical right-sizing outcomes from our engagements: M365 seat reductions of 8–18% through elimination of ghost accounts and role-based over-provisioning; E5 to E3 downgrades for 15–40% of the population where E5 features are not used; Dynamics seat reductions of 20–35% through module-by-module access reviews; and Azure spend optimisations of 12–25% through Reserved Instance and savings plan right-sizing.

Free Guide

Microsoft EA Negotiation Tactics

How Fortune 500 buyers slash Microsoft EA costs — true-up traps, ELP rules, and renewal leverage.

The Right-Sizing Methodology

A complete Microsoft licence right-sizing exercise covers five domains: M365 seat management, Azure committed spend, Dynamics 365, Developer tools, and security add-ons. Here is the structured approach our advisors apply.

Step 01

M365 Seat Census: Ghost Accounts and Inactive Users

Pull the complete M365 licence assignment report from the Microsoft 365 Admin Centre. Cross-reference against your Active Directory or Entra ID user list. Identify accounts that have been licenced but show zero sign-in activity in the last 90 days — these are typically leavers who have not been deprovisioned, contractors whose engagements have ended, or service accounts that were assigned user licences incorrectly. In most large enterprises, this exercise alone identifies 3–8% of seats that can be immediately removed from the renewal base.

Step 02

E5 vs E3 Population Review

For each user assigned an M365 E5 licence, audit which E5-specific features they are actively using. Microsoft's usage data in the Admin Centre and Microsoft 365 Usage Analytics provides feature-level adoption data by user. Users who are assigned E5 but whose usage shows only E3-level feature activity (Exchange Online, Teams, SharePoint, basic Defender) are candidates for downgrade to E3 or E3 + targeted add-ons. In most enterprise deployments, 20–40% of E5 users can be reclassified without functional impact. See our Microsoft E5 Security: Cost-Benefit Analysis for the security-specific decision framework.

Step 03

Frontline Worker and Kiosk Licence Identification

Microsoft offers Frontline Worker licences (M365 F1 at $2.25/user/month and F3 at $8/user/month) for users who do not require full desktop Office applications. Manufacturing floor workers, retail staff, healthcare aides, and field service employees often do not need the full E3 suite. Identifying the frontline worker population and reclassifying them to F-tier licences is one of the highest-value right-sizing actions available — the per-seat saving is typically $20–$25 per user per month.

Stay Ahead of Vendors

Get Negotiation Intel in Your Inbox

Monthly briefings on vendor pricing changes, audit trends, and contract tactics. Unsubscribe any time.

No spam. No vendor affiliations. Buyer-side only.

Step 04

Azure Reserved Instances and Savings Plans

For organisations with Azure committed spend in their EA, a Reserved Instance (RI) and savings plan audit identifies compute resources that are running on pay-as-you-go pricing when a 1-year or 3-year reservation would deliver 20–40% savings. Azure Cost Management provides a reservation recommendations report that identifies the top candidates. Cross-reference these recommendations against your actual deployment plans — do not commit to reservations for workloads that are under active migration or rationalisation. See our dedicated guide on Azure Reserved Instances Negotiation for the full methodology.

Step 05

Dynamics 365 Module and User Access Review

Dynamics 365 licences are frequently over-provisioned at initial deployment and never reviewed. For each Dynamics module in your EA (Sales, Customer Service, Finance, Supply Chain, HR), pull the user list and cross-reference against actual system logins in the last 90 days. Users with no Dynamics activity in the last quarter are candidates for licence removal. Additionally, review whether users assigned full user licences could be reclassified as Team Members (read-only access) at significantly lower cost. See our guide on Dynamics 365 Licensing Guide for module-level details.

Tools and Data Sources

The right-sizing exercise draws on data from multiple Microsoft administrative portals:

Important: Microsoft's usage data has known gaps and delays. Licence assignment data is authoritative — Microsoft bills on what is assigned, not what is used. Do not rely solely on Microsoft-provided usage reports; cross-reference with HR systems, Active Directory, and application access logs to get an accurate picture of actual requirement.

Presenting Right-Sizing Findings in Renewal Negotiations

The value of a licence census is not just in the cost reduction itself — it is in the negotiating posture it creates. When you present Microsoft with a data-led licence census showing your revised seat requirements, Microsoft's response is constrained: they cannot argue that you need more licences than you can demonstrate you are using. This shifts the burden of proof from the buyer to Microsoft.

Present your census findings in writing before Microsoft's formal renewal proposal. This establishes your seat base as the reference point for the negotiation, rather than Microsoft's inflated starting position. Our How We Work page explains the structured approach we take to EA renewal negotiations in detail.

Handling Microsoft's Push-Back

Microsoft's account team will typically respond to right-sizing evidence in one of three ways: accepting the reduced seat count and adjusting pricing; proposing a "true-up protection" clause that effectively locks the higher seat count; or counter-arguing with Microsoft's own usage data. Each response has a specific counter-strategy. In our experience across 200+ Microsoft EA engagements, persistent presentation of usage data, combined with a credible willingness to reduce scope, results in Microsoft accepting the revised seat base in approximately 85% of cases.

Timing the Right-Sizing Exercise

The right-sizing exercise should be completed at least 6 months before your EA renewal date. This provides sufficient time to complete the audit, validate findings, remove ghost accounts, and incorporate the results into your negotiation strategy before Microsoft's account team opens formal renewal discussions. Starting later reduces your leverage — Microsoft's renewal proposals are harder to revise once formally submitted. For guidance on the full renewal timeline, see our Microsoft EA Renewal: 15 Tactics That Work.

Further Reading