The Complete Guide to Microsoft Enterprise Agreement True-Up: Process, Pitfalls, and Cost Reduction Strategies

1. Introduction: What Is the EA True-Up and Why It Matters

An Enterprise Agreement (EA) is a volume licensing contract with Microsoft that covers a minimum of 500 users or devices and requires a three-year term commitment. Unlike simple perpetual licenses, an EA includes an annual reconciliation process called a True-Up. This True-Up is the mechanism by which Microsoft compares the quantities you licensed in your EA against the actual usage you deployed during the year. If usage exceeds your licensed quantities, you owe additional payment. If usage falls short—which is rare—Microsoft may allow True-Down in limited circumstances, though their default position is a one-way ratchet: licenses can only go up or stay flat, never down.

Most organizations view True-Up as a straightforward administrative task: Microsoft sends a reconciliation report, accounting approves the additional charges, and the bill gets paid. This perception is fundamentally flawed. The True-Up is the single most important financial checkpoint in your EA relationship. It is when Microsoft recalculates what you owe, when your usage patterns become formally documented, and when you have maximum leverage to negotiate not only the True-Up charges themselves, but also renewal terms, discount rates, and SKU mix. Organizations that treat True-Up as pure administration typically overpay by 15 to 25 percent compared to peers who approach it strategically.

