Start free trial
Start free trial
How-to 5 steps 3 min read Updated 11 November 2026

How to offboard users in Microsoft 365 without losing data or control

Offboard a leaver without orphaned Teams, lost OneDrive files or paid-for licenses: transfer ownership first, then disable the account.

Torsten Mandelkow Works with
How-to

What is user offboarding in Microsoft 365?

Offboarding a user in Microsoft 365 means removing a departing person's access and handing over what they owned, including Teams, sites, OneDrive files, apps and licenses, so that nothing is lost or left without an owner.

In short

  • Disabling the account stops the sign-in, not the leftovers.
  • Hand over ownership before you disable, so Teams and sites keep an owner.
  • OneDrive files are deleted after the retention period unless someone moves them.
  • A disabled account with a license still costs money every month.

Step by step

Five steps keep ownership and data intact from the leaver's last day.

  1. Start from the HR event

    Trigger offboarding from the leaving date in your HR system, not from a request that someone has to remember. Give the manager the checklist in advance.

  2. Hand over ownership

    List the Teams, SharePoint sites, Microsoft 365 groups, apps and flows the person owns, and add a new owner to each before the account is disabled. A resource with a disabled owner is the same as one with none.

    Tip: Check for Teams and sites where the leaver is the only owner first, since those stop working for their members.

    In Rencore:

  3. Secure and move the data

    Give the manager access to the leaver's OneDrive, move what the team needs to a shared site, and revoke sessions and tokens. Check any retention or legal hold before deleting anything.

    In Rencore:

  4. Remove access and reclaim licenses

    Remove the person from groups, Teams and sites, remove guest invitations they made, then disable the account and take back the licenses.

    In Rencore:

  5. Verify and keep the record

    A week later, check that nothing is left with a disabled owner or a license on a disabled account, and keep the record of what was handed over, to whom and when.

Why offboarding leaves gaps

Offboarding spans many services and many stakeholders: HR, IT, managers and the owners of each workload. Without one place that lists the whole checklist, each team does its part and the rest is assumed.

What stays behind is easy to miss because nothing breaks at once. Teams and sites lose their only owner, OneDrive files that colleagues need are deleted, apps and flows stop being maintained and licenses keep billing. Months later it surfaces as a security or cost question you cannot answer.

Connectors in this How-to

Each connector page in the Rencore docs lists the objects, policies, reports and actions behind these steps.

Common questions about offboarding in Microsoft 365

What goes wrong when offboarding is not centrally governed?
Each service is handled by a different team and each leaver is checked against a different list. Teams and sites lose their only owner, OneDrive files that colleagues depend on are deleted after the retention period, apps and flows keep running under a departed user's connections, and licenses keep costing money. The risk is not one dramatic failure but small gaps that nobody can see together.
Is disabling the account in Entra ID enough?
No. Disabling the account stops the sign-in, but everything the person owned stays where it was. A disabled owner still counts as an owner, so a Team can have only disabled owners and nobody to approve a new member. Sessions and tokens may also stay valid for a while, so revoke them as part of the same step and treat the disable as the start of the process, not the end.
How long should we keep a leaver's OneDrive?
Long enough for the manager to take what the team needs, and no longer than your retention policy says. Microsoft deletes a OneDrive a set period after the account is removed unless a retention policy or hold applies, so decide the period in advance, name who reviews the files, and move anything that is still needed to a team site before the clock runs out.
How does Rencore support offboarding?
Rencore Governance flags what a leaver leaves behind: Teams with a disabled owner or only disabled owners, site collections with disabled owners, groups with disabled user accounts, OneDrives of disabled users and disabled accounts that still hold licenses. Actions add new owners, remove users from Teams, groups and sites, and remove license subscriptions, and an offboarding dashboard shows what is outstanding.

Last updated 11 November 2026

About the author

Torsten Mandelkow

Torsten is co-founder and CAA at Rencore. During his time as a SharePoint consultant, he always tried to improve and automate the SharePoint development process, first by creating the SharePoint Software Factory (SPSF), and later by creating the SharePoint code analysis tools, today known as SPCAF. After an intermezzo for 3 years at Microsoft, he is now part of the RENCORE team and is responsible for the further technical development of all our tools.

Related

See what a leaver leaves behind

We will show the offboarding dashboard and the actions that hand over ownership and reclaim licenses in a short demo.

Request a demoGet started free
Rencore newsletter

Subscribe to our newsletter

Get the latest insights on governing Microsoft 365, Copilot and AI agents, delivered to your inbox.

Loading form