Offboarding

Departed users holding live licenses are the most common — and most expensive — form of seat waste. License Maxing tracks contractors and their end dates, then executes the offboarding for you.

What an offboarding does

Up to three actions, configurable per organization and overridable per contractor:

  1. Disable the account — blocks sign-in immediately.
  2. Revoke active sessions — invalidates existing tokens so open sessions end.
  3. Reclaim licenses — removes all license assignments, freeing the seats.

Running an offboarding

  1. Track the person under Contractors (name, email, end date).
  2. When they leave, choose Execute offboarding. The request is queued and the background worker applies each enabled action through Microsoft Graph.
  3. The result lands as Success, Partial, or Failed per action, visible on the contractor record and in the audit log. Admins receive a results email.

Configuring defaults

Settings → Offboarding sets the organization-wide default for which of the three actions run. Individual contractors can override the defaults — for example, disable and revoke a contractor's sessions but leave licenses in place while their mailbox is reviewed.

ServiceNow integration (Enterprise)

If your organization requires change management, connect ServiceNow in Settings. Offboarding executions can then open a change request and close it with the execution result, keeping your CMDB trail intact.

Requirements

Offboarding modifies accounts, which requires the User.ReadWrite.All application permission granted by tenant admin consent. Read-only connections can track contractors and end dates but can't execute until consent is upgraded.