Why right sizing and employee offboarding belong together
Most right sizing programs focus on finding waste that already exists. That matters, but it treats the symptom. The source of a large share of inactive seats is a broken handoff at the moment someone leaves. Offboarding usually disables the identity and email, because security demands it, but stops there. The per seat licenses attached to that person across the stack keep billing because nobody told the finance side they were freed.
The result is predictable. Every departure leaves a trail of paid seats in the suite, the chat tool, the video tool, storage, the signature platform, and a long tail of smaller applications. Multiply by annual turnover and the number is significant. Worse, it grows quietly, because each leak is invisible until someone runs a full cleanup.
The difference between deprovisioning and reclamation
These two are easy to confuse and the gap between them is where the money sits. Deprovisioning is a security action. It removes access so a former employee can no longer log in. Reclamation is a commercial action. It returns the freed license to the pool or reduces the billed count so you stop paying. A user can be fully deprovisioned, with no access at all, while their license keeps costing you money. Security teams own the first. Often nobody owns the second.
How to connect offboarding to reclamation
Make the directory the single trigger
Offboarding should fire from one place, usually the HR system or the identity provider. When a leaver is marked, that event should drive both access removal and license release across connected applications. The more tools that read from a single source of truth, the fewer seats slip through.
Map every per seat tool to the leaver workflow
List the applications that bill per user and define, for each, what happens on departure. Some integrate directly with the identity provider and can release automatically. Others need a manual step in an admin console. Either way, the action must be owned and tracked, not assumed.
Handle the contract timing
Freeing a seat does not always cut the bill immediately. Monthly plans flex fast. Annual and multi year commitments, including a Microsoft Enterprise Agreement, often hold the count until renewal. The discipline is to release the seat into the pool the moment someone leaves, then reuse it for the next joiner instead of buying new, so you avoid growth even when you cannot reduce mid term.
Catch the long tail
The big tools usually get handled. The leak hides in the smaller applications bought by individual teams that sit outside the central offboarding flow. A periodic reconciliation of every per seat tool against the active employee directory catches these before they accumulate.
Reusing freed seats instead of buying new
One of the quiet wins of good offboarding is that it feeds joiners. If a seat releases cleanly when someone leaves, the next hire takes that seat rather than triggering a new purchase or a true up. Over a year of normal turnover this keeps your license count flat against headcount instead of ratcheting upward. It is the difference between a count that tracks reality and one that only ever grows.
Governance that keeps it working
Connecting offboarding to reclamation is a setup task, but keeping it honest is ongoing. Assign an owner for each major application who is accountable for the seat count. Audit the leaver to reclamation flow on a schedule to confirm seats actually release. And report the recovered and reused seats so the saving is visible and the discipline sticks.
Where this fits in cutting workplace spend
Offboarding discipline is what makes right sizing permanent rather than a recurring chore. It pairs with inactive user cleanup and tier downgrades, and it sits inside the wider digital workplace cost optimization discipline. See the license right sizing cluster for the rest. Related reading includes what SaaS license right sizing is, inactive user cleanup across the stack, and right sizing before a renewal. To put this in place, see the license right sizing service.
Enterprise Agreement reduction timing referenced here reflects Microsoft commercial licensing as of June 2026. Vendor plans change often, so confirm current terms before acting.