LocationsResourcesContact
📅 Book a Meeting
Microsoft Licensing — True-Up Best Practices

Microsoft Licensing True-ups: How to Avoid Costly Mistakes

The annual true-up process is pivotal for organisations with Microsoft Enterprise Agreements. It is the yearly reconciliation during which you must report any increase in usage of Microsoft products — additional licences, new users, or extra software deployments — since your last agreement baseline. Managed correctly, a true-up is routine and predictable; handled poorly, it can result in surprise bills, compliance penalties, or wasted expenditure.

📅 July 2025⏱ Microsoft EA Compliance Guide✍️ Fredrik Filipsson

Understanding the True-Up Process

Under a typical Microsoft Enterprise Agreement (EA), you commit to an initial licence count for a set number of users, devices, and products. The true-up is an annual report and purchase in which you declare usage above the original commitment. For example, if you licensed 100 product users but deployed 120 during the year, the true-up is when you purchase licences for those 20 additional users retroactively.

True-ups ensure you pay for what you used and keep your licensing compliant. Most EAs require increases to be reported — you generally cannot reduce licence counts mid-term. Reductions or "true-downs" must wait until agreement renewal.

📋

Annual Usage Reporting

You must formally report any increases in licences, users, or other metrics covered by the EA — typically 30 days before your agreement anniversary date.

💳

Payment for Overuse

You are billed for incremental licences or subscriptions added during the year. These are typically prorated to align with the agreement term (e.g. an added user licence billed for the remaining months of the year).

Compliance Assurance

The true-up is your opportunity to ensure licensing is in line with actual deployments. It effectively resets your compliance position, aligning licences with current usage going forward.

Failing to execute the true-up properly can have serious consequences. If you don't account for additional usage, you risk being non-compliant — which could lead to penalties in a software audit and back payments for unlicensed use. Conversely, if you overpay or overprovision "just in case," you waste budget on unused licences. The goal is a precise true-up — no shortfall, but no excess spend.

Learn more about the full Microsoft licensing framework

Microsoft Licensing Guide →

Common True-Up Mistakes to Avoid

Microsoft true-ups involve many moving parts, and several pitfalls can trip up even experienced IT teams. Here are the five most common mistakes.

Mistake #1

Lack of Accurate Tracking

The most fundamental mistake is not having an up-to-date inventory of your Microsoft software deployments and user counts. If you aren't tracking new installations or user onboarding throughout the year, it's easy to miss something at true-up. This can lead to an unpleasant surprise when an audit finds unlicensed deployments that were never reported.

A company deploys several new SQL Server instances for projects but doesn't update its licence records. At true-up, they under-report and later face a compliance penalty for those instances.
Mistake #2

Last-Minute Rush

Procrastinating until the true-up deadline to gather data often results in errors or omissions. Rushed reports might overlook deployed software, miscount users, or lack the documentation to substantiate the numbers. A last-minute scramble means you have little time to vet the data or explore cost-saving adjustments.

Mistake #3

Overlooking Cloud Services

Many organisations focus on on-premises software but forget that cloud services (Azure VMs, additional Microsoft 365 subscriptions) acquired during the year may also need to be true-upped if they're under the EA. Ignoring cloud usage growth is a frequent mistake.

An IT department adds several Azure virtual machines for a new app, assuming Azure's pay-as-you-go covers it. If those VMs are part of an EA enrolment (such as an Azure plan under EA), they must be reported in the true-up. Not doing so under-reports usage.
Mistake #4

No Internal True-Up Preparation

Some organisations view the true-up as a one-time annual event rather than a year-round process. Without interim checks, they may discover too late that they've exceeded entitlements or purchased licences they didn't deploy (which could have been deferred). This reactive approach leads to either compliance gaps or wasted spend.

Mistake #5

Assuming True-Up Can Reduce Licences

A common misconception is that the true-up is an opportunity to remove or reduce licence counts if usage has decreased. In reality, an EA true-up only accounts for increases. If your usage decreased (e.g. you offboarded 50 users), you generally cannot credit or "true-down" those licences until the EA renewal. Organisations that don't understand this may overestimate savings or fail to plan for the fixed costs on unused licences until renewal.

Read Microsoft Licensing Metrics (Cores, Users, Devices) to understand which metrics are tracked in each true-up and how to count them correctly.

Best Practices to Manage True-Ups Effectively

Avoiding costly true-up surprises comes down to diligent licence management and proactive planning. Here are eight key practices to ensure your true-ups go smoothly and align with actual needs.

1

Maintain an Accurate Inventory Year-Round

Don't wait for the true-up date to discover what's deployed. Maintain a continuous software asset inventory — track every new server installation, user addition, or cloud service subscription as it happens. A centralised asset management system or licensing database ensures your true-up report is prepared in advance, with all necessary data readily available.

