The True Cost of a Forgotten License

The cost of unused license seats rarely shows up as a single alarming number. It shows up as one seat here, another there, quietly renewing month after month, until someone finally adds it all up and asks why the Microsoft 365 bill keeps climbing while headcount barely moved. A single forgotten E5 seat feels trivial in isolation. Multiply it across a few dozen leavers, some over-provisioned pilots, and a couple of departments that never cleaned up after a reorg, and it stops being trivial.

This article walks through the actual arithmetic of a forgotten seat: what it costs over a year, why it survives so long unnoticed, and where to look if you want to find your own version of it before the next renewal.

What "forgotten" actually means

A forgotten license is not always an obvious mistake. It usually falls into one of a few patterns:

• The leaver seat: someone left the company, their account was disabled or deleted for security reasons, but the license itself was never unassigned, so the seat sits reserved against your tenant's pool.
• The project seat: a contractor or a pilot group was licensed for a few months, the project ended, and nobody circled back to release the seats.
• The role-change seat: someone moved from a role that needed Power BI Pro or Teams Phone to one that doesn't, and their license tier followed them out of habit rather than out of need.
• The duplicate seat: a user has two accounts (a guest and a member, or a leftover test account) and both are licensed.

None of these are dramatic failures. They are the normal residue of a growing organization, and every Microsoft tenant accumulates some amount of it.

Why it survives so long

License assignment and license usage live in different places. Assigning a seat is a one-time admin action. Noticing that the seat is idle requires someone to actively go looking, in a report that most IT teams do not check weekly. Unless there is a deliberate review cadence, an idle E5 seat can run for a full year, or several, without triggering anything. There is no error message. The invoice just quietly reflects it.

The arithmetic of one seat

Take a single Microsoft 365 E5 seat. Street pricing varies by region, contract type, and volume discount, but E5 commonly runs in the range of several hundred euros or dollars per user per year, roughly two to three times the cost of an E3 seat. For the sake of a clean example, assume a seat costs €430 per year (a reasonable mid-range figure many mid-market organizations recognize from their own agreements).

One forgotten seat for one year: €430. Not nothing, but not a headline either. The real cost only becomes visible when you look at how these seats accumulate.

The compounding effect

Here is where a single seat becomes a budget line worth acting on:

Scenario	Forgotten seats	Annual cost at €430/seat
One overlooked leaver	1	€430
A department that never cleans up after reorgs	12	€5,160
Company-wide drift over 2-3 years without review	50	€21,500
Mid-market org (500-2,000 users) with no seat hygiene	100+	€43,000+

The pattern is not that any single seat is expensive. It is that forgotten seats do not remove themselves. Each one renews automatically at the next contract cycle, and new ones join the pile every time someone leaves, a project ends, or a role changes. Without a deliberate check, the count only grows.

It is worse when the seat is a premium tier

The math above uses a blended average, but the real damage concentrates in premium tiers. An idle E5 seat, sitting unused because the person left or the role changed, costs two to three times what an idle E3 seat costs, for exactly the same amount of unused capacity. If your organization defaults new hires or entire departments to E5 "to keep things simple," your forgotten-seat cost multiplies along with it.

Why this stays invisible to Finance

Finance sees a Microsoft 365 line item on a vendor invoice. It rarely gets broken down seat by seat, and even when it does, department, job title, and last-sign-in-date data live in different systems (Entra ID, HR, the admin center) that nobody has stitched together. So the invoice looks stable, maybe even predictable, and nobody flags it, because nothing about a renewing contract looks anomalous from the outside. The cost is real, it is just distributed across too many small line items to notice without deliberately looking for it.

The audit gap

Most access reviews focus on what a user can reach: group membership, app permissions, standing access. License tier is a related but separate question, and it is often left out of the same review cycle. A user can pass an access review cleanly (their group memberships are all correct) while still holding a license tier nobody would assign them today. The two checks need to happen together, or the license waste keeps compounding even in organizations that are otherwise disciplined about access governance.

How to find your own forgotten seats

A practical seat-hygiene pass does not require a big project. It requires the right three signals, checked on a schedule:

1. Cross-reference license assignment against account status. Any licensed seat attached to a disabled or deleted account is an immediate reclaim candidate.
2. Check sign-in activity, not just account status. An enabled account with zero sign-ins in 60-90 days, licensed at E5, is very likely a stale seat even if nobody remembered to disable it.
3. Compare license tier against role and department pattern. If nine out of ten people in a job title carry E3 and one carries E5 with no distinguishing usage, that one is worth a look.
4. Set a recurring cadence, not a one-off cleanup. A single sweep recovers the backlog. A quarterly or monthly check keeps new drift from becoming next year's backlog.

A cleanup without a cadence just refills itself

Teams that do a one-time license audit often see a satisfying drop in wasted spend, and then watch it creep back up over the following year because the underlying process that created the waste (manual provisioning, no offboarding trigger tied to license removal, no periodic check) never changed. The lasting fix is process, not a single spreadsheet exercise.

Where ServiceChanger fits

ServiceChanger's license module reads real Entra ID sign-in activity and keeps a contract and seat registry alongside it, so you can see exactly which seats are unused, under-utilized, or attached to accounts that no longer need them, without stitching together multiple admin center reports by hand. It flags forgotten and idle seats and expiring contracts, and gives right-sizing guidance on where the reclaimable cost is sitting. That guidance is reporting and insight: ServiceChanger surfaces the seats worth reviewing, the actual license change happens in the Microsoft 365 admin center or through your Microsoft partner.

Because ServiceChanger also automates access lifecycle through its ABAC engine, when someone leaves or changes roles, their group membership and access follow their attributes automatically. That does not remove a license on its own, but it does mean the access side of the leaver process stops depending on someone remembering a manual step, which is exactly where forgotten seats start in the first place.

FAQ

How much does one forgotten license really cost per year? It depends on the tier and your contract, but a single E5 seat commonly runs several hundred euros or dollars per year, often two to three times an E3 seat. The real cost is rarely one seat, it is the accumulation of many small forgotten seats across a tenant over time.

Why doesn't Finance catch this on the invoice? Because the invoice shows a total, not a per-user breakdown tied to sign-in activity, role, and account status. Those data points live in different systems, so nobody sees the correlation unless they deliberately go looking for it.

Does an access review already cover license waste? Not usually. Most access reviews check group membership and app access, not license tier against actual usage. A user can pass an access review while still holding a license that no longer matches their role.

Can ServiceChanger remove or reassign licenses for us automatically? No. ServiceChanger reports on real usage, flags unused and under-utilized seats, and gives right-sizing recommendations with a contract and seat registry behind it. The actual license assignment change happens in the Microsoft 365 admin center or through your licensing partner.

Next step

If you want to see how many forgotten seats are sitting in your own tenant right now, that is exactly the kind of gap the ServiceChanger identity and access platform is built to surface. Read more on license management or browse our Microsoft 365 coverage to see how seat hygiene fits into a broader access strategy.