EA Renewal License True-Up: A Practical Checklist

An EA renewal license true-up is the moment your Microsoft spend gets locked in for the next term, often three years. Whatever seat count and license mix you walk into that negotiation with becomes the baseline you pay against until the next renewal. If that baseline includes hundreds of unused E5 seats or a Power BI Pro allocation nobody touches, you are not just overpaying today, you are overpaying every month for the life of the agreement.

Most IT and procurement teams treat the true-up as a paperwork exercise: confirm current seat counts, sign, move on. The organizations that actually save money treat it as a rightsizing project with a hard deadline. The renewal date forces a decision either way, so it is the best forcing function you will get to clean up license sprawl before it gets contractually baked in.

This article covers what a true-up actually is, why renewals default toward waste, and a concrete process for walking into your renewal with real usage evidence instead of last year's numbers.

What happens in an EA true-up, exactly

An Enterprise Agreement true-up is the annual (and at renewal, multi-year) reconciliation between what you are licensed for and what you are actually using. Under an EA, you typically commit to a minimum seat count per product, and the true-up is where Microsoft or your licensing partner confirms whether your deployed count has grown, shrunk, or stayed flat.

At a renewal, this reconciliation carries more weight than a routine annual true-up. You are not just adjusting numbers within an existing term, you are setting the terms, tiers, and committed volumes for the next agreement period. Decisions made here are expensive to unwind mid-term.

Why renewals tend to lock in waste

A few patterns show up again and again in EA renewals:

• The "same as last year" default. Procurement often renews the existing mix with minor adjustments because nobody has the usage data to justify a bigger change.
• Growth assumptions padded in. Teams add a buffer "in case we hire," and that buffer becomes permanent seats nobody is tracking against actual headcount.
• Tier creep survives unnoticed. If E5 was rolled out broadly at some point, that tier often just carries forward into the new term without anyone asking whether usage supports it.
• The negotiation window is short. True-up conversations often start weeks, not months, before the deadline, which pushes teams toward accepting the status quo rather than doing a proper usage review.

None of this is malicious. It is what happens when a contractual deadline meets a lack of usage visibility.

Build your usage baseline before the negotiation starts

The single biggest lever in a true-up is walking in with real numbers instead of estimates. That means pulling usage data well before the renewal conversation, not during it.

What to pull

1. Assigned licenses per SKU, straight from the Microsoft 365 admin center or Entra ID.
2. Sign-in activity per user, using Entra ID sign-in logs (signInActivity via Microsoft Graph) to separate active accounts from dormant ones.
3. Feature-level usage for premium tiers: Power BI report views, Teams Phone calling minutes, Defender and Purview activity, so you can tell whether E5 seats are earning their price.
4. Stale and orphaned accounts: former employees, service accounts, and contractors whose access never got cleaned up but whose license is still billed.
5. Growth trend, actual headcount change over the last 12 months, so buffer requests are grounded in a real trajectory instead of a guess.

Turn the data into three simple buckets

Bucket	What it means	Renewal action
Active, right-tiered	Signed in recently, using features that match their license	Renew as is
Active, over-tiered	Signed in recently, but no premium feature usage in 60-90 days	Downgrade candidate before renewal
Inactive or orphaned	No sign-in in 60-90+ days	Reclaim seat, remove from true-up count

Even a rough pass through these three buckets, done a month or two before renewal, gives procurement a defensible number to negotiate with instead of "roughly what we had last year plus a bit."

Negotiating the renewal itself

Once you have a usage-backed baseline, the conversation with your reseller or Microsoft account team changes shape. A few things worth pushing on:

Right-size before you commit, not after

It is far easier to negotiate a lower committed seat count at renewal than to reduce it mid-term. If your data shows 15% of E5 seats have no premium feature usage, that is the moment to convert them, not six months into the new agreement.

Match tier mix to measured need

Rather than standardizing a whole tenant on one tier "to keep it simple," use your usage buckets to propose a split: E3 as the default, E5 for roles with demonstrated need for security, compliance, or analytics features. This is usually where the largest savings sit, since the E3-to-E5 price gap is substantial per seat.

Build in a true-up cadence, not just a renewal cadence

A three-year term is a long time to fly blind. Ask whether interim usage checkpoints, even informal ones, can be part of the agreement structure, so waste does not quietly rebuild itself between now and the next renewal.

Keep growth buffers honest

If the business genuinely expects headcount growth, build that into the negotiation with the actual trend data, not a round number picked because it sounds safe.

Making the next true-up easier than this one

The renewal itself is a one-time push, but the underlying problem, license assignment drifting away from actual need, keeps happening between renewals unless something structural changes.

Two things help most:

• Provisioning access and licenses from attributes (department, job title, location) instead of copying a colleague's setup, so new hires start at the right tier instead of the highest tier anyone happened to have.
• A standing view of usage versus assignment, checked regularly rather than reconstructed from scratch every time a contract deadline approaches.

If the next true-up starts from a clean, monitored baseline instead of three years of accumulated drift, it stops being a scramble and becomes a five-minute confirmation.

Where ServiceChanger fits

ServiceChanger's license module reads real Entra ID sign-in activity and keeps a contract and seat registry alongside it, so the three buckets above (active and right-tiered, active and over-tiered, inactive) are visible year-round instead of something you have to reconstruct in the weeks before a renewal deadline. It flags unused seats, under-utilized premium tiers, and expiring contracts, and gives right-sizing guidance on which seats to bring into the true-up conversation. That guidance is reporting and insight: ServiceChanger surfaces the evidence, the actual license changes still happen in the Microsoft admin center or through your licensing partner.

Because ServiceChanger also automates access assignment through ABAC, the rightsizing decisions you make at renewal, which roles genuinely need E5-tied features, become rules that keep new joiners and movers correctly licensed going forward, instead of drifting again before the next true-up.

FAQ

What is the difference between a true-up and a renewal? A true-up is the periodic reconciliation of licensed versus deployed seats within an existing agreement term. A renewal is the point where the entire agreement, including committed volumes and tiers, is renegotiated for the next term. The renewal true-up carries more weight because the numbers agreed there set your baseline for years, not months.

How far ahead should we start preparing for an EA renewal true-up? Start pulling usage data at least two to three months before the renewal deadline. That gives enough time to identify downgrade and reclaim candidates, validate them against roles that need premium features, and build a defensible number before negotiations start, rather than during them.

Can we reduce our committed seat count at renewal if usage has dropped? Yes, this is exactly the point in the agreement cycle where committed volumes can be adjusted. Reducing mid-term is typically harder or not possible, which is why the renewal is the highest-impact moment to align your license count with actual usage.

Does ServiceChanger handle the EA renewal negotiation for us? No. ServiceChanger gives you the usage data, seat and contract visibility, and right-sizing guidance to walk into the renewal with real numbers. The negotiation itself and any license or SKU changes happen through the Microsoft 365 admin center or your licensing partner.

Next step

If your EA renewal is coming up and you are not sure how many of your seats are actually earning their tier, that visibility gap is exactly what the ServiceChanger identity and access platform is built to close. Read more on license management or browse our cost coverage for more on getting Microsoft spend under control before it locks in.