2

Conduct Regular Internal Licence Audits

Treat every quarter (or at least mid-year) as a mini true-up. Reconcile licence entitlements versus actual usage on a regular schedule. Internally auditing your deployments lets you spot discrepancies early — discovering that a development team installed Visio on 10 PCs without licences, or that 30 provisioned Office 365 accounts belong to former employees. Early detection lets you address issues before the official true-up.

3

Leverage Tools for Licence Tracking

Microsoft provides tools such as the Microsoft 365 Admin Centre reports, Azure Cost Management, and the Microsoft Assessment and Planning (MAP) Toolkit. Third-party Software Asset Management (SAM) tools can automate tracking across on-prem and cloud environments, generating reports on user counts, installations, and consumption. Automation reduces human error and is far cheaper than a true-up mistake or compliance fine.

4

Plan for Changes and Growth

Anticipate how organisational changes affect licensing and budget accordingly. If you know a new project will require 50 SQL Server licences next quarter, or you're acquiring a company with 200 additional employees, start accounting now. Planning prevents "shock" true-up costs — you'll have set aside funds and negotiated better pricing for the expected additions.

5

Engage with Microsoft (and Your Advisors) Early

Maintain open communication with your Microsoft account manager or licensing reseller throughout the year. If you're unsure how a specific deployment is licensed under your EA, ask before deploying. Involve an independent licensing advisor if you have one — they can double-check counts and identify areas of concern. Early communication prevents misunderstandings and ensures no surprises when the true-up is finalised.

6

Start True-Up Preparation Early

Treat the true-up like a project with a timeline. Begin formal data gathering and reconciliation at least one to two months before the report is due. This provides buffer to resolve anomalies — if your inventory shows more usage than expected, you have time to investigate and take corrective action. Starting early ensures accurate and complete submission, avoiding last-minute mistakes.

7

Reclaim and Reallocate Before You True-Up

Identify unused or underused licences before submitting your true-up. Perhaps you have 50 Visio users on paper, but only 30 used it in the last 6 months — reassign those 20 licences to cover new needs instead of purchasing more. Check for dormant cloud subscriptions or installations that can be retired. Re-harvesting licences can significantly cut your true-up bill.

8

Consider Independent Expert Review

True-ups can be complex in large enterprises with many product deployments. Engaging an independent licensing expert or SAM consultant provides an extra layer of assurance. An expert might notice that SQL Server licences you're planning to true-up could be covered by existing licences with Software Assurance (via Licence Mobility) at no extra cost, or might suggest an EA amendment for a cheaper outcome.

A Microsoft true-up should never be a cause for panic. By treating licensing as a year-round responsibility — tracking usage, staying ahead of changes, and regularly auditing — your annual true-up becomes a straightforward confirmation of what you already know. The key to avoiding costly mistakes is proactivity.
An independent Microsoft licensing review before your true-up is the single highest-ROI step. Our Microsoft Optimisation Services cover licence inventory reconciliation, true-up preparation, compliance assessment, and cost-saving recommendations. Most engagements identify savings worth multiples of the advisory investment — turning your true-up from a risk event into a cost optimisation opportunity.

Microsoft Licensing Case Studies

See how we've helped global enterprises save millions on Microsoft EA renewals, true-ups, and licence optimisation.

View Microsoft Cases →

📂 Microsoft Licensing Case Studies

📊 EA Renewal Cases 🤝 Negotiation Cases 🏢 All Vendor Cases

🔧 Microsoft Advisory Services

💰 Licence Optimisation 📋 EA Optimisation 🤝 Contract Negotiation 🛡️ Audit Defence

📄 White Papers & Resources

📑 EA Benchmarking Report 📄 All White Papers ✍️ Blog & Insights

Need Help With Your Microsoft True-Up or EA Compliance?

Whether you need true-up preparation, licence inventory reconciliation, compliance assessment, EA renewal negotiation, or audit defence — our Microsoft licensing specialists deliver measurable savings and protect your interests as a fully independent advisor.

💡 Download our Microsoft licensing white papers for actionable strategies

View White Papers →
FF

Fredrik Filipsson

Co-Founder, Redress Compliance

Fredrik Filipsson brings over 20 years of experience in enterprise software licensing, including senior roles at IBM, SAP, and Oracle. For the past 11 years, he has advised Fortune 500 companies and large enterprises on complex licensing challenges, contract negotiations, and vendor management — consistently delivering outcomes that save clients millions across Oracle, Microsoft, SAP, IBM, Salesforce, Broadcom, and GenAI engagements.

View all articles by Fredrik →