Last Updated: October 30, 2026
Quick Summary
To revoke employee access, disable the identity in your identity provider first, then revoke active sessions and invalidate access tokens so devices already logged in are kicked out. Do this before resetting passwords, since a reset alone leaves live sessions and saved tokens working.
- Freeze high-risk admin, finance, and remote access before notifying the employee.
- Disable the account, revoke sessions, and invalidate tokens within one hour.
- A password reset changes the key but does not close already-open sessions.
- Remove OAuth grants, app passwords, and delegated mailbox permissions by name.
- Set a 30-day watch on the former employee’s username for sign-in attempts.
Table of Contents
- Why Revoking Employee Access After Termination Is a Race Against the Clock
- The Employee Offboarding Checklist: A Timed, Role-Based Sequence
- Step 1: Disable the Identity and Revoke Active Sessions and Access Tokens
- Step 2: How to Revoke Access to Microsoft 365 After Termination
- Step 3: Remote Access, VPN, and Shared Credentials
- Step 4: Physical Access Control Employee Offboarding
- Step 5: Device Recovery, Evidence, and Completion Verification
- Schedule Your Free Offboarding Access Review
- Frequently Asked Questions
Why Revoking Employee Access After Termination Is a Race Against the Clock
Most companies treat offboarding as paperwork. It is not. It is a security event with a countdown timer attached.
The moment an employee learns they are being let go, every credential they hold becomes a tool for retaliation, data theft, or carelessness.
Access revocation is the process of removing a departing employee’s ability to reach company systems, buildings, and data.
What Former Employees Can Still Reach After the Badge Is Turned In
Handing back a badge feels final. It rarely is.
A former employee can still reach a surprising amount if nobody checks:
- Email syncing to a personal phone
- Cloud files shared with a personal account
- VPN access that still accepts an old certificate
Each of these is a live door. A password reset closes one. It does not close the rest.
The Employee Offboarding Checklist: A Timed, Role-Based Sequence
A good employee offboarding checklist is a sequence with owners and deadlines, not a flat task list. Some steps must happen before the person is told; others can wait for the exit interview.
Here is the order we recommend, built around risk level rather than convenience:
| Window | Action | Owner |
|---|---|---|
| Before notification | Freeze high-risk access (admin, finance, remote) | IT + HR |
| Within 1 hour | Disable identity, revoke sessions and tokens | IT |
| Within 4 hours | Cut email, VPN, cloud apps, shared credentials | IT |
| Same day | Remove physical access and collect devices | Facilities + IT |
| Within 24 hours | Verify completion, log evidence, review exceptions | IT + Manager |
Watch out: the biggest failure we see is starting with the badge and ending with the login. Physical access is visible and easy. Digital access is invisible and everywhere.
Step 1: Disable the Identity and Revoke Active Sessions and Access Tokens
Start here: disable the identity, then kill every session it opened.
A disabled account with a live session is still an open account. When you revoke employee access at the identity level, do three things:
- Disable the account in your identity provider so no new sign-in succeeds
- Revoke active sessions so devices already logged in are kicked out
- Invalidate access tokens so apps holding a saved pass don’t keep working
Why a Password Reset Alone Leaves the Door Open
A password reset changes the key. It does not change the locks already open.
If the employee is signed in on a phone, home laptop, or tablet, that session keeps running until it expires or is explicitly revoked.
This is why the order is disable, revoke, then reset. Resetting first can tip off the person that something is happening.
If your building still runs on key cards and you are weighing phone-based credentials, our overview of mobile access credentials explains how those get deprovisioned alongside physical cards.
Step 2: How to Revoke Access to Microsoft 365 After Termination
The fastest reliable way to revoke access to Microsoft 365 after termination is through the admin center, not the user’s mailbox settings. But that is only half the job: Microsoft 365 sits behind an identity provider, and a disabled account with a live token is still open. Treat this as three layers: identity, sessions, and indirect access.
Layer 1: Disable the identity, not just the mailbox
In the Microsoft 365 admin center or Entra ID (formerly Azure AD), block sign-in on the user object first. This stops new authentication immediately. Do not start by resetting the password, a reset can notify the departing employee’s recovery email or phone and tip them off before you have cut sessions.
- Block sign-in on the account.
- Revoke refresh tokens so apps holding a saved grant cannot silently mint new access tokens. In Entra ID this is the “Revoke sessions” action on the user; in PowerShell,
Revoke-AzureADUserAllRefreshToken(or the Microsoft Graph equivalent) does the same. - Reset the password and remove any app passwords. App passwords bypass modern authentication and are a common forgotten door.
Layer 2: Kill sessions and tokens that are already live
Sessions and tokens outlive the password change unless you explicitly revoke them.
- Sign out of all sessions in the admin center so devices already logged in are kicked out.
- Check for OAuth grants the user consented to. Third-party apps with delegated permissions can keep reading mail or files after the account is blocked. Review enterprise applications and remove the user’s consent grants.
- Audit app passwords and legacy protocols. If IMAP, POP, or SMTP AUTH is enabled, an old mail client with a saved app password can keep syncing. Disable legacy auth for the tenant if you have not already.
A password reset changes the key. It does not change the locks already open. If the employee is signed in on a phone, a home laptop, or a tablet, that session can keep running until it expires or is explicitly revoked. Some refresh tokens last for weeks.
Layer 3: Close indirect access surfaces
This is where most checklists stop and most breaches start.
- Convert the mailbox to a shared mailbox if the manager needs the history, then remove the license. Shared mailboxes do not consume a license and preserve mail for the retention period.
- Reassign OneDrive to the manager so files are not orphaned when the account is deleted.
- Remove delegated mailbox permissions. “Send As” or “Full Access” rights survive account disablement unless you remove them.
The order that works
- Block sign-in.
- Revoke refresh tokens and sign out all sessions.
- Reset password and remove app passwords.
- Remove OAuth grants and delegated permissions.
- Convert mailbox to shared, reassign OneDrive, remove license.
- Audit sharing links and group ownership.
The same logic applies to Google Workspace, Slack, and any other collaboration tool. Transfer ownership of files and channels to the manager before you delete the account. Deleting first can wipe data you needed to keep.
Disabling a Microsoft 365 account is not the same as revoking access. Refresh tokens, OAuth grants, app passwords, delegated mailbox rights, and sharing links are separate doors that stay open until someone closes them by name.
Step 3: Remote Access, VPN, and Shared Credentials
Remote access is the highest-risk door in the building. It reaches past the front desk and straight into the network.
Treat it as a separate task from email, even if both live in the same system.
Then turn to shared credentials. These are the logins everyone knows and nobody owns:
- The alarm panel code
- The supply ordering account
- The shared social media login
Change every one of these the day the person leaves.
Watch out: default passwords and open remote ports are how most small-business breaches start. Security System Vulnerabilities Exposed shows what an exposed panel or forwarded port looks like from the outside.
Step 4: Physical Access Control Employee Offboarding
Physical access control employee offboarding is the step most teams think they have handled. Often they have not.