The True-Up timing also aligns with critical moments in your EA lifecycle. Your third-year True-Up occurs just as your three-year agreement approaches renewal. This synchronization creates a unique negotiation window. Microsoft field teams, driven by fiscal year Q4 targets (April to June in Microsoft's calendar), are highly motivated to secure renewal commitments and new seat commitments at this moment. Sophisticated buyers leverage this timing to negotiate both True-Up terms and renewal discount rates simultaneously, often achieving 20 to 35 percent better pricing than if these negotiations were treated separately.

2. How the EA True-Up Works: The Mechanics

The True-Up mechanics involve three parallel streams of data: your EA licensing baseline, your active usage deployment, and Microsoft's monitoring telemetry. Your EA baseline is the quantity of each license SKU you purchased in your original EA contract. For example, your EA might specify 2,500 Enterprise Mobility + Security (E3) seats, 800 Microsoft 365 Enterprise (E5) seats, and 150 Azure Reserved Instances (a different class of commitment). This baseline is locked at the time you sign the EA agreement and remains static until you modify it through a True-Up or mid-term adjustment.

Your active usage deployment is what you actually deploy across your organization. This includes all the M365 SKUs you have assigned to users (E1, E3, E5, E7), all the standalone Copilot Pro licenses at $30 per user per month, all your Azure consumption measured in vCPU-hours or storage gigabytes, and all your other licensed products. Microsoft monitors this deployment through multiple telemetry channels: direct assignment in your M365 admin portal, Azure consumption APIs, and in some cases, third-party software asset management data if you've integrated it with Microsoft.

At the True-Up checkpoint, Microsoft compares these two data sets. If your active usage equals or falls below your baseline, you owe nothing for that product line. If your usage exceeds your baseline, you owe payment for the overage quantity multiplied by the pro-rated unit cost. The pro-ration is significant: if your EA anniversary is in month six of a calendar year, and you added 100 new E5 seats in month three, you typically pay for only nine months of true overage (months three through eleven), not the full 12 months. However, once a license is added in the True-Up, it becomes part of your new baseline for subsequent years. This is the ratchet mechanism Microsoft uses: your baseline never decreases, so each year's True-Up sets the floor for next year's baseline.

Understanding the unit cost calculation is essential for predicting your True-Up liability. Your EA includes an agreed-upon discount off list price. If list price for E5 is $240 annually and your EA discount is 15 percent, your effective cost is approximately $204 per seat per year. In a True-Up, you pay this same discounted rate for overages, pro-rated to the months used. If you add 100 E5 seats in month three of a June anniversary year, you owe approximately 100 × $204 × 0.75 (nine months pro-ration) = $15,300 in additional charges. However, there is complexity: some customers negotiate True-Up rates separate from the baseline EA discount, often at less favorable terms (10 to 12 percent discount instead of 15 percent). Always clarify your True-Up pricing terms with Microsoft before the reconciliation.

3. The True-Up Timeline: Step-by-Step Calendar

Understanding the True-Up timeline is critical because each milestone represents a decision point where you can influence the outcome. Microsoft's standard timeline runs from 120 days before your EA anniversary through 30 days after.

120 Days Before Anniversary (Discovery Phase): This is when you should begin conversations with your Microsoft account team about expected usage changes. If you know you are planning to add 500 new employees to your organization, or if you are migrating Azure workloads that will consume significant new capacity, raise this with Microsoft now. This conversation achieves several goals: it gives you a read on Microsoft's appetite for negotiating True-Up terms, it allows you to understand the cost impact before charges appear on your bill, and it signals to Microsoft that you are engaged and thinking strategically about your licensing.

90 Days Before Anniversary (Planning Phase): This is when Microsoft typically initiates formal discussions about anticipated changes. They will request that you certify your expected user and device counts for the coming year. Do not take this request lightly. This is your opportunity to provide accurate data and to flag any major deployments. If you underestimate and end up with a huge True-Up six months later, you cannot go back and renegotiate. Conversely, if you overestimate, you may increase your baseline unnecessarily and lock yourself into higher costs for future years.

60 Days Before Anniversary (Review Phase): Microsoft will provide you with a preliminary True-Up calculation showing estimated additional charges. This is your critical review window. This is when you audit their usage data against your own records, challenge any discrepancies, and flag any license optimization opportunities. For example, if you have deployed more E1 seats than E3 seats, but your EA baseline allocates heavy E3 inventory, you may be able to trade down some E3 licenses to E1 and reduce your True-Up liability. It is also at this stage that you should initiate discussions about discount rates, particularly if this is your third-year True-Up and you are approaching renewal. Microsoft is highly motivated to lock in renewal commitments at this moment, and they have flexibility in their pricing that is unavailable at other times.

30 Days Before Anniversary (Finalization Phase): This is your last window to make changes to the True-Up order before it becomes binding. Microsoft will provide a final reconciliation number, and you will either accept it or request adjustments. If you have identified license optimization opportunities in the prior phase, these should be processed now. If you are negotiating renewal terms, these should be addressed now. Once your True-Up order date passes, you have limited recourse to challenge the charges, and your baseline is reset for the following year.

The timing alignment with Microsoft's fiscal year is crucial. Microsoft's fiscal year runs July 1 through June 30. Q4 is April through June. Many EA anniversaries fall in this window, which means your True-Up is being processed during Microsoft's highest-pressure revenue period. Account teams have quotas, and they are incentivized to secure new commitments, higher discount tiers, or larger baseline increases. This is when they are most willing to negotiate. Conversely, if your EA anniversary falls outside this window (July through March), Microsoft's account teams have less quota pressure, and they are less motivated to negotiate aggressively. Timing your renewal negotiations to align with Q4 is a significant advantage.

4. What Licenses Are Covered in a True-Up

Not all Microsoft licenses are subject to True-Up. Understanding which products are included is critical for accurate forecasting. M365 user licenses are universally included: all E1, E3, E5, and the new E7 SKU are subject to True-Up. Copilot Pro ($30 per user per month) is increasingly showing up in True-Ups with no advance warning to customers, creating surprise charges. Azure consumption is included but tracked differently: instead of per-seat reconciliation, Azure is reconciled on a consumption basis (vCPU-hours, storage gigabytes, data transfer), measured through Azure Resource Manager telemetry.

Standalone Defender licenses (Defender for Cloud, Defender for Office 365) are included. Some Defender components are bundled into E5 and E7 (Defender XDR is included in E5), but advanced features like Sentinel (Security Information and Event Management) are typically add-ons, tracked separately, and subject to consumption-based billing rather than per-seat reconciliation. Windows Enterprise E3 and E5 (formerly Windows 10/11 Enterprise) are included and subject to per-device reconciliation. Power Platform licenses (Power Apps, Power Automate) are included if they are part of your EA. Dynamics 365 user licenses are included. Project and Visio user licenses are included.

What is notably NOT included in typical EA True-Ups: server licenses (SQL Server, Windows Server) are often sold separately under Server/Cloud Enrollment (SCE) agreements, not EAs, and follow a different reconciliation model. Perpetual on-premises software licenses purchased through Software Assurance (SA) programs follow their own renewal cycle. Office 365 Consumer subscriptions (if any) are not part of EA and are not subject to True-Up. However, this boundary between EA and non-EA products is increasingly blurred. Microsoft is actively pushing customers toward unified EA agreements that bundle everything, which simplifies the contract structure but concentrates risk into a single reconciliation event.

5. Calculating Your True-Up: A Practical Framework

True-Up calculation follows a straightforward formula: (Actual Usage – Licensed Quantity) × Unit Cost × Pro-Ration Factor = True-Up Charge. However, the devil is in each component's definition.

Actual Usage Definition: This is where Microsoft's interpretation diverges from customer expectations. For M365 licenses, "actual usage" is the quantity of users who have been assigned a license at any point during the measurement period. It is not unique concurrent users; it is cumulative assignments. If you assigned 100 E5 licenses in January, 50 more in March, and 75 more in October, your actual usage count is 225 E5 seat-months (not 225 unique users, but seat-months summed across all months). This is a critical distinction. If you have high employee turnover or seasonal hiring, your actual usage can far exceed your steady-state headcount because each new assignment is counted in the cumulative total.

Licensed Quantity Definition: This is typically the quantity specified in your original EA agreement, unless you have made interim adjustments. However, if you have previously undergone True-Ups that resulted in overage charges, those overages reset your baseline. For example, if your original EA allocated 1,000 E3 licenses and your first year True-Up found 1,100 E3 users, your new baseline becomes 1,100 E3. Your second year True-Up will compare actual usage to this 1,100-license baseline, not your original 1,000.

Unit Cost: This is the negotiated discount rate applied to list price. However, as noted earlier, True-Up unit costs sometimes differ from baseline EA unit costs. Always request explicit clarification: are True-Up overages charged at the same discount rate as your baseline EA licenses, or at a different (typically less favorable) rate? A one-percent difference in discount rate can mean tens of thousands of pounds in additional charges across your True-Up, particularly if you have significant overages.

Pro-Ration Factor: This is where timing matters. If your EA anniversary is June 30, and you added a license in month six (December), you pay for seven pro-rated months (December through June). If you added the license in month one (July), you pay for the full 12 months. However, different products have different pro-ration rules. For cloud-based products like Microsoft 365, pro-ration is typically counted in actual calendar days. For server licenses or on-premises products, pro-ration may be counted in calendar months. Always confirm the exact pro-ration methodology before accepting a True-Up bill.

A worked example: Your organization has a June 30 EA anniversary. Your baseline is 2,000 E5 licenses at a 15 percent discount (list price $240, your net cost $204). During the year, you added users steadily, and your June reconciliation shows 2,200 actual E5 seat-months assigned. The monthly average is 200 new E5 assignments spread across the year. Your True-Up overage is 200 seats. However, because these were added gradually throughout the year, the average pro-ration is approximately 0.5 (half the year used on average). True-Up charge: 200 × $204 × 0.5 = $20,400. But here is the critical point: your new baseline for next year is 2,200 E5 licenses, not 2,000. If you continue to assign E5 at the same rate next year, you will have consumed your baseline and will have zero True-Up overage next year. But if you need to add more users, every additional E5 above 2,200 will again be subject to True-Up charges, now at a 2,200-license baseline. This baseline ratchet is how Microsoft systematically increases your licensing spend year over year.

6. The True-Down Myth: What Microsoft Will and Won't Allow

One of the most persistent misconceptions about True-Up is that if your usage falls short of your licensed baseline, Microsoft will allow you to reduce your baseline. This is the True-Down myth, and it is almost entirely false. Microsoft's default position is a rigid one-way ratchet: baselines can increase, but they rarely decrease.

Why does Microsoft enforce this policy? First, they want to lock in high baselines because high baselines create a revenue floor in future years. If your baseline is 2,000 E5 licenses and you only use 1,500, Microsoft prefers to keep the 2,000 baseline and hope that next year you will consume more, rather than reduce the baseline to 1,500 and watch it shrink further if consumption remains static. Second, reducing baselines creates administrative complexity and bad optics. If Microsoft allows True-Down, they effectively admit that the customer over-licensed, which is a poor negotiating message. Third, many customers who appear to under-utilize in a given year are actually planning for future growth. If Microsoft reduces baselines and then that growth materializes, the customer will be back negotiating for a baseline increase, which creates unnecessary friction.

There are rare exceptions to the no-True-Down rule. The most common exception is a major organizational change: if you sell off a business unit that consumed 50 percent of your licensed seats, Microsoft may agree to a corresponding baseline reduction. Another exception is if you have fundamentally misallocated your baseline during initial EA setup. For example, if you specified 2,000 E5 seats but only ever intended to use 500, and this was clearly documented in writing at the time of agreement, Microsoft may permit a correction. However, these are exceptions, not the rule. In our experience managing 200+ EA True-Ups, we have succeeded in negotiating True-Down in fewer than 5 percent of cases, and only when backed by compelling documented evidence of material change in business circumstances.

The implication is clear: overestimating your baseline during EA setup is a costly error. Once you lock in a high baseline, you are paying for it every year, even if you do not use it. This is why the planning phase (90 days before anniversary) is so critical. You must ensure your baseline projections are conservative but realistic. Do not inflate numbers to appear to be growing. Do not game the system by deploying temporary licenses to justify a higher baseline. These tactics inevitably result in future years of overpayment or negotiation friction.

7. Seven Common True-Up Pitfalls (and How to Avoid Each)

Pitfall 1: Not Tracking Mid-Year Deployment Changes. Many organizations deploy new users or devices mid-year without formally notifying procurement. A new department joins, a contractor is onboarded, a cloud migration happens, and suddenly dozens or hundreds of new licenses are assigned in your M365 admin portal. Microsoft sees this immediately through telemetry, but you may not realize it until the True-Up bill arrives. Prevention: implement a monthly reconciliation process where your M365 administrator runs a user license assignment report and sends it to procurement. Establish a change control process: any new license assignment above a threshold (e.g., 10 seats) requires procurement approval.

Pitfall 2: Confusing Frontline Worker Licenses with Standard E Licenses. Microsoft has introduced a separate category of lower-cost licenses for "firstline workers" (typically warehouse, retail, field service staff). Frontline Worker E3 and E1 are cheaper than standard E3 and E1, but they have different feature sets. Many organizations mistakenly assign standard E3 licenses to frontline workers, paying standard E3 rates for what should be Frontline Worker E3. Conversely, some organizations assign Frontline E3 to roles that require standard E3 features, then face feature gaps. Prevention: clearly document which roles should be assigned which SKU. Work with your Microsoft account team to classify your user population by role, then establish assignment policies (via Automatic Group Licensing in M365 if possible) to ensure correct SKU assignment.

Pitfall 3: Accidental Copilot Pro Activation. Microsoft has made it trivially easy for users to activate Copilot Pro ($30 per user per month) from the M365 admin portal. Many organizations have had hundreds of users activate Copilot Pro during a pilot phase, then left them active after the pilot ended. At True-Up, Microsoft discovers these active assignments and bills the organization for the full month/year. Prevention: disable the ability for users to self-activate Copilot Pro in your tenant settings. If you run a Copilot pilot, explicitly allocate a pilot cohort, assign Copilot Pro only to that cohort, and then deactivate all licenses at the end of the pilot. Do not leave pilot licenses active hoping they will be used.

Pitfall 4: Ignoring Azure Consumption Volatility. Azure consumption is measured continuously, not at annual checkpoints like M365 licenses. Your team may decide to migrate a large workload to Azure in month eight of your fiscal year, causing your Azure consumption to spike dramatically. At True-Up, you will owe for that full consumption, even though you only used the resources for five months. If you have Azure Reserved Instances (RIs) or commitment-based pricing, your True-Up calculation is different: you may owe nothing if your usage fits within your reserved capacity. Prevention: monitor Azure consumption monthly. If you see significant increases, proactively engage your Microsoft account team to discuss True-Up implications and to explore whether Azure Reserved Instances or other commitment-based pricing options could reduce your liability.

Pitfall 5: Not Accounting for License Transfers and Movements. In some organizations, licenses are moved between users frequently. A role holder leaves, their E5 license is reassigned to their replacement, and so on. Microsoft's telemetry captures cumulative assignments, not unique users. If you move the same E5 license to 10 different people over the course of a year, you may be charged for 10 E5 seat-months, not one. Prevention: be aware that moving licenses is functionally equivalent to adding new licenses from Microsoft's perspective. If you rely heavily on license reuse due to high turnover, factor this into your baseline projections. A headcount of 500 with 30 percent annual turnover may require 650 license seat-months due to reuse. Design your baseline accordingly.

Pitfall 6: Underestimating True-Up Charges and Having No Budget Contingency. Many finance departments budget for True-Up based on the prior year's charges, assuming a linear increase. In reality, True-Up is highly variable depending on hiring, deployments, and organizational changes. If you budget £100,000 but the actual True-Up is £250,000 due to an unexpected business acquisition or expansion, you create a mid-budget crisis. Prevention: build a 25 to 50 percent contingency buffer into your True-Up budget, even in years where you expect minimal changes. Communicate to your finance team that True-Up is unpredictable and that mid-year budget adjustments may be necessary.

Pitfall 7: Missing the Negotiation Window. The most expensive pitfall is treating True-Up as a passive billing event rather than an active negotiation opportunity. If you simply accept Microsoft's True-Up calculation without question, you forfeit the chance to negotiate not only the True-Up terms, but also renewal rates, SKU mix, and discount tiers. Prevention: treat the 90-day-to-30-day window as a negotiation event. Engage your Microsoft EA advisory specialists at the 90-day mark. Request detailed usage reports and challenge any anomalies. If this is your third-year True-Up and you are approaching renewal, explicitly link True-Up negotiations to renewal rate discussions. Use the True-Up as leverage to extract better terms on your renewal.

8. Strategic True-Up: Turning a Cost Event into a Negotiation Lever

While most organizations view True-Up as a pure cost, sophisticated buyers view it as a negotiation event. The strategic approach involves several tactics that collectively can reduce your true cost by 20 to 35 percent over a three-year cycle.

Tactic 1: Baseline Optimization Before True-Up. In the 60-day review phase, before Microsoft finalizes the True-Up, audit your deployed licenses against your organizational needs. Do you have departments or business units that can shift from E5 to E3, reducing your E5 overage? Can you shift users from perpetual licenses to cloud-based licenses to reduce complexity? Can you consolidate redundant products (multiple security tools) into Microsoft's unified stack to eliminate add-on expenses? Each of these optimizations reduces your True-Up liability while also simplifying your licensing for future years. The cost of this optimization is often just a few days of IT and procurement time, with payoff in the tens of thousands of pounds.

Tactic 2: Align True-Up Negotiation with Renewal Timeline. If this is your third-year True-Up, you are within 12 months of your EA anniversary. Microsoft knows this. They know that after three years, you will need to renew, and they are motivated to retain you. This is your maximum leverage point. Instead of negotiating True-Up and Renewal separately, negotiate them as a package. Tell Microsoft: "We will approve a true-up for our current year overages, but only if you agree to [specific renewal terms: discount rate, SKU mix, term length]." This bundling approach gives you 2-3x more negotiating power than if you handled each event separately.

Tactic 3: Use True-Up to Test Pricing Models. Many organizations do not realize they can negotiate the True-Up unit cost separately from their baseline EA rate. If your baseline EA discount is 15 percent but you are negotiating a large True-Up charge, ask Microsoft to apply an even better rate (17 to 20 percent) to the True-Up, in exchange for a three-year renewal commitment at the current baseline rate. This creates a win for both parties: Microsoft gets a committed renewal, and you get a discounted rate on the True-Up overage. This tactic is particularly effective in Q4 (April-June) when Microsoft account teams are trying to close deals before fiscal year-end.

Tactic 4: Leverage Competitive Alternatives in Your Negotiation. Before accepting a True-Up bill, have a conversation with your incumbent software vendors or competitive alternatives. If you are considering Google Workspace, Okta, or other non-Microsoft identity solutions as part of a broader platform evaluation, mention this to Microsoft. If you are considering Amazon WorkSpaces or Citrix for desktop delivery instead of Windows Enterprise + Microsoft Teams, mention this. The mere suggestion that you are evaluating alternatives often prompts Microsoft to offer significant pricing concessions on your True-Up. Microsoft's goal is to prevent logo loss, and they will often discount aggressively to avoid this risk.

Tactic 5: Consolidate Your Licensing Under a Single EA. Many large organizations have multiple EA agreements with Microsoft: one managed by IT, one by Finance, one purchased through a reseller, etc. This fragmentation weakens your negotiating position. Microsoft will not give you their best pricing on a 500-seat EA when you have multiple agreements totaling 3,000 seats. Consolidating these into a single EA, ideally with a single reseller partner, gives you more volume leverage and a more coherent negotiating position. The True-Up process is a good time to propose this consolidation, as it forces a formal renegotiation anyway.

9. Copilot and AI in the True-Up: New Complexity in 2026

Copilot Pro ($30 per user per month) is increasingly becoming a True-Up liability for organizations that have not carefully managed its deployment. When Microsoft first introduced Copilot Pro, many customers ran pilots or trials without establishing clear governance. Users who found value in Copilot kept it activated, and organizations lost track of how many licenses were actually in use. At True-Up, Microsoft discovers these active assignments and bills the organization retroactively.

The complexity is compounded by the fact that Copilot Pro is not bundled into E5 or E7 in most cases (though it is included in E7, the top SKU). Instead, it is a separate $30-per-user-per-month add-on. For organizations with 5,000 E5 users and Copilot Pro activated on 500 of them, this represents 500 × $30 × 12 = £180,000 in annual Copilot costs. If this was never formally approved or budgeted, the True-Up bill comes as a shock.

Microsoft is actively pushing E7 adoption as a way to consolidate Copilot and other AI features into the bundle. E7 includes Copilot Pro plus advanced compliance and AI features that were previously add-ons. However, E7 is significantly more expensive than E5 (rough estimates: 15 to 30 percent premium). For most organizations, upgrading all users to E7 to "free" Copilot is not financially rational. The better approach is to be intentional about Copilot deployment: designate specific roles or departments that should have Copilot Pro, assign it only to those populations, and treat it as a formal part of your baseline, not a pilot that sprawls.

Prevention for the True-Up: disable user self-service activation of Copilot Pro in your M365 admin center. Require that any Copilot deployment be formally approved by procurement and tracked in your license inventory system. During your True-Up planning phase, specifically review your Copilot Pro activation status and ensure you are budgeting for it as a line item. If you have Copilot Pro activated on more users than you intended, use the True-Up window as a forcing function to clean it up: deactivate unintended licenses, document your intended Copilot population, and update your baseline for next year to reflect your true Copilot strategy.

10. True-Up for Azure and Hybrid Infrastructure

Azure True-Up is fundamentally different from M365 True-Up because Azure is consumption-based, not seat-based. Instead of reconciling licensed quantities against assigned users, Azure reconciliation measures actual consumption (vCPU-hours, storage gigabytes, data transfer terabytes) against your committed capacity or reserved capacity.

If you have Azure Reserved Instances, your True-Up is relatively simple: your actual consumption is compared to your reserved capacity. If you consumed less than your reservation, you have no additional charge. If you consumed more, you pay for the overage at the on-demand rate (which is typically significantly higher than your reserved rate). If you use commitment-based pricing (like Azure Hybrid Benefit or Azure Savings Plan), your True-Up calculation measures your actual spend against your committed amount. Again, overage is billed at on-demand rates.

The key to controlling Azure True-Up is proactive capacity planning. Monitor your Azure consumption monthly. If you see consumption trending toward your reserved capacity limit, proactively purchase additional reserves before the True-Up window. The cost of purchasing additional reserves now is typically lower than paying for on-demand overage at True-Up. Additionally, Azure Reserved Instances have a return window (typically 30 days): if you over-purchase, you can return unused reserves for a refund, subject to terms. This flexibility allows you to be conservative in your planning without being locked into excessive costs.

Hybrid scenarios—combining on-premises and Azure infrastructure—add complexity. If you have SQL Server databases running both on-premises and in Azure, your SQL Server licensing may span multiple billing models: Software Assurance on-premises, and Azure commitment in the cloud. At True-Up, you need to ensure these are being reconciled correctly and that you are not double-paying for capacity. This is a common source of overpayment in hybrid environments. Ensure your Microsoft account team understands your hybrid architecture and is reconciling your SQL licensing across both on-premises and Azure at True-Up time.

11. Right-Sizing Before Your True-Up Submission

The 60-day window before True-Up submission is your opportunity to conduct a comprehensive audit of your licensing and make changes before the new baseline is locked in. Right-sizing involves four key activities: usage analysis, SKU optimization, feature audit, and cost-benefit review.

Usage Analysis: Run a report of all licensed users by SKU in your M365 admin center. This report should be cross-referenced with your HR system to identify any orphaned licenses (users who have left the organization but still have licenses assigned) or duplicates (users with multiple license assignments). Orphaned licenses are pure waste and should be deactivated immediately. Every orphaned E5 license you deactivate before True-Up reduces your future baseline, saving potentially £200+ per user per year.

SKU Optimization: Analyze which features each user cohort is actually using. Your E5 users may primarily use email and SharePoint, with minimal use of E5-exclusive features like advanced threat protection or compliance tools. Those users could be downgraded to E3, reducing per-user cost from ~£240 to ~£170. Conversely, some of your E3 users may be power users of Copilot, advanced security, or compliance features that are only in E5. Identify these populations and consider upgrading them to E5 or E7, but only if the cost is justified by feature usage.

Feature Audit: Review your actual usage of standalone add-ons like Defender for Cloud, Sentinel, or Power Platform licensing. Many organizations purchase these licenses based on theoretical need, then never fully deploy them. If you have purchased Sentinel capacity but are only using a fraction of it, you may be able to reduce your commitment before True-Up. Conversely, if you are consuming more Sentinel or Defender capacity than you have licensed, adjust your commitment upward before the True-Up bill forces it.

Cost-Benefit Review: For any license you are considering removing or modifying, conduct a quick cost-benefit analysis. Is the cost of the license justified by the value it is delivering? Are there alternative tools that deliver the same value at lower cost? This is the moment to make strategic decisions about whether Microsoft is still the right choice for specific use cases, or whether unbundling to best-of-breed alternatives makes financial sense.

12. Third-Year True-Up: EA Renewal Alignment

Your third-year True-Up is special because it coincides with your EA renewal decision point. After three years, your initial EA term expires, and you must decide whether to renew with Microsoft, switch vendors, or renegotiate terms with Microsoft. This convergence creates maximum leverage for negotiation.

Microsoft field teams know that the third year is a retention risk moment. They also know that your True-Up negotiations are happening at exactly this moment, when you are most engaged with your licensing. This is why Microsoft account teams are most willing to negotiate aggressively during third-year True-Ups, especially if they fall in Q4 (April-June). Use this moment strategically.

Before your third-year True-Up, conduct a comprehensive competitive evaluation. Request pricing from Google (Google Workspace), AWS (WorkSpaces, identity services), or Okta (identity platform) for equivalent capabilities. Request pricing from lower-cost Microsoft resellers for comparison. Document any capability gaps or integration challenges you have experienced with Microsoft products over the three years, and evaluate whether alternative solutions address these gaps. Present this evaluation to Microsoft as part of your renewal negotiation. The conversation becomes: "We are very interested in renewing, but we want renewal pricing that reflects our three years of loyalty and our expanded consumption. We are also evaluating [specific alternatives] as part of our platform strategy. What can you offer to retain us?"

This conversation, timed to your third-year True-Up, typically results in 20 to 40 percent better pricing than if you simply renewed at Microsoft's list rates or historical discounts. Microsoft's retention motivation is high, and their flexibility is greatest when renewal is at risk.

13. How Independent Advisors Add Value at True-Up

Organizations often manage True-Up internally, without external support. However, independent advisors add value in three critical ways: usage audit, negotiation support, and contract structure advice.

Usage Audit: An external advisor can conduct an objective audit of your licensing usage, often identifying 10 to 20 percent in hidden optimization opportunities that internal teams miss. This is not a reflection on your IT team's competence; it is simply that your team is embedded in the day-to-day operations and lacks the external perspective that an advisor brings. An advisor can often pay for their own cost through the optimizations they identify.

Negotiation Support: Microsoft account teams are trained negotiators with extensive experience in getting customers to accept higher pricing and larger baselines. An independent advisor, representing your interests and with no relationship history with Microsoft, can take a harder negotiation stance than your internal team might be comfortable with. This dynamic—internal team managing the relationship, advisor pushing hard on pricing—often results in 10 to 20 percent better pricing than internal negotiation alone.

Contract Structure Advice: Advisors with experience across multiple EAs can offer insights on contract structures, term lengths, discount escalation clauses, and renewal mechanics that optimize your long-term cost. Many organizations do not realize they can negotiate True-Up unit costs separate from baseline EA costs, or that they can tie renewal rates to usage thresholds. An advisor brings this expertise to the table, often identifying creative structures that benefit both you and Microsoft.

The best advisors operate on a fee-for-service basis (not commission from Microsoft or resellers), which ensures their advice is truly independent. If you are managing a multi-million-pound EA True-Up with significant organizational changes or growth, engaging an independent advisor for the 90-day-to-30-day window is typically a worthwhile investment.

14. Checklist: 15-Step True-Up Preparation Framework

To ensure you do not miss critical steps, use this 15-step framework as your True-Up preparation guide:

1. 120 days before anniversary: Schedule initial conversation with Microsoft account team about anticipated changes.
2. Mark your calendar with all four milestone dates (120, 90, 60, 30 days before anniversary).
3. Conduct a current-state license audit across M365 and Azure.
4. Identify and deactivate any orphaned or duplicate licenses.
5. Classify your user population by role and document the correct SKU for each role.
6. Review Copilot Pro activation status and disable self-service if it is enabled.
7. 90 days before: Provide Microsoft with formal certification of expected user and device counts for the coming year.
8. Request a preliminary True-Up calculation from Microsoft.
9. Cross-reference Microsoft's usage data against your own records; challenge any discrepancies.
10. Identify SKU optimization opportunities (E5 to E3 downgrades, Frontline Worker recategorization, etc.).
11. Determine whether this is your third-year True-Up; if so, begin renewal evaluation and competitive benchmarking.
12. 60 days before: Request detailed usage reports and consumption breakdowns by cost center or department.
13. Initiate formal negotiation conversations about True-Up pricing, renewal terms, and discount structures.
14. For Azure, review your reserved capacity and consumption forecasts; plan any additional reserves if needed.
15. 30 days before: Finalize the True-Up order and confirm all changes are reflected; ensure new baseline is documented for next year.

15. How Redress Compliance Helps + Call to Action

Redress Compliance has managed over 200 EA True-Ups across enterprises ranging from 500 to 50,000 users. In 2024-2026 alone, we identified an average of 18 percent in overpayment across these engagements, with an average identified saving of £2.4 million per organization. The pattern is consistent: organizations that approach True-Up with independent advisory support and strategic preparation achieve 20 to 35 percent better outcomes than those managing it alone.

Our Microsoft EA advisory specialists work with you during the critical 90-day-to-30-day window. We audit your usage, identify optimization opportunities, benchmark your discount rates against market peer data, and lead negotiations with Microsoft on your behalf. We focus on three outcomes: reducing your True-Up charges, securing better renewal terms, and optimizing your SKU mix for your business needs.

Whether you are planning a True-Up, managing one now, or preparing for a renewal, our Microsoft EA advisory specialists team can help. We have the data, the expertise, and the negotiating track record to deliver results. Let us help you turn your True-Up into a cost control and negotiation event, not just a billing event.