Blog/How-to guides

How to Deprovision an Account Properly When Someone Leaves

A leaver checklist that holds up: revoke sessions first, transfer data before deletion, rotate shared credentials, and know the 20 and 30 day windows.

CyberWatch AILast reviewed 21 November 2026 · 7 min read
An empty office desk with a chair pushed in, a keyboard and a dark monitor

The usual leaver process is a password change and a deleted mailbox, and it gets two things wrong in opposite directions. It leaves access open, because a password change does not end a session that already exists. And it destroys data, because deletion starts a retention clock that most people do not know about until they need something back.

What follows is a leaver sequence that closes access quickly and keeps what you need. It is written for Microsoft 365 and Google Workspace, because that is where most of the risk sits, with the non-SSO systems treated as a separate list because that is where most of the misses happen.

Before the last day: build the list

You cannot revoke access you have not recorded. For every leaver, the person's manager should hand you four things, ideally a week before the departure:

  • Every system they used, including the ones IT never provisioned. The SaaS trial that became load-bearing, the supplier portal, the courier account.
  • Every shared credential they knew. This is the one that gets forgotten, and it is the one that survives everything else you do, because a shared password is not revoked by disabling a personal account.
  • Every device holding company data, company-owned and personal.
  • What needs to keep working after they go, meaning their mailbox, their files, any calendar they own, and anything automated that runs under their name.

If your organization has no such list, build it from the leaver you are handling now and keep it as the template. Our article on joiners, movers and leavers covers the process this slots into.

Hour zero: cut the access

Do these in order, on the last working day, at a time agreed with the manager. For anyone leaving involuntarily, do them while the conversation is happening rather than afterwards.

  1. Block sign-in. In Microsoft 365, block the user in the admin center. In Google Workspace, suspend the user from Menu > Directory > Users. Suspension in Workspace is particularly useful here because it resets the user's sign-in cookies and OAuth tokens as well as blocking access.
  2. Revoke the sessions and the refresh tokens explicitly. This is the step that actually ends access. Blocking an account does not reliably terminate a session already established, and Microsoft's own documentation notes expected delays of roughly half an hour to an hour depending on where you make the change. In Entra ID, use the revoke sessions action on the user. Do not assume a password reset did this for you.
  3. Reset the password anyway, so that any cached credential stops working and so that the account cannot be re-enabled quietly by someone who knows it.
  4. Remove administrative roles. Check both platforms: in Google Workspace, Menu > Account > Admin roles; in Entra ID, roles and administrators. A suspended account with a role attached is still a role you have to account for.
  5. Revoke app passwords and connected applications. In Google Workspace these are on the user's Security page under Application-specific password and Connected applications. An app password is a standing credential that bypasses interactive sign-in entirely, so this is not optional.
  6. Wipe or block the mobile devices. Microsoft's leaver sequence has this as its own step for a reason: it removes your organization's data from a phone or tablet you do not control. In Google Workspace, review the devices linked to the account and wipe the ones holding work data.
  7. Remove them from groups and distribution lists, which is both a security step and the thing that stops a bounce-back arriving at a customer in three weeks.

Record a timestamp against each one. "Access revoked at 16:40" is an answer; "we disabled the account that week" is not.

Hour one: the credentials that were never theirs

Everything above removes one person's identity. None of it touches a credential that several people shared, and this is where most leaver processes quietly fail.

Work through the shared credential list and rotate every one the leaver knew. Banking, payroll, the domain registrar, the social media accounts, the Wi-Fi pre-shared key if it has not changed in years, the alarm code, the shared mailbox password if one exists. Rotate, then re-share only with the people who still need it, through your password manager rather than over chat.

Then deal with the systems outside single sign-on, by hand, one at a time. The bank. The payment gateway. The accounting package. The courier account. The CRM if it is not federated. Each of these has its own user list and its own deprovisioning, and none of them noticed that you disabled an account in your identity provider. Our note on former staff access covers why these linger.

Day one to three: save what you need before you delete anything

Now slow down. Deletion is irreversible on a clock, and the clocks are shorter than people assume.

In Microsoft 365, the recommended sequence after blocking sign-in is to save the mailbox contents, then decide what happens to the address. You can forward the email to another employee or convert the mailbox to a shared mailbox, and in both cases the account has to stay in place because it anchors the forwarding or the shared mailbox. Give a colleague access to the OneDrive and Outlook content before deleting, because after deletion that content is retained for 30 days, during which you can restore the account and regain access. Removing the license retains email, contacts and calendar for 30 days before permanent deletion, but if you remove the license without deleting the account, the OneDrive content stays accessible to you beyond 30 days. Only then delete the account, which stops mail to that address being received. If you need the data for legal or compliance reasons, apply a hold through Purview eDiscovery before any of this.

In Google Workspace, transfer before you delete, because what is not transferred is lost. From Menu > Directory > Users, point to the user and choose More options > Delete user. A super admin is then offered, next to Data in other apps, a choice of Don't transfer data or Transfer, where you name a recipient and select what moves. During deletion a super admin can transfer Drive and Docs files, primary Calendar data and Data Studio data. Gmail content needs a separate migration or redirect, and group calendars the user owns have to be transferred by the user before they go, which is a strong argument for doing this a week early rather than on the day.

Two Workspace specifics worth knowing. You can restore a deleted user within 20 days, and you have to restore the user inside that window before you can transfer their data. And a user on litigation hold cannot be deleted until the hold is lifted, while deleting a user means Vault holds and retention rules no longer apply and data can be purged immediately even if you restore within 20 days. If your organization has any legal preservation obligation, read that sentence twice before clicking delete.

Also be aware of the hybrid case. If you synchronize accounts from an on-premises Active Directory into Microsoft 365, you have to delete and restore those accounts in Active Directory, not in the Microsoft 365 admin center.

A departing colleague forwarded something odd before they left? Paste the message or link into CyberWatch AI Scan for a free check.

Week one: verify, do not assume

Three checks, each of which has caught a real gap in a real organization.

Try to sign in as them. Use the old password if you have it, and use a password reset flow to see whether the recovery phone and email still point at the former employee. Attackers and disgruntled leavers use the same door.

Search the logs for activity after the revocation time. In Google Workspace that is Reporting > Audit and investigation > User log events; in Microsoft 365, the Entra sign-in logs and the Purview audit log. Any successful authentication after your timestamp is a step you missed, not a logging artefact.

Re-read the shared credential list a week later. People remember shared passwords in the shower, not in meetings. One follow-up question to the team usually produces one more credential.

Make the next one take fifteen minutes

Write the sequence above into a checklist with a line per step, a timestamp column and a signature. Keep the completed ones. If your licensing includes Microsoft Entra ID Governance you can go further and schedule the tasks with a leaver workflow, which runs the revocation steps on the departure date automatically, but the checklist is what makes the process reliable whether or not you automate it.

Then feed the misses back. Every credential you find late, every system that was not on the list, every device nobody knew about becomes a line in the template. After three or four leavers the process stops producing surprises, which is the actual goal. The related work is in running an access review, which is how you catch what the leaver process missed, and what to do with your own accounts when you leave a job for the individual's side of the same event. For the programme around it, see our small business cybersecurity guide.

Frequently asked questions

What is the single most important step?

Revoking active sessions and refresh tokens, not changing the password. Blocking sign-in or resetting a password does not always end a session that is already established, so someone can keep reading mail in a browser tab for hours. Revoke sessions explicitly and verify.

Should I delete the account immediately?

Usually not. Deletion starts a clock and can destroy data you will want. In Microsoft 365, deleted account content is retained for 30 days and the account can be restored in that window. In Google Workspace you can restore a deleted user within 20 days. Block access first, transfer data, then delete deliberately.

How do I keep a leaver's mailbox without paying for a license?

In Microsoft 365, convert the mailbox to a shared mailbox or set up forwarding, both of which need the account to stay in place as the anchor. Do not delete the account after setting either of these up, because the forwarding or shared mailbox depends on it.

What about the Drive files?

In Google Workspace, transfer them before you delete. A super admin can transfer Drive and Docs files, primary Calendar data and Data Studio data during the deletion itself. Files in shared drives stay with the organization; files the user solely owned and that are not transferred are permanently deleted.

What gets missed most often?

Shared credentials, systems outside single sign-on, personal devices holding company mail, and third-party app grants. A leaver who knew the shared bank portal password still knows it after their account is disabled, because that credential was never theirs to lose.

How fast does this need to happen?

Access revocation on the last working day, timed to the hour for anyone leaving involuntarily. Data transfer and deletion can take days. The risk window is between the person learning they are leaving and the access being removed, which is why planned leavers and sudden leavers need different timings.

Does disabling the account in the admin center take effect immediately?

Not always instantly. Microsoft's own guidance notes different expected delays depending on where you make the change, in the region of half an hour to an hour. Plan for that gap rather than assuming the moment you click save is the moment access stops.

What evidence should I keep?

A completed checklist per leaver with timestamps, who performed each step, and what data was transferred to whom. This is what answers a later question about whether a departing employee could still have had access, and it takes two minutes if you fill it in as you go.

Sources

  1. Remove a former employee - Overview, Microsoft Learn
  2. Revoke user access in Microsoft Entra ID, Microsoft Learn
  3. Automate employee offboarding tasks with the Microsoft Entra admin center, Microsoft Learn
  4. Delete or remove a user from your organization, Google Workspace Admin Help
  5. Suspend a user temporarily, Google Workspace Admin Help
  6. Manage a user's security settings, Google Workspace Admin Help
  7. Transfer Drive files to a new owner as an admin, Google Workspace Admin Help
  8. SP 800-53 Rev. 5: Security and Privacy Controls for Information Systems and Organizations, NIST
  9. 10 Steps to Cyber Security, NCSC
Share this article
LinkedIn WhatsApp X
For organizations

Your people get these messages at work too.

CyberWatch AI sends your staff realistic practice attacks, trains the gaps it finds, and shows management exactly where the organization stands.