Deleting a user from the access control software is not enough if that person also holds a physical key, a back-door fob, or a garage code.
This is where cloud-managed systems pull ahead of older on-premise panels. With cloud access control, you remove a user from one dashboard and the change lands at every door, at every site, within seconds.
Step 5: Device Recovery, Evidence, and Completion Verification
The last step proves the job is done. Skipping it is how access quietly comes back. This section turns the final step into an auditable closeout with a record you can hand to an auditor, a client, or a lawyer.
Recover every device, then prove it was wiped
Collect every company device: laptop, phone, tablet, keys, fobs, and any hardware token. Wipe and reimage the laptop before it goes back into stock. Do not trust a “factory reset” the departing employee performed themselves, a reset can leave the device enrolled in mobile device management (MDM) or still signed into a personal Apple or Google account that can re-enable access.
- Check MDM enrollment before reissuing. Remove the device from Intune, Jamf, or whichever MDM you run so the old user’s profile and certificates are gone.
- Revoke device certificates issued to the laptop or phone. A certificate can authenticate to Wi-Fi or VPN even after the password is changed.
- Record the serial number and wipe date for each device. This is the difference between “we think we got it” and “we can show we got it.”
Build a completion record that survives an audit
A simple completion record should show, for each system:
- Which systems were disabled and the exact timestamp
- Who confirmed each step (name and role, not just “IT”)
- What devices were recovered, with serial numbers and wipe confirmation
Store the completion record somewhere the departing employee never had access to, a shared drive the manager owns, or a ticketing system. A record kept in the person’s own OneDrive is not evidence; it is a liability.
Monitor for attempted sign-ins after the fact
Revocation is not complete until you have watched for the person trying to get back in. Most identity providers log failed sign-ins, blocked-account attempts, and token refresh failures. Set a 30-day watch on the former employee’s username and review it weekly.
- Failed sign-in spikes can indicate a saved credential on a device you did not collect.
- Token refresh failures can indicate an app still trying to authenticate with a revoked grant.
- Password reset attempts using the person’s recovery email or phone are a signal that recovery methods were not removed.
If you see activity, treat it as a missed door and go back through the identity, session, and indirect-access layers in Step 2.
Handle exceptions without leaving doors open
Two exceptions come up constantly, and both need a documented decision rather than a shrug.
- Legal holds. If litigation or an investigation is pending, do not delete the mailbox or OneDrive. Disable the account, preserve the data in place, and document who authorized the hold and when it can be released. Deleting data under a hold is a spoliation problem, not just a security one.
- Contractor and role-change exits. A contractor leaving mid-project may still need a specific shared drive for handoff. Grant that access to a named successor, not the contractor’s personal account, and set an expiration date.
This record is your evidence. If a client or auditor asks whether a former employee still had access, the log answers in seconds. A year-end review is a good time to check that your offboarding records are complete and consistent.
Device recovery is not the finish line. A defensible offboarding closes with a timestamped completion record, a 30-day sign-in watch, and a documented decision for every exception, legal holds, contractor handoffs, and manager access included.
Schedule Your Free Offboarding Access Review
Offboarding is where good security habits either hold or fall apart.
At Systems Integrations, we help organizations close those gaps with a cybercentric approach to physical security. Systems Integrations provides cloud-managed card access and works as a single point of contact for design, installation, and ongoing management across your sites.
Contact Systems Integrations for a free consultation to review your offboarding process.
Frequently Asked Questions
How quickly should employee access be disabled after termination?
For involuntary terminations, disable accounts at or before the moment the employee is notified. For planned departures, set a fixed revocation time on the last working day and confirm it in writing with HR. The goal is to make the revocation event coincide with the end of employment, not follow it. If you wait until the next business day, former staff can still reach email, cloud files, and VPN sessions overnight.
What should a complete employee offboarding checklist include?
A workable checklist covers identity disablement, session and token revocation, email and collaboration access, cloud application permissions, VPN and remote access removal, shared credentials and service accounts, group memberships, device recovery, and physical access control. Assign an owner and a deadline to each line, and record completion with a timestamp. Store the signed checklist with HR so you can produce it during an audit or a dispute.
How do you revoke access to Microsoft 365 after termination?
Block sign-in on the account first, then revoke refresh tokens and active sessions so existing logins drop immediately. Convert the mailbox to a shared mailbox if the manager needs the history, set an auto-reply, and remove the license once data is preserved. Remove the user from Teams, SharePoint, and OneDrive sharing links, and transfer file ownership to the manager. Check for inbox rules or forwarding the employee created before leaving.
Why is physical access control part of employee offboarding?
A disabled network account does nothing about a badge that still opens a server room, a records closet, or a warehouse door. Deactivate the credential in the access control system, remove the person from groups and schedules, and pull any mobile credentials or visitor passes. Review the audit trail for the last 30 days of entries, and confirm with the facility manager that the badge no longer works at any door.