Understanding Microsoft True-Ups: Your Annual Reconciliation
A Microsoft True-Up is the annual reconciliation process that occurs within a three-year Enterprise Agreement (EA). It happens automatically 30 days before your EA anniversary date and serves a single critical purpose: to reconcile the number of user seats and products you've actually deployed against what you licensed and paid for during that contract year.
For most enterprises, the True-Up is the first moment of transparency into actual Microsoft consumption. Many organisations discover that they've either under-provisioned licenses (creating compliance exposure) or over-provisioned them (wasting budget). The True-Up is Microsoft's formal reconciliation event—and it's also where Microsoft field teams see an opportunity to upsell, negotiate new terms, or transition customers to higher-tier SKUs.
The stakes are high. True-Up reconciliations can swing tens of thousands to hundreds of thousands of pounds depending on your organisation's size. Worse, if you discover during a True-Up that you've been under-licensed, Microsoft can retroactively charge you for the entire period plus penalties. That's why preparing 60–90 days before the True-Up notice arrives is essential.
How the True-Up Mechanism Actually Works
Timing: True-Up always occurs on your EA anniversary date. Microsoft sends formal notice 30 days before, giving you a narrow window to gather data, negotiate, and commit to quantities.
What gets reconciled: User seats and products deployed across your entire Microsoft footprint. This includes M365 (E1, E3, E5, E7), Azure consumption-based overages, Windows Server, SQL Server, Visual Studio subscriptions, Power Platform, and Dynamics 365. Any Microsoft product under your EA is subject to True-Up reconciliation.
The math: Microsoft compares the number of licenses you've actually deployed (pulled from their usage telemetry and your declarations) against the quantities in your agreement. If you're over, you pay for the additional seats at True-Up rates. If you're under, you face two scenarios: (1) you negotiate True-Down rights to reduce your commitment, or (2) you keep your commitment as-is and receive a credit or adjustment.
The critical distinction is that True-Up pricing is not the same as your original EA pricing. Microsoft applies a "True-Up multiplier" that often results in higher per-unit costs than your initial discount. For example, if you initially negotiated E3 at £180 per user per year with a 15% discount, a True-Up of additional E3 seats might cost £220–240 per seat. That uplift compounds quickly at scale.
The E7 consideration: The Microsoft 365 SKU stack has evolved. Organisations can now choose from E1 (basic), E3 (core), E5 (advanced), and E7 (the new top-tier SKU). E7 bundles advanced AI, security, and compliance features that were previously sold separately as add-ons—including Copilot integration, advanced threat protection, and enhanced governance tools. At True-Up time, Microsoft field teams actively pitch E5-to-E7 upgrades, positioning E7 as the modern standard. If your organisation is on E5, expect this conversation.
The 7 Most Costly True-Up Mistakes
Year after year, the same patterns emerge. These seven mistakes account for the vast majority of True-Up overcharges and compliance exposures:
1. Missed or Underreported Server Products
SQL Server and Windows Server licensing under Enterprise Agreements is complex and easily overlooked. Many organisations deploy SQL Server Standard or Enterprise editions, along with Windows Server instances (especially in hybrid cloud setups with Azure), but don't declare these in their True-Up reconciliation. Microsoft catches these during audit, resulting in back-charges covering the entire under-licensed period plus penalties.
Action: Conduct a detailed server audit 60 days before True-Up. Include SQL Server instances (both on-premise and on IaaS), Windows Server deployments, and any database workloads. These are high-value items that easily add £50,000–200,000+ to an unexpected True-Up bill.
2. Self-Provisioned Power Platform Seats and Apps
Power Platform (Power Apps, Power Automate, Power BI) is increasingly self-service within enterprises. Business users create apps and automations without centralised governance. These all require licensing. If your organisation uses Power Platform beyond what you've licensed, the True-Up will flag it—and at premium pricing.
Action: Audit your Power Platform environment. Identify all Power Apps creators, Power Automate flows in use, and Power BI premium capacity. Cross-reference against your licensed seat count. Many organisations discover 20–40% more Power Platform usage than expected.
3. Azure Overage Charges Bundled in True-Up
Azure is consumption-based, not seat-based, but overages are often reconciled during True-Up. If your Azure spending exceeds your EA commitment, you pay the overage. Unlike M365, Azure has no "True-Down" option—overages are permanent charges. Many organisations under-estimate Azure growth and discover Q3 or Q4 that they're tracking to exceed their annual commit.
Action: Monitor Azure consumption monthly. Use Azure Cost Management or third-party tools to forecast year-end spend. If you're trending to exceed your commitment, escalate to procurement. You may have opportunity to negotiate higher commitment (in exchange for better rates) or find cost optimisation opportunities.
4. Contractor and Service Account M365 Seats Overlooked
M365 licenses are assigned to people and service accounts. Contractors, temporary workers, service accounts, and shared mailbox accounts all count. When your IT team counts "active users," they often forget to include contractors on expired assignments or service accounts that are technically "active" but don't belong to employees. Microsoft's telemetry catches these.
Action: Pull a user census 60 days before True-Up. Segment by employee, contractor, service account, and shared resource. Verify every non-employee M365 assignment. Remove or reallocate licenses for departed contractors and obsolete service accounts.
5. Accepting Inflated True-Up Pricing Without Negotiation
True-Up pricing is not fixed. It's negotiable. Yet 70% of organisations accept Microsoft's initial True-Up quote without challenge. Standard EA discounts are now 10–20% (down from historical 15–25%), but many organisations accept True-Up multipliers of 25–40% above their original EA rates.
Action: Before signing a True-Up, compare the per-unit True-Up cost against your original EA rate. If the uplift exceeds 5–10%, push back. Microsoft expects negotiation at True-Up time. Benchmark your rate against market standard discounts and reference your original EA terms. You have leverage—Microsoft wants to retain you and capture additional E7 upgrades.
Discover where your True-Up costs are hiding
Let our Microsoft EA specialists audit your usage and pricing in advance6. Ignoring Visual Studio Subscription Creep
Visual Studio subscriptions (Enterprise, Professional, Test Professional) are often provisioned by development teams without central tracking. Developers move between projects, leave the organisation, or dual-provision subscriptions across teams. Each subscription is a licensed seat, and True-Up includes them. An enterprise with 100 developers might discover 120–150 actual Visual Studio subscriptions in deployment.
Action: Audit all Visual Studio subscription types assigned across your organisation. Identify duplication, inactive subscriptions, and users with higher-tier subscriptions than necessary (e.g., Enterprise when Professional suffices). Consolidate to your actual developer headcount and skill tiers.
7. Failing to Leverage True-Down Rights
Most enterprise agreements include True-Down rights: the ability to reduce license quantities at the True-Up reconciliation point. If you've over-licensed, you can reduce your commitment for the remainder of your EA term. However, True-Down is not automatic. You must explicitly request it, and it must be negotiated as part of the True-Up. If you don't ask, you keep your commitment as-is and face unnecessary costs.
Action: Review your licensed vs. deployed quantities 90 days before True-Up. If you have significant over-licensing (e.g., 20%+ more licenses than active users), file a True-Down request. True-Down doesn't reduce your current True-Up bill, but it lowers your commitment for the remaining EA term, saving cost over the full three-year agreement.
True-Up as a Microsoft Sales Opportunity: The E5 to E7 Push
Microsoft doesn't view True-Up as merely a reconciliation event. It's a sales moment. Your account team has orders to use the True-Up conversation to pitch account expansion—specifically, to migrate E5 users to E7 and to drive adoption of Copilot add-ons.
Here's how it typically plays out: Your Microsoft account executive says something like, "During your True-Up, we noticed you have 800 E5 users. E7 is now our recommended tier. It includes Copilot for Microsoft 365 and advanced security that you're likely buying separately. Let's upgrade your E5 base to E7—it's only £40–60 more per user per year."
The pitch feels reasonable. E7 does bundle features previously sold as add-ons. But here's the reality: E7 pricing is still a negotiation. Microsoft doesn't force an upgrade, but they will price standard E7 at £350–400 per user per year (vs. E5 at £250–300). If you don't push back, you've just committed to a permanent uplift of £40–100 per user annually.
Copilot pricing: Copilot for Microsoft 365 was initially a £30/user/month add-on. E7 now bundles it. But if Microsoft pitches E7 without discounting for the Copilot that's now included, they're double-dipping on the value transfer. Negotiate the E7 rate down proportionally, or stick with E5 and buy Copilot licenses selectively.
The best approach is to enter your True-Up prepared with a clear SKU strategy. Know whether E5 or E7 is right for your organisation based on security and compliance requirements (not Microsoft's sales pitch). If you're considering E7, benchmark the E7 price against E5 + Copilot add-ons and negotiate accordingly.
Building a True-Up-Ready Organisation
The enterprises that navigate True-Up smoothly don't wait until 30 days before the renewal. They build True-Up readiness into their quarterly governance cycle.
Establish a Cross-Functional True-Up Governance Team
Your team should include ITAM (IT Asset Management), Finance/Procurement, IT Operations, and Security. Monthly or quarterly, this group should:
- Review actual M365, Azure, and other Microsoft product consumption
- Compare deployed licenses against budgeted quantities
- Identify under-utilised or over-provisioned products
- Flag compliance risks (under-licensing)
- Model scenarios for the upcoming True-Up
Conduct a 90-Day Pre-True-Up Data Gathering Sprint
Start 90 days before your EA anniversary. Your ITAM team should pull comprehensive usage data from:
- M365 Admin Center: Active users, license assignments, seat utilisation
- Azure Cost Management: Monthly spend, consumption forecast for full year
- SQL Server licensing tool: All SQL Server instances by edition and core count
- Windows Server inventory: All Windows Server deployments (on-premise and cloud)
- Power Platform admin portal: Power Apps, Power Automate, Power BI usage
- Visual Studio admin portal: All Visual Studio subscription assignments
- Active Directory or Entra ID: Full user census, including contractors and service accounts
Stay Ahead of Your True-Up
Redress Compliance sends early-warning True-Up forecasts and negotiation playbooks. Get insights 60 days before your True-Up notice arrives, so you're never caught off guard.
Model Your True-Up Scenarios
Once you have clean data, model three scenarios:
- Scenario A (Status Quo): Keep current quantities and SKU mix. What is the True-Up bill?
- Scenario B (Optimised): Reduce over-licensed products, consolidate service accounts, adjust to actual deployment. What is the True-Up bill?
- Scenario C (Upgraded): Migrate E5 to E7, or increase Copilot adoption. What is the incremental cost vs. Scenario A?
Run these models at least 30 days before your True-Up notice. Share results with leadership and procurement so they understand the financial implications of each path.
Negotiating True-Up Pricing: Key Levers
When Microsoft presents your True-Up bill, several levers influence the final price:
1. Demand True-Up Pricing Aligned to Original EA Rates
Your opening position: True-Up pricing should match your original EA discount rate. If you negotiated E3 at 18% off list, the True-Up should reflect the same 18% discount, not a new 10% "True-Up multiplier." Microsoft won't always agree, but you must anchor the negotiation there.
2. Leverage Volume and Longevity
If you've been a loyal Microsoft customer and your licence base is growing, reference that. "We've added 200 E3 users this year and are trending to grow further. Our original EA was 500 users; we're now at 800. This growth justifies a renewal at competitive rates—not a markup." Volume and longevity earn discounts.
3. Negotiate E7 Pricing Explicitly if Considering Upgrade
Don't let Microsoft present E7 as a simple add-on cost. Negotiate E7 as a line item. Get a specific E7 per-user annual rate. If Microsoft's E7 price is £380 and E5 is £280, and Copilot-as-add-on would cost £360 annually (£30/month × 12), the true incremental cost of E7 is only £20/user. Push for that framing.
4. Explore Multi-Year Commitment Discounts
If your next EA renewal is approaching (typically 3 years out), consider committing to a new 3-year term during the True-Up. Multi-year commitments earn better discounts. You can trade a small True-Up uplift in year 1 for a lower overall rate over the next three years.
5. Know Your Walk-Away Price
Before entering True-Up negotiation, calculate your maximum acceptable True-Up cost. If Microsoft won't match your rate band after two rounds of negotiation, you have walk-away leverage: "At that price, we need to explore alternative productivity platforms or reconsider our Microsoft commitment." It's not always credible, but it reframes the conversation from "Microsoft dictates price" to "mutual negotiation."
True-Down Rights: What You Can and Cannot Reduce
What you can reduce: Any product quantity that you've over-licensed. If you licensed 600 E3 seats but only deployed 500, you can request a True-Down to 500 for the remaining EA term. Once approved, your commitment drops, and you pay based on the lower number for all future periods.
What you cannot reduce: True-Down does not reduce your current-year True-Up bill. It only affects your commitment for years 2 and 3 of a three-year EA (or the remaining term in a multi-year agreement). Additionally, True-Down is not automatic. You must explicitly request it, and Microsoft can decline in rare cases if the over-licensing was intentional or if you're requesting reduction of a newly added product.
Strategic use: If you're planning an organisational restructure or significant headcount reduction, True-Down is valuable. If you over-licensed E5 expecting growth that didn't materialise, True-Down reclaims the cost difference. Always explore True-Down if you have 15%+ over-licensing.
Conclusion: Make True-Up a Strategic Moment, Not a Surprise
Microsoft True-Ups are where licensing strategy intersects with budget impact and vendor power dynamics. The organisations that avoid the seven costly mistakes and navigate True-Up smoothly share one trait: they plan ahead. They gather data 90 days early. They model scenarios. They understand their SKU strategy. And they negotiate with clear information and realistic expectations.
The True-Up is also where Microsoft will pitch E7 upgrades and Copilot expansion. That's a legitimate conversation—E7 and Copilot may be right for your organisation. But only if you've evaluated them on technical merit and negotiated fair pricing, not because a field rep positioned them as table stakes during True-Up.
If your organisation is within 90 days of a True-Up and you haven't started planning, now is the time. Engage your governance team, pull usage data, and model your scenarios. The difference between rushed preparation and strategic planning is often £50,000–200,000 in avoidable costs.
Let our experts guide your True-Up strategy
Redress Compliance specialises in Microsoft EA negotiation and True-Up optimisation for enterprises across EMEA and North America