Home/Microsoft 365/Leaver Process
Cost Optimization · M365 Operations

Every leaver who keeps their license is a contract decision nobody made.

In a thirty thousand seat estate with ten percent annual attrition, three thousand users leave every year. If the deprovisioning runs at a two week delay, the buyer is paying for an average of one hundred and fifteen seats every single day that were already vacated. At blended Microsoft 365 cost the carrying number reaches mid six figures inside a calendar year. The leaver process is not an HR ceremony. It is a license operating standard. The procurement team owns the metric, even if the work itself runs through HR and identity.

Contact Us Microsoft 365 pillar →
The four populations

A leaver is not a single category.

The license consequences differ for each population, so the process needs to fork at the trigger point rather than collapse into a single workflow.

Population 01 · 02
Resignation · Termination

Voluntary and involuntary employee exits

The textbook case. HR triggers the workflow on the agreed last day. Identity disables the account at the configured time. The licensing group rule removes the seat. The license returns to the pool.

  • Voluntary. Predictable timeline, often two to four weeks notice. The license should be removed at end of business on the last working day, not later.
  • Involuntary. Immediate. The license removal needs to be tied to the same automation that disables the account, not to a manual hand off.
  • Both. The mailbox, OneDrive, and Teams content require a retention plan. That plan must not depend on holding the license.
Population 03 · 04
Contractor · Internal move

Contractors and internal moves

The two populations most commonly missed. Contractors leave outside the HR workflow because the workflow does not own them. Internal movers change role but rarely have their license tier reassessed.

  • Contractor end. The trigger is contract end, recorded in the contractor management system. That system rarely talks to identity by default.
  • Internal move. The role change should update the licensing group membership through the attribute rule. In practice the previous tier persists until the next pooling audit.
  • Both. The license consequence is identical to an exit even though the user remains. The process needs to treat them as license events.
The standard

Twenty four hours. Measured.

The license operating standard for a leaver is removal of all paid entitlement within twenty four hours of the trigger event. The trigger event is the HR last day, the contractor contract end, or the internal role change effective date.

Phase 01

Hour zero to four

HR or contractor management closes the record. The identity sync picks up the change on the next cycle. Entra ID flags the account for disable.

  • Automation. No human in the loop required for the standard path.
  • Exception path. Legal hold or active investigation overrides the standard removal.
Phase 02

Hour four to twenty

The account is disabled. The mailbox enters the configured retention path. OneDrive content transfers to the designated business owner or shared location. Teams memberships are cleared.

  • Content path. Shared mailbox conversion is free. Mailbox below fifty gigabytes can sit shared without an E3 attached.
  • OneDrive. Inactive OneDrive moves to a holding tenant or an archive workspace.
Phase 03

Hour twenty to twenty four

The licensing group membership clears. The seat returns to the pool. The reconciliation script confirms the removal and writes the event to the license ledger.

  • Audit trail. Every removal logged with timestamp and trigger source.
  • Pool effect. The seat is available for reassignment immediately, subject to the contracted reassignment window.
The shared mailbox question

The single largest leaver savings lever.

The shared mailbox conversion is the highest leverage operational move in the leaver process. Microsoft permits shared mailboxes up to fifty gigabytes without an attached license. Most enterprises hold thousands of licensed mailboxes belonging to former employees that could be converted within hours.

The mechanic

What conversion actually means

A shared mailbox is an Exchange mailbox without a sign in. It can be accessed by delegated users through Outlook or by automation. It does not consume an Exchange Online plan, an E3, or an E5 license unless a per user policy requires one.

The conversion is performed inside the Exchange admin center or through PowerShell. The mailbox content is preserved. Delegation can be set up immediately. The associated license can be removed from the user account and returned to the pool the moment the conversion completes.

The constraint

Above fifty gigabytes, the attach returns

The fifty gigabyte ceiling is the constraint that matters. A shared mailbox that crosses fifty gigabytes requires an Exchange Online Plan 2 license attached to maintain the size. Most former employee mailboxes sit below the threshold but a small population sits above it.

The operational answer is content retention policies that move content out of the mailbox to compliant archive locations. The size drops below the threshold. The license can be removed. The shared mailbox continues to function for the delegated population.

The contracting consequence

What the leaver process does at renewal.

The leaver process is not separately negotiated. It shows up at the renewal as a clean, defensible active user count that Microsoft cannot inflate. The discipline is what permits the buyer to negotiate from a real number rather than an aspirational one.

Effect 01 · 02

Active user count accuracy

The active count at the renewal table is the count that pricing keys off. Without a clean leaver process the count is inflated by stranded seats that have not been removed. Microsoft prices the next term against the inflated count, with year over year uplift on top. The leaver discipline removes the inflation at source.

The clean count also enables the true down conversation. The buyer can present documented evidence of the natural attrition the pool absorbed during the term and argue for a lower starting seat count at renewal. Without the leaver discipline, the documentation does not exist.

Effect 03

Audit posture strengthened

The leaver process is the third element of an audit defensible position. The buyer can demonstrate when each license was assigned, when each leaver was removed, and how the pool absorbed the difference. Microsoft audit teams will not invest time in challenging an organization whose leaver discipline produces this evidence trail.

The opposite is also true. Buyers without a leaver process invite the audit team to count assigned seats against the entitlement contracted. The math against a poorly maintained tenant favors Microsoft every time.

The twenty four hour leaver operating standard.

Our internal standard for HR integration, identity automation, shared mailbox conversion criteria, and the monthly reconciliation script. Sent on request.

$420M+ recovered · 340+ engagements
Engage the practice

Close the leaver gap before the next true up window.

The leaver process compounds inside a single quarter. The seats removed today reduce the inventory Microsoft will quote against twelve months from now.

Contact Us 79% audit exposure cut · 20+ years practice depth