What Is a Microsoft EA True-Up?
The Microsoft Enterprise Agreement true-up is the annual reconciliation mechanism built into every EA. Each year on your EA anniversary, you must report the actual number of qualifying users, devices, and software deployments across your organization. If that number has grown since your initial EA commitment or your last true-up, Microsoft bills you for the difference — at your EA-negotiated prices — retroactively to the start of the EA year.
This is the moment many organizations discover they've been using more software than they licensed. And because the EA obligates you to report honestly, under-reporting creates audit exposure. The true-up is Microsoft's primary revenue mechanism for capturing organic growth within your organization.
Understanding the true-up is critical within the context of your broader Microsoft Enterprise Agreement negotiation strategy. The terms you negotiate upfront — including true-up pricing, the definition of "qualifying users," and step-down rights — directly determine how expensive your annual reconciliation will be.
Key Principle
The true-up is not just an administrative exercise — it's a negotiation. The prices applied at true-up are locked at your initial EA rates. If you've negotiated good upfront discounts, those flow through to true-up additions. If you haven't, every incremental seat costs full EA list price.
How the True-Up Process Works
Microsoft structures the true-up as a formal annual order within your EA. The process follows a predictable sequence:
Expert Advisory
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
- Anniversary notification: Microsoft sends a true-up reminder 30-60 days before your EA anniversary. This includes your current EA order quantities as the baseline.
- You conduct inventory: Your organization runs a full count of qualifying users and deployments across all EA-covered products.
- You submit a true-up order: Through your Microsoft reseller or direct EA portal, you submit an order for any quantities above your current EA baseline.
- Microsoft invoices the delta: You're charged for the additional licenses at your EA rates, backdated to the start of the EA year. If you're 6 months into your EA year when you submit the true-up, you pay for 12 months of the additional licenses — not 6.
- New baseline is set: Your true-up quantities become the new baseline for the following EA year.
The retroactive billing is the detail that catches most organizations off guard. If you hired 200 employees in month 3 of your EA year and deployed Microsoft 365 for them, your true-up at month 12 will charge you for 12 months of those 200 seats — not the 9 months they actually used the software.
Important
True-up backdating means a delay in reporting always costs more than reporting accurately throughout the year. 200 seats at $360/year (M365 E3) reported at month 12 = $72,000. If you'd reported them at month 3, you'd still pay $72,000 — but Microsoft bills from the EA start date regardless of when you submit the true-up order.
What Gets Counted at True-Up
The scope of what Microsoft counts at true-up depends on which products are in your EA. For most enterprise customers, true-up counts include:
| Product Category |
What Gets Counted |
Common Misses |
| Microsoft 365 |
Qualifying users with active accounts |
Shared mailboxes, service accounts, contractors |
| Windows Enterprise |
Qualifying devices running Windows Enterprise |
VDI clients, Azure Virtual Desktop instances |
| SQL Server |
Core licenses or CALs per server/device |
Dev/test environments, Docker containers |
| Exchange / SharePoint |
User CALs or SA if on-prem |
External users, extranet partners |
| Dynamics 365 |
Named users per module |
Team member licenses vs. full user licenses |
| Azure |
Monetary commitment / MACC consumption |
Software deployed in Azure needing separate licenses |
The "Qualifying User" Definition
One of the most important — and most abused — concepts in EA true-up is the definition of a "qualifying user." Microsoft's standard definition is any user who accesses the licensed software, but the EA includes important nuances:
- Shared mailboxes that are only accessed by other licensed users generally do not require their own license.
- Service accounts used only for automated processes typically do not require user licenses.
- Contractors and temps may be eligible for limited-use or kiosk licensing at a lower cost than full user licenses.
- External users accessing your SharePoint intranet may require external connector licenses rather than full user licenses.
Scrutinizing these definitions before your true-up is often worth tens of thousands of dollars in avoided costs. Many organizations default to counting every Active Directory account, significantly over-reporting their true user count.
9 Costly True-Up Traps
Trap 01
Free Resource
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
Counting All AD Accounts as Qualifying Users
Your Active Directory may contain thousands of inactive accounts, shared mailboxes, service accounts, and test users. Counting all of them inflates your true-up count substantially. Audit AD for accounts that haven't logged in within 90 days, service accounts with no interactive access, and shared mailboxes not requiring individual licenses.
Trap 02
Missing Teams Rooms Licensing
Microsoft Teams Rooms devices require their own licensing — either Teams Rooms Basic (free, limited) or Teams Rooms Pro ($40/device/month). Many organizations deploy Teams Rooms hardware and forget to account for device licenses at true-up, creating significant exposure if Microsoft audits your deployment.
Trap 03
Azure Software Running Without True-Up Licenses
Running SQL Server or Windows Server in Azure without BYOL or Azure Hybrid Benefit doesn't eliminate your licensing obligation — Azure simply bills you for the license cost through the VM pricing. But if you're deploying SQL Server in Azure without proper tracking, you may owe true-up obligations for on-prem licensing you thought you'd eliminated.
Trap 04
Ignoring Contractor and Temp Worker Exposure
Contractors who access Microsoft 365 or other EA-covered products create licensing obligations. However, many organizations miss that these users are eligible for lower-cost options — Frontline Worker licenses (F1/F3) or limited-use agreements — rather than full E3/E5 licenses. Paying full price for contractor access is a common overpayment.
Trap 05
Missing the True-Up Submission Window
Most EAs require true-up submission within 30-60 days of the EA anniversary. Missing this window can trigger automatic renewal at your current EA quantities (even if they're wrong) or, worse, create a lapsed-EA scenario where Microsoft's standard pricing applies. Always submit early — aim for 30 days before the anniversary.
Trap 06
Over-Assigning Premium SKUs
Many organizations assign M365 E5 to all users for simplicity, when only a subset (finance, legal, security) actually need E5 features. At true-up, if you've grown from 1,000 to 1,200 users and all are on E5, you're adding 200 E5 seats at ~$57/user/month when 150 of those users need only E3 (~$36/user/month). That's a $78,000/year difference on just 200 seats.
Trap 07
Not Reclaiming Departing Employee Licenses
When employees leave, their accounts should be immediately disabled and their licenses reclaimed. Organizations with high turnover often accumulate hundreds of ghost licenses — paid-for seats attached to inactive accounts. While you can't reduce below your EA minimum, reclaiming licenses offsets true-up additions and avoids unnecessary cost increases.
Trap 08
Treating VDI as Physical Device Licensing
Virtual desktop infrastructure has specific licensing rules that differ from physical devices. Windows Enterprise licenses for VDI may be covered differently under your EA than physical device licenses. Azure Virtual Desktop has its own licensing model entirely. Mis-categorizing VDI deployments is a frequent source of both over-payment and audit exposure.
Trap 09
Assuming True-Up Prices Match Your Initial EA Discount
Your true-up additions are priced at your EA agreed rates — which may have been negotiated 2 years ago when pricing was different. Microsoft regularly adjusts list prices. If your EA discount was 15% off a list price that has since increased by 20%, your true-up additions are more expensive in absolute terms than your original purchase. Always verify current list prices when calculating true-up budgets.
90-Day True-Up Preparation Checklist
Structured preparation over 90 days transforms the true-up from a reactive billing event into a controlled, optimized process.
Days 90–61: Inventory & Discovery
- Export all active user accounts from Azure Active Directory, filtering by last sign-in date
- Run Microsoft 365 admin center license reports to see assigned vs. active licenses per SKU
- Identify all service accounts, shared mailboxes, room mailboxes, and equipment mailboxes
- Inventory all devices running Windows Enterprise using Intune, SCCM, or your MDM solution
- Document all contractor, temp, and external user accounts and their current license assignments
- Pull Azure usage reports to identify SQL Server and Windows Server deployments
- Check Teams Rooms device inventory against current device license assignments
Days 60–31: Optimization
- Disable all inactive accounts (no sign-in within 90 days) and reclaim their licenses
- Downgrade contractors and frontline workers from E3/E5 to F1/F3 where eligible
- Review E5 assignments — remove E5 from users who haven't activated E5-specific features
- Convert eligible on-prem software to Azure Hybrid Benefit to reduce Azure cost and potential true-up exposure
- Align Teams Rooms devices with appropriate license tier (Basic vs. Pro)
- Right-size shared mailboxes — ensure they don't carry user licenses unnecessarily
- Review Dynamics 365 team member vs. full user assignments
Days 30–1: True-Up Submission
- Calculate final true-up delta: current count minus EA baseline quantities
- Verify pricing: confirm your EA unit prices for each product in the true-up
- Prepare true-up documentation with supporting audit evidence
- Brief finance on expected true-up invoice amount and timing
- Submit true-up order to Microsoft reseller or direct EA portal — at least 14 days before anniversary
- Confirm receipt and begin negotiating for next EA year's pricing adjustments
Facing a large true-up invoice?
Expert negotiators can challenge Microsoft's true-up calculations and reduce your exposure.
Get Expert Help →
License Optimization Before True-Up
The most impactful true-up cost reduction doesn't come from negotiation — it comes from accurate license management in the months before reconciliation. Organizations that run continuous license optimization programs typically reduce true-up additions by 20-40% compared to those that manage licenses reactively.
SKU Right-Sizing: The E3 vs E5 Decision
M365 E5 is Microsoft's premium suite at approximately $57/user/month versus E3 at $36/user/month. The $21/month premium per user covers advanced security (Defender, Entra ID P2, Purview), voice (Phone System), and analytics (Power BI Pro). If users don't need these features, the premium is pure waste.
Conduct a feature utilization audit for all E5 users: who has actually used Defender P2 features? Who is using Power BI Pro vs. Free? Who has Cloud App Security policies applied to them? Typically 40-60% of E5 users in enterprise organizations are using only E3-level features. Downgrading these users before your true-up addition date prevents locking in unnecessary E5 seats for another year.
For a deeper analysis of when E5 is justified, see our Microsoft 365 E3 vs E5 comparison guide.
Frontline Worker Licensing
Microsoft 365 F1 ($2.25/user/month) and F3 ($8/user/month) exist specifically for frontline and task workers who need limited Microsoft 365 access. Retail staff, warehouse employees, healthcare workers, and others who primarily use mobile apps rather than full Office desktop applications are candidates. Many enterprises inadvertently assign E3 to these workers — paying 4-16x the appropriate price.
Shared Device Licensing
Shared devices — kiosks, tablets rotated among shifts, shared workstations — can often use Microsoft 365 Shared Device licenses rather than individual user licenses. This is particularly valuable in manufacturing, healthcare, and retail environments where devices far outnumber regular users.
Negotiating True-Up Terms
Most organizations treat the true-up as a billing exercise, not a negotiation. That's a mistake. The true-up moment is actually a leverage point — you're Microsoft's customer committing to additional spend. Use it.
Negotiate Pricing Before Submission
Before submitting your true-up order, engage your Microsoft account team. If you're adding a significant number of seats, request additional discounts on the true-up additions. Microsoft's standard EA pricing already includes volume discounts, but enterprise account teams have discretionary discount authority — especially if you're committing to multi-year growth or expanding into new Microsoft products.
Bundle True-Up with Renewal Negotiations
If your true-up falls within 6 months of your EA renewal, you have significant leverage. Microsoft wants your renewal — use your true-up addition as a bargaining chip. "We'll commit to these additional seats in the renewal at the agreed price, but we want improved terms on the overall EA" is a legitimate negotiation position. See our Microsoft EA renewal tactics guide for detailed renewal negotiation playbooks.
Challenge Auto-Renewal Pricing
If Microsoft automatically renews your EA at expiry without a formal renegotiation, you likely missed a pricing improvement opportunity. Push back on any auto-renewal pricing — Microsoft's list prices change annually, and your original discount percentage may now apply to a higher base, meaning you're paying more in absolute terms than intended.
Request Credit for Optimization Efforts
Organizations that have made significant SAM (software asset management) investments and can demonstrate accurate, proactive license management sometimes successfully negotiate true-up credits or enhanced discount terms. Microsoft values customers who don't create audit risk.
Handling True-Up Disputes
True-up disputes are more common than Microsoft acknowledges. The most frequent sources of dispute are:
- Pricing discrepancies: Microsoft applies a different unit price than what your EA specifies. Always cross-reference your EA price list against the true-up invoice.
- Count methodology disagreements: Microsoft interprets the EA's qualifying user definition differently than you do. Document your counting methodology and the EA language that supports it.
- Retroactive period disputes: Microsoft back-dates true-up charges from the EA start date, but you may have evidence that the deployments occurred later in the year.
- Product classification errors: True-up includes the wrong products or applies the wrong SKU pricing.
For significant disputes, engage a specialist Microsoft negotiation consulting firm. Disputes above $100K warrant professional representation — the ROI is typically 5:1 or better. Document everything: email timestamps, deployment logs, Azure AD export dates, and your EA agreement language.
Expert View
Most true-up disputes settle without formal escalation if you can document your position clearly and engage Microsoft's licensing team (not just your account executive). The account team wants to preserve the relationship; the licensing team wants contractual accuracy. Both are motivated to resolve disputes quickly.
Frequently Asked Questions
What is a Microsoft EA true-up?
A Microsoft EA true-up is the annual reconciliation where your organization reports actual software usage versus your licensed quantities. Any additions are billed at your EA rates, retroactive to the start of the EA year. It occurs once annually on your EA anniversary date.
Can I reduce licenses at true-up?
Generally no — EA minimum quantities are locked for the 3-year term. You can only report additions. Step-down rights (5-10% annual reduction allowance) must be negotiated upfront in the EA. At renewal, you can reduce quantities.
How do I prepare for a Microsoft true-up?
Start 90 days before your EA anniversary. Run a full license inventory, deactivate inactive accounts, right-size SKU assignments, and calculate the true-up delta. Submit your true-up order at least 14 days before the anniversary date.
What are the most common true-up traps?
The most costly traps are: counting all AD accounts (including shared mailboxes and service accounts) as qualifying users, forgetting Teams Rooms device licensing, over-assigning E5 to users who need only E3, and not reclaiming departed employee licenses before the true-up count date.
When should I start preparing for true-up?
90 days before your EA anniversary. Month 1: full inventory. Month 2: optimization and SKU rationalization. Month 3: submission preparation and early submission. Never wait until the final weeks.