Employee offboarding in Microsoft 365 and Google Workspace comes down to one rule: save the data before you delete the account. Microsoft keeps a deleted user’s OneDrive and Outlook content for 30 days by default. Google lets you restore a deleted user for up to 20 days. After that, anything nobody moved is gone.
Small teams often handle employee offboarding from memory. The departure lands on a Friday, the account gets deleted to free a license, and a month later someone needs a grant file or a donor thread that lived in that account.
This piece walks through one employee offboarding checklist for both platforms, in the order the vendors’ own help pages follow: cut access, wipe devices, keep mail flowing, hand over files, close AI assistant accounts, then remove licenses and delete. It also covers the two places people forget: shared drives and AI workspaces that sit outside your main tenant.
The short version: on the last day, reset the password, sign the person out everywhere, and block sign-in. Then wipe work data from their phone, convert or forward their mail, transfer their files, and remove them from ChatGPT, Claude or any other AI workspace. Delete the account only after the data has a new home. Admin menus move, so the steps below are as of November 2026; check the linked help pages when you run them.
Before the last day: list what the person owns
Employee offboarding goes faster when you know what you are closing. Start from your asset list. Our guide to IT asset management covers how to keep one.
For each departing person, write down:
- Devices: laptop and phone, and whether each is company-owned or personal.
- Mail: who should get new messages sent to the old address, and for how long.
- Files: what in their OneDrive or My Drive other people still need.
- Shared spaces: Microsoft 365 groups, Teams, Google shared drives and group calendars they own or manage.
- Other accounts: AI assistants, the CMS, the CRM or AMS, social media, the domain registrar, and any tool they signed up for with a work email.
- Shared logins: any account whose sign-in codes go to their phone. Our post on multi-factor authentication explains why those need a new second factor.
Two items are easier for the person to handle than for an admin. On Google, the Google Workspace deletion article says that when a calendar owner is deleted, their secondary calendars, including group calendars, and their events are deleted too. Google suggests asking the user to transfer ownership before they leave. On Claude Team and Enterprise, private projects become unreachable once the person is removed, so ask them to share what the team still needs.
Step 1: cut access on the last day
Employee offboarding starts with access.
Microsoft 365. Microsoft’s sign-in step starts in the Microsoft 365 admin center. Open Users > Active users, select the person, and reset the password. Then select Sign out of all sessions on the Account tab.
Microsoft says the person is prompted to sign in again within an hour, because an access token is good for an hour. For an immediate sign-out, Microsoft points to the Revoke-MgUserSignInSession PowerShell cmdlet.
Next, select Block sign-in. Microsoft notes that a block can take up to 24 hours to take effect, which is why the password reset comes first.
If your accounts sync from on-premises Active Directory, Microsoft says you must delete and restore them in local AD, not in Microsoft 365. Our explainer on identity and access management covers why one source of truth matters.
Google Workspace. Reset the password, then sign the person out. Google’s sign-out article says to open the user under Directory > Users, then Security > Sign-in cookies > Reset. Google notes this does not sign the person out of apps such as Gmail and Google Drive for desktop. The same article covers revoking third-party apps the person authorized.
Suspending the user also resets sign-in cookies. Hold the suspension until Step 2 is done.
Step 2: wipe work data from phones and tablets
Microsoft 365. Microsoft’s device step uses the Exchange admin center. Go to Recipients > Mailboxes, select the user, and choose Manage mobile devices. Pick a device, select an option such as Account Only Remote Wipe Device, then select Block access. If you manage phones with Basic Mobility and Security, Microsoft says to wipe and block from there instead.
Google Workspace. In the Admin console, go to Devices > Mobile & endpoints > Devices. Google’s wipe article offers two actions:
- Wipe account is meant for a personal device when the user is leaving. Personal data and apps generally stay.
- Wipe device is meant for a lost or stolen device. It needs advanced mobile management.
Google’s preparation steps for a wipe include resetting the password and restoring a suspended account. So wipe first, then suspend.
Collect laptops and back up anything local before you reimage. Our guide to data backup strategy covers where copies belong.
Step 3: keep mail flowing to the right person
Microsoft 365. You can forward new mail to a colleague, or convert the mailbox to a shared mailbox. Microsoft’s mail step says forwarding sends only new messages. A shared mailbox keeps the old mail too.
Microsoft’s conversion article has the details that catch people:
- The mailbox needs a license when you convert it. If you already removed it, add it back.
- Without a license, a shared mailbox is limited to 50 GB. Under that size, you can remove the license after converting.
- A Litigation Hold on a shared mailbox needs Exchange Online Plan 2, or Plan 1 plus the Exchange Online Archiving add-on.
- Reset the password. If you do not, the original username and password keep working on the shared mailbox.
Either way, keep the account. Microsoft says it must stay to anchor the forwarding or the shared mailbox.
Google Workspace. Google’s preservation options are to transfer data to another user, keep the account on an Archived User license, or export with Vault. Google notes that license fees still apply to the account that holds the data. Its deletion article adds that the email address is removed from Google Workspace 20 days after the account is deleted.
Step 4: hand over OneDrive, My Drive and shared drives
OneDrive. Microsoft’s file access step runs through the SharePoint admin center. Go to More features > User profiles > Manage User Profiles. Find the person, choose Manage site collection owners, and add a colleague as a site collection administrator. The colleague can then open the OneDrive by its URL.
After the account is deleted, Microsoft keeps the OneDrive for 30 days by default. Microsoft’s retention article says you can set that from 30 to 3,650 days under Settings > Retention.
My Drive. Google’s transfer article uses Apps > Google Workspace > Drive and Docs > Transfer ownership. The new owner gets a transfer folder in their My Drive. Points to know:
- The recipient must be active, with enough storage and Drive turned on.
- The sender cannot be on litigation hold or already deleted.
- Files in Trash do not move, and sharing does not change.
- A transfer that runs longer than 36 hours stops, and you start it again.
Shared drives. Google says files in shared drives belong to the organization and are not deleted with the user. The risk is a shared drive left with no manager. Google’s shared drive troubleshooting article fixes that under Drive and Docs > Manage shared drives > Manage members: make someone a manager. On Microsoft 365, check the groups and Teams the person owned, and add an owner.
Step 5: close AI assistant accounts
AI tools are the newest gap in employee offboarding. Microsoft 365 Copilot and Gemini in Workspace run on the main account, so Steps 1 to 4 cover access. Separate AI workspaces need their own removal, and each treats the person’s data differently.
ChatGPT Business, Enterprise and Edu. OpenAI’s help article on removed members says access is revoked immediately. The person’s projects and GPTs move to a workspace owner. Their conversations and files do not, and the owner cannot see them. On Business, chats are kept indefinitely and come back if the person is re-added. Enterprise and Edu follow the workspace’s retention setting.
Claude Team and Enterprise. Anthropic’s help article on removed users says other members lose access to the person’s chats. Projects shared with the organization stay. Removal alone does not delete the account or its data. If you provision with SCIM, remove the person in your identity provider first, or they may be provisioned again.
Also revoke API keys the person created, and review connectors tied to their account, such as the ones in our Claude for Google Workspace post. If the person used a personal AI account for work, you cannot close it. Our guide to AI training data settings shows which plans keep work content out of model training.
Step 6: remove licenses, then delete
| Item | Microsoft 365 | Google Workspace |
|---|---|---|
| Restore a deleted user | 30 days | Up to 20 days |
| Mail after license removal | Kept 30 days, then deleted | Suspended users keep data but are still billed |
| Cloud files after deletion | OneDrive kept 30 days by default (30 to 3,650 configurable) | Untransferred files deleted after the restore window |
| License count on delete | License freed to reassign or remove | Annual plan: count unchanged. Flexible: prorated |
Microsoft 365. Microsoft’s offboarding overview says that when you remove or delete a license, the person’s email, contacts and calendar are kept for 30 days, then deleted permanently. Skip account deletion if the mailbox anchors forwarding or a shared mailbox.
Google Workspace. Data the person owned alone, and that was not transferred, is permanently deleted. Google’s suspension article says suspended accounts are still charged on both Annual and Flexible plans.
If you use Vault, Google says retention rules and holds stop applying to a deleted user, and the data can be purged immediately. A user on litigation hold cannot be deleted until a Vault admin lifts the hold, which can take up to 48 hours. Export first if you need a copy. Our post on Google Vault Gemini exports covers what Vault exports today.
An employee offboarding checklist you can copy
- List devices, mail, files, shared spaces and outside accounts.
- Ask the person to transfer group calendars and share private AI projects.
- Reset the password and sign out all sessions.
- Block sign-in (Microsoft) and revoke third-party app access (Google).
- Wipe work data from phones, then suspend the Google account.
- Convert to a shared mailbox, set forwarding, or pick a Google preservation option.
- Give a colleague the OneDrive, or transfer My Drive ownership.
- Add a manager to every shared drive and an owner to every group.
- Remove the person from ChatGPT, Claude and other AI workspaces, and revoke their API keys.
- Export anything under Vault or legal hold.
- Remove the license, then delete the account once the data has moved.
- Record the date and who did each step, so the next employee offboarding starts from a known state.
Frequently Asked Questions
What is the first step in employee offboarding for Microsoft 365?
Reset the password and select Sign out of all sessions, then block sign-in. Microsoft says a block can take up to 24 hours, so the password reset is what stops access quickly.
How long does Microsoft keep a former employee’s mail?
After you remove or delete the license, Microsoft keeps email, contacts and calendar for 30 days, then deletes them permanently. A shared mailbox under 50 GB keeps the mail without a license.
How long can I restore a deleted Google Workspace user?
Up to 20 days. After that, data the person owned that was not transferred is permanently deleted, and the email address is removed.
Does suspending a Google Workspace user save money?
No. Google says suspended accounts are still charged on Annual and Flexible plans. Deleting a user on an Annual plan also does not reduce your license count.
Do I need to reset the password after converting to a shared mailbox?
Yes, in practice. Microsoft says that if you do not, the original username and password keep working on the shared mailbox.
What happens to Google shared drives during employee offboarding?
The files stay, because the organization owns them. Check that each shared drive the person managed still has a manager, and add one in the Admin console if not.
What happens to a ChatGPT Business user’s GPTs and projects?
OpenAI moves them to a workspace owner. The person’s conversations and files do not transfer, and the owner cannot see them.
Does removing someone from Claude Team delete their data?
No. Anthropic says removal alone does not delete the account or data. Projects shared with the organization stay; private projects and chats become unreachable to others.
How often should a small team review its employee offboarding checklist?
Whenever you add a new system. Admin menus change, so check the vendor help pages before each departure.