SeatReaper
Entrar

MSP offboarding checklist: every license and seat to remove when someone leaves

Por SeatReaper · 3 de novembro de 2026 · 3 min de leitura

Os artigos do blog são em inglês.

When someone leaves a client, the offboarding ticket usually says "disable the account." Doing only that leaves a trail of seats still billing: the Microsoft 365 license, the RMM agent on their laptop, the EDR agent, the backup seat, the security training seat, the MFA user, sometimes a phone number. Each one sits in a different console, so each one is easy to miss.

This checklist covers the whole trail, in the order that keeps the client's data safe.

The day they leave

These follow Microsoft's guide to removing a former employee.

  • Block sign-in and sign them out of every session, so a known password stops working at once.
  • Wipe and block their mobile devices if they had company email or data on a phone.
  • Decide what happens to their mailbox. Forward it to a manager, or convert it to a shared mailbox. A shared mailbox under 50 GB needs no license; one on litigation hold or with an archive still does.
  • Give someone access to their OneDrive if the client needs the files.
  • Save anything the client must keep before you remove the license. Microsoft keeps the mailbox data for 30 days after the license is removed, then deletes it.

Licenses and seats to remove

  • Microsoft 365 licenses. Remove every paid license from the user. Blocking sign-in does not do this.
  • RMM agent on their computer, if the device is being retired rather than handed to someone else.
  • EDR or antivirus agent on the same device.
  • Backup. Both the device backup and any per-user Microsoft 365 backup seat.
  • Security awareness training seat.
  • MFA user in a separate MFA tool, if the client uses one.
  • Phone number or extension, released or reassigned.
  • Anything else billed per person: remote access, password manager, line-of-business apps.

Many of these tools bill per seat until the seat is removed in that tool's own console. Disabling the Microsoft 365 account does not reach them.

After the offboarding

  • Check each removal took. A license added back by a group, a device that checks in again, a backup seat still billed: check a week later.
  • Lower the subscription quantity at renewal. A license removed from a person is available, not cancelled. Under Microsoft's new commerce terms the count can usually only go down around purchase and renewal. See When you can lower Microsoft 365 license counts.
  • Delete the user account when the client no longer needs it. Keep it if a shared mailbox depends on it.

Doing it for every departure

The checklist is easy to follow once. The hard part is that nobody tells the MSP when someone leaves, and the seats outside Microsoft 365 are invisible from the Microsoft 365 admin center.

SeatReaper starts from the other end. It reads every client's Microsoft 365 tenant and the RMM, EDR, backup, MFA, training and phone tools you connect, and flags each person who left, or each dead device, with every system still billing for it. Offboard everywhere turns that into one checklist per person: their sign-in, every license, their devices in N-central, Datto RMM, NinjaOne, CrowdStrike, SentinelOne, Webroot, Huntress, Sophos, Acronis and Cove, and their seats in Datto SaaS Protection, KnowBe4 and Duo. Each item is checked off when a sync confirms it is gone. See Offboarding someone everywhere.

SeatReaper is free for up to 3 client tenants, and every connection is read-only by default. Create an account and run it on a client that had someone leave recently.