What the Microsoft EA True-Up Is and How It Works, The Annual True-Up Timeline and Contractual Deadlines, True-Up Cost Drivers — Headcount Growth, Cloud Expansion, and Product Sprawl, How to Audit Usage Before Submitting True-Up Numbers, The Licence Cleanup Process That Reduces True-Up Cost by 10–20%, Product-Specific True-Up Strategies for M365, Azure, Dynamics 365, and Server Products, Common True-Up Pitfalls and How to Avoid Them, How True-Up Data Becomes Renewal Negotiation Leverage, Enterprise Subscription Agreement — The True-Down Alternative, and the Ongoing Governance Framework That Makes True-Ups Routine
The Microsoft Enterprise Agreement True-Up is the annual reconciliation process where organisations report additional licences consumed during the year and purchase them at the EA's locked-in pricing. It occurs at each EA anniversary (typically 30 days before) across the three-year term. While contractually straightforward — you pay for what you've added — the true-up is where most enterprises haemorrhage money through poor licence hygiene, unmanaged growth, auto-provisioning defaults, and failure to clean up before reporting. For the complete EA overview, see Microsoft Enterprise Agreement Guide. For the Microsoft licensing knowledge base, see the Microsoft Licensing Knowledge Hub.
| True-Up Characteristic | How It Works | Opportunity | Risk If Mismanaged |
|---|---|---|---|
| Annual reconciliation | Report additional users, devices, and cloud subscriptions added since last count; purchase at EA pricing | EA pricing is locked — additions cost the same per-unit rate as original purchase | Unmanaged growth creates budget surprises — $100K–$1M+ unplanned spend common in large enterprises |
| One-directional (standard EA) | Can add licences at true-up but CANNOT reduce — committed quantities are fixed for the term | Enterprise Subscription Agreement variant allows true-down at anniversaries | Over-provisioned licences are locked in for the remaining term — no refund or reduction |
| 30-day reporting window | True-up report due 30 days before EA anniversary date | Predictable deadline enables structured preparation | Missing the deadline can create compliance gaps and strain Microsoft relationship |
| Price protection during term | True-up pricing matches original EA rates — protected from Microsoft list price increases | Additions in years 2 and 3 still use year-1 pricing — significant value if Microsoft raises prices | No protection at renewal — Microsoft may attempt 10–20% uplift on next term |
| Pro-rated payment | Licences added via true-up are pro-rated for the remaining term | Adding in year 3 costs less than adding in year 1 due to shorter remaining term | Large deployments early in the term create substantial lump-sum payments |
| Compliance verification | Microsoft uses true-up as de facto compliance check — discrepancies may trigger formal audit | Accurate true-ups build trust and reduce audit risk | Under-reporting triggers audit; over-reporting wastes budget |
Understanding the primary cost drivers behind true-up growth enables proactive budget planning and targeted cost reduction. For common licensing mistakes, see Common Microsoft Licensing Mistakes to Avoid. For eliminating redundant software, see Eliminating Redundant Microsoft Software.
| Cost Driver | How It Increases True-Up | Typical Impact | Mitigation |
|---|---|---|---|
| Headcount growth | Every new employee requires M365, Windows, and potentially other licences | $400–$700 per new user per year (M365 E3/E5) | Forecast hiring with HR; budget for expected additions; use F1/F3 for frontline workers |
| Auto-provisioning to premium tiers | Default onboarding scripts assign E5 instead of E3; auto-licensing applies most expensive available licence | $288/user/year wasted (E5 vs E3 delta) × hundreds of users = $50K–$200K+ annually | Audit provisioning scripts; set default to E3; require justification for E5 |
| Cloud service expansion | Azure consumption growth, new Power Platform adoption, Dynamics 365 rollouts | Varies widely — Azure overcommitment alone can be $100K–$500K+ | Track Azure usage vs commitment monthly; right-size before true-up |
| Server infrastructure growth | New SQL Server, Windows Server, or System Center deployments | $6K–$15K per server in additional core licensing | Centralise server provisioning; require SAM approval before deployment |
| Mergers and acquisitions | Acquired company's users and systems need licensing under the EA | Potentially $500K–$5M+ depending on acquisition size | Pre-negotiate M&A clauses in EA; plan integration licensing separately |
| Departed employees not delicensed | Licences remain assigned to terminated employees; counted as active at true-up | $400–$700 per ghost user per year — 5–10% of licence base typical | Automate delicensing in offboarding workflow; monthly HR/AD reconciliation |
For Microsoft licensing metrics, see Microsoft Licensing Metrics: Cores, Users, Devices.
The licence cleanup performed 60–90 days before the true-up deadline is the single most impactful cost reduction activity in Microsoft EA management. Most enterprises find 10–20% of their licence assignments are waste — departed employees, unused subscriptions, over-provisioned editions, and duplicate accounts. For true-up mistakes to avoid, see Microsoft Licensing True-Ups: Avoiding Costly Mistakes.
| Cleanup Activity | What to Look For | Typical Waste Found | Savings Per Unit |
|---|---|---|---|
| Remove departed employee licences | Compare M365 admin centre user list against current HR headcount; flag any user not in active HR system | 5–10% of total licence base (50–500+ licences in large enterprises) | $396–$684 per user per year (E3/E5) |
| Downgrade over-provisioned editions | Identify E5 users who only use E3 features (no Defender P2, no compliance, no audio conferencing) | 20–40% of E5 assignments may only need E3 | $288 per user per year (E5→E3 downgrade) |
| Move frontline workers to F licences | Identify users on E3/E5 who only need mobile/web access, basic Teams, and limited apps | Varies — retail, manufacturing, healthcare organisations often have hundreds of frontline users on E3 | $300+ per user per year (E3→F3 downgrade) |
| Reclaim inactive licences | Pull M365 usage reports; identify users with no sign-in activity in 90+ days | 5–15% of licences typically inactive | $396–$684 per reclaimed licence per year |
| Eliminate duplicate accounts | Search for users with multiple M365 accounts (common after M&A or domain migrations) | 1–5% of licence base in post-M&A environments | $396–$684 per duplicate eliminated |
| Remove unused add-on subscriptions | Audit Visio, Project, Power BI Pro, and other add-on assignments against actual usage | 30–50% of add-on licences often unused | $120–$660 per unused add-on per year |
Each Microsoft product category has specific true-up dynamics. Optimising each category independently maximises overall savings. For the EA overview including product scope, see Microsoft Enterprise Agreement Guide. For Microsoft EA vs MPSA, see Microsoft EA vs MPSA.
| Product Category | True-Up Trigger | Optimisation Strategy | Savings Potential |
|---|---|---|---|
| Microsoft 365 E3/E5 | New users; over-provisioning; departed employees not delicensed | Monthly HR/AD reconciliation; edition right-sizing; F-licence for frontline; automate offboarding delicensing | 10–25% reduction in M365 true-up cost through cleanup |
| Azure consumption | New workloads; VM sprawl; dev/test not shut down; reserved instance expiry | Weekly Azure cost monitoring; auto-shutdown for dev/test; reserved instances for steady-state; tag-based cost allocation | 20–40% Azure cost reduction through optimisation |
| Dynamics 365 | New module rollouts; user count growth; Team Member vs full licence confusion | Use Team Member ($8/user/month) for light users; audit Dynamics user assignments quarterly | $57–$202/user/month saved by right-sizing to Team Member |
| SQL Server | New database instances; core count increases; edition upgrades (Standard→Enterprise) | Consolidate databases; evaluate Azure SQL as alternative; right-size editions | $6K–$15K per eliminated server |
| Windows Server + CALs | New physical/virtual server deployments; user/device CAL growth | Use Azure Hybrid Benefit; consolidate VMs; track CAL assignments accurately | $3K–$6K per consolidated server |
For evaluating Microsoft renewal proposals, see How to Evaluate a Microsoft Renewal Proposal.
Treating the true-up as a structured 90-day project rather than a last-minute exercise dramatically improves accuracy and reduces cost. For Microsoft contract renewal planning, see Microsoft Contract Renewal Planning Strategy.
| Timeline | Activity | Deliverable | Owner |
|---|---|---|---|
| T-90 days | Kickoff: assemble true-up team (SAM, IT, Finance, HR); pull current licence inventory from M365 admin centre | Baseline licence count; team assigned with clear roles | SAM Manager |
| T-75 days | HR reconciliation: cross-reference M365 users against active employee list; flag departed employees | List of licences to reclaim from departed/inactive users | SAM + HR |
| T-60 days | Licence cleanup: remove departed users; downgrade over-provisioned editions; reclaim inactive licences; eliminate duplicates | Cleaned licence inventory — typically 10–20% reduction in assignments | SAM + IT Ops |
| T-45 days | Usage analysis: pull M365 usage reports; review Azure consumption vs commitment; audit server deployments | Product-by-product usage analysis; identify genuine net additions | SAM + Cloud Ops |
| T-30 days | Calculate true-up order: determine net new licences needed; calculate cost; obtain Finance approval | True-up order with cost estimate; Finance sign-off | SAM + Procurement + Finance |
| T-15 days (or anniversary deadline) | Submit true-up: place order through reseller or Microsoft portal; verify processing; update internal records | Submitted and confirmed true-up; updated licence inventory | Procurement + SAM |
For the final steps at signing/renewal, see Final Steps Before Signing Your Microsoft EA.
Even experienced ITAM professionals fall into common traps during the true-up process. Awareness of these pitfalls is the first step to avoiding them. For broader licensing mistakes, see Common Microsoft Licensing Mistakes to Avoid. For true-up-specific mistakes, see Microsoft Licensing True-Ups: Avoiding Costly Mistakes.
| Pitfall | What Happens | Financial Impact | Prevention |
|---|---|---|---|
| Last-minute scramble | True-up preparation starts days before deadline; data is rushed, inaccurate, or incomplete | Over-reporting wastes $50K–$200K+; under-reporting triggers audit | Start 90 days before; make true-up a structured project, not an afterthought |
| Ghost users — departed employees still licensed | Offboarding process doesn't include licence reclamation; departed employees counted in true-up | $400–$700 per ghost user per year — hundreds of thousands wasted across large enterprises | Automate delicensing in HR offboarding; monthly AD/HR reconciliation |
| Default E5 provisioning | Automated onboarding assigns premium E5 to all users regardless of need | $288/user/year unnecessary spend × hundreds of users | Set E3 as default; require documented justification for E5 assignment |
| No Finance communication | True-up cost lands on Finance desk as unplanned expense; creates internal friction | No direct financial impact but damages IT-Finance relationship and future budget approvals | Include Finance in true-up planning from T-90; provide cost estimate at T-45 |
| Ignoring contract terms | Missing reduction eligibility windows; not understanding which subscriptions can be adjusted | Locked into unneeded subscriptions for remaining term | Review EA contract 90 days before anniversary; know which products allow true-down |
Three years of true-up data is the most powerful asset in an EA renewal negotiation. It shows exactly what your organisation uses, how usage trends have moved, and where Microsoft's value proposition is strong or weak. For negotiation strategies, see How to Negotiate the Best Deal with Microsoft. For price protection clauses, see Negotiating Price Protections in Microsoft EA.
| True-Up Insight | Negotiation Application | Expected Impact |
|---|---|---|
| Usage declined for specific product | Negotiate reduced quantity at renewal — present data showing shrinking usage as justification | 5–20% cost reduction on that product line; Microsoft may counter with alternative or discount |
| Consistent over-provisioning at E5 but E3 usage patterns | Negotiate mixed E3/E5 deployment with lower blended rate | $100K–$500K+ savings by right-sizing before renewal baseline locks in |
| High true-up additions each year | Negotiate better per-unit pricing for expected growth; request volume tier uplift | 5–15% lower per-unit rate on growth licences |
| Significant shelfware identified | Use unused licence data to negotiate elimination of those products; redirect spend to actually-used services | Eliminates waste; may fund new products at no net cost increase |
| Azure consumption consistently below commitment | Negotiate lower Azure commitment with rollover clause for next term | Prevents overcommitment waste; rollover protects against timing mismatches |
For CIO-level renewal evaluation, see CIO Playbook: Evaluating Microsoft Renewal Proposals. For termination and renewal options, see Negotiating Termination and Renewal Options.
The Enterprise Subscription Agreement (ESA) is a variant of the standard EA that allows organisations to reduce (true-down) licence counts at each anniversary — not just add. This provides critical flexibility for organisations with volatile headcount or undergoing restructuring. For the CSP and NCE licensing shift, see CIO Playbook: Microsoft CSP and NCE Licensing Shift.
| Dimension | Standard EA | Enterprise Subscription Agreement (ESA) | When ESA Is Better |
|---|---|---|---|
| True-up | Can add licences at each anniversary | Can add licences at each anniversary | Both allow adding |
| True-down | CANNOT reduce — locked to initial quantities for full 3-year term | CAN reduce at each anniversary — typically by up to a negotiated percentage | ESA protects against paying for unneeded licences if headcount drops |
| Licence ownership | Perpetual — licences owned after term (at last-used version) | Subscription — licences expire if agreement is not renewed | Standard EA better for long-term ownership; ESA better for flexibility |
| Cost | Generally lower annual cost (no flexibility premium) | ~10–15% premium over standard EA for flexibility | ESA premium justified if headcount volatility exceeds 10–15% |
| Best for | Stable organisations with predictable headcount and steady growth | Organisations with volatile headcount, M&A activity, restructuring, or seasonal workforce | Evaluate based on headcount volatility and risk tolerance |
For the benefits of standard EA, see Benefits of a Microsoft Enterprise Agreement.
The difference between proactive and reactive true-up management directly impacts budget predictability, compliance risk, and Microsoft negotiating position. For managing Microsoft under an EA, see Managing Microsoft Under an EA. For Microsoft EA optimisation services, see Microsoft EA Optimization Service.
| Dimension | Reactive True-Up Management | Proactive True-Up Management | Financial Difference |
|---|---|---|---|
| Budget impact | Unplanned true-up costs surprise Finance; large last-minute payouts disrupt IT budget | True-up costs anticipated, budgeted, and communicated 90+ days in advance | Eliminates budget surprises — improves IT-Finance relationship |
| Licence waste | Paying for departed employees, unused subscriptions, and over-provisioned editions | Monthly cleanup eliminates waste before true-up count | 10–20% true-up cost reduction through cleanup alone |
| Compliance risk | Under-reporting triggers Microsoft audit; over-reporting wastes budget | Accurate data eliminates audit risk; compliance demonstrated proactively | Avoids audit costs: $100K–$500K+ in potential back-payments eliminated |
| Renewal leverage | No data to challenge Microsoft's renewal proposal; accept default 10–20% uplift | Three years of true-up data drives data-based negotiation; challenges Microsoft assumptions | 5–15% better renewal terms through data-driven negotiation |
| Microsoft relationship | Perceived as disorganised; Microsoft pushes harder on compliance and upselling | Perceived as sophisticated buyer; Microsoft offers better terms to retain relationship | Strategic positioning — difficult to quantify but significant |
For Microsoft renewal with licensing experts, see Microsoft EA Renewal with Licensing Experts.
| # | Action | Owner | Timing | Key Outcome |
|---|---|---|---|---|
| 1 | Mark true-up deadlines in calendar: EA anniversary date, T-90, T-60, T-30 preparation milestones | SAM Manager | At EA signing; reviewed annually | No missed deadlines — structured preparation every year |
| 2 | Implement monthly HR/AD reconciliation: automate comparison of M365 users against active employee list; flag mismatches | SAM + HR + IT Ops | Monthly — ongoing | Ghost users eliminated continuously — not just at true-up |
| 3 | Set provisioning defaults to E3: configure automated onboarding to assign E3 by default; require documented approval for E5 | IT Ops / Identity | Implement once; review quarterly | Prevents $288/user/year unnecessary E5 provisioning |
| 4 | Run pre-true-up licence cleanup at T-60: remove departed users, downgrade over-provisioned editions, reclaim inactive, eliminate duplicates | SAM + IT Ops | 60 days before each anniversary | 10–20% reduction in true-up cost through cleanup |
| 5 | Pull M365 usage reports: analyse actual feature usage to identify E5→E3 downgrade candidates and inactive licences | SAM | T-60; quarterly throughout the year | Data-driven edition right-sizing |
| 6 | Review Azure consumption vs commitment: identify idle resources, right-size VMs, apply reserved instances | Cloud Ops / FinOps | Weekly monitoring; monthly optimisation review | 20–40% Azure cost reduction |
| 7 | Calculate true-up order and obtain Finance approval: determine net new licences; calculate cost; submit to Finance at T-45 | SAM + Procurement + Finance | T-45 | No budget surprises — Finance informed and approved in advance |
| 8 | Submit true-up order by deadline: place order through reseller or Microsoft portal; verify confirmation | Procurement | T-30 (30 days before anniversary) | Compliant and on time — no audit risk from missed deadline |
| 9 | Archive true-up data for renewal leverage: document licence counts, cleanup actions, usage trends, and cost for each year | SAM | After each true-up | Three years of data for renewal negotiation — the single most valuable renewal asset |
| 10 | Conduct post-true-up review: identify what drove additions; plan governance improvements; feed insights into next year's budget | SAM + Finance + IT leadership | Within 30 days after true-up | Continuous improvement — each year's true-up is better managed than the last |
For expert Microsoft EA true-up and renewal guidance, Redress Compliance provides independent advisory through our Microsoft EA Optimization Service, Microsoft Contract Negotiation Service, Microsoft Audit Defense Service, and Microsoft Optimization Services.
The true-up is an annual reconciliation process where organisations report additional licences consumed during the year and purchase them at the EA's locked-in pricing. It occurs at each EA anniversary (typically 30 days before), ensuring licence compliance by aligning entitlements with actual usage.
The true-up occurs at each EA anniversary — annually during the three-year term. Most EAs require the true-up report to be submitted 30 days before the anniversary date. This means three true-ups during a standard EA: at the end of year 1, year 2, and year 3 (which coincides with renewal).
Under a standard EA, no — the true-up is one-directional (add only). You cannot reduce committed quantities mid-term. The Enterprise Subscription Agreement (ESA) variant allows true-down at anniversaries, typically up to a negotiated percentage. Some cloud subscriptions may also allow reduction depending on EA terms.
True-up costs vary widely based on organisational growth. A mid-size enterprise (5,000 users) with 10% annual growth typically spends $200K–$500K per true-up. Large enterprises (20,000+ users) with similar growth rates often see $500K–$2M+ per true-up. Without cleanup, 10–20% of this is typically waste.
Missing the true-up deadline creates a compliance gap. Microsoft may charge backdated licensing at list price rather than EA rates, trigger a formal audit, or apply administrative penalties. At minimum, it strains the Microsoft relationship. Always submit on time — even a zero-change report if no additions occurred.
The highest-impact strategy is pre-true-up licence cleanup 60–90 days before the deadline: remove departed employee licences, downgrade over-provisioned editions (E5→E3), reclaim inactive licences, and eliminate duplicates. This typically reduces the true-up bill by 10–20%. Additionally, right-size Azure consumption and Dynamics 365 user assignments.
A standard EA provides perpetual licence ownership but does not allow quantity reduction mid-term. The Enterprise Subscription Agreement (ESA) allows true-down (reduction) at each anniversary but licences expire if the agreement is not renewed. ESA typically costs 10–15% more but provides critical flexibility for volatile organisations.
Neither. Over-estimating wastes budget on unused licences; under-estimating creates compliance risk and may trigger audit. Aim for accuracy through systematic data collection, HR/AD reconciliation, and pre-true-up cleanup. The goal is reporting exactly what is needed — no more, no less.
True-up pricing matches the per-unit rates locked in at EA signing. If you negotiated $30/user/month for M365 E3 at signing, additions in year 2 or 3 still use that same rate — even if Microsoft has raised list prices. Payment is pro-rated for the remaining EA term.
While true-up pricing is contractually set, large additions (100+ licences) may warrant discussion with your Microsoft account team or reseller about additional volume benefits. You cannot renegotiate the per-unit rate mid-term, but you may be able to negotiate value-added services, credits, or better pricing at the next renewal.
Three years of true-up data shows exactly what your organisation uses, growth trends, and where waste exists. This data enables you to right-size the renewal baseline, challenge Microsoft's proposed uplift (typically 10–20%), negotiate reduced quantities for declining products, and demand better rates for growing products.
All products and subscriptions under the EA are subject to true-up, including Microsoft 365 user subscriptions, Windows Server and SQL Server core licences, CALs, Dynamics 365 subscriptions, Azure consumption above commitment, Power Platform licences, and any add-ons (Visio, Project, Power BI Pro).
Implement monthly automated reporting from M365 admin centre, Azure cost management, and Active Directory. Cross-reference against HR headcount data. Use a Software Asset Management (SAM) tool to maintain continuous inventory. Quarterly internal audits catch discrepancies before they compound into true-up surprises.
For EA deals above $2M, independent Microsoft licensing advisors typically deliver 10–25% savings through optimisation and cleanup that internal teams miss. They also provide benchmark data for renewal negotiation. The advisory fee is typically a fraction of the savings identified.
This article is part of our Microsoft Enterprise Agreement Guide pillar. Explore related guides:
Redress Compliance has helped hundreds of enterprises negotiate better Microsoft EA, CSP, and Azure terms — typically saving 15–30% on renewals.
100% vendor-independent · No commercial relationships with any software vendor