Tools for Cybersecurity

Practical guide · November 16, 2026

Employee offboarding checklist: how to verify IT access is removed

Treat offboarding as a coordinated removal of access across identity systems, applications, devices and credentials. Disabling the main account is one step. Close the task only after checking the applications and access paths the person actually used, while preserving business records under your organization’s retention decisions.

For example, Microsoft explains that applications can maintain their own sessions: Microsoft Entra cannot directly revoke an application-issued session token. Access changes can also take time to become effective. An identity-provider action is therefore not proof that every open application session ended immediately. Microsoft access-revocation guidance

Set the timing and ownership first

Have the authorized people or HR owner provide the effective departure time and the scope of the request. Assign an IT coordinator and an owner for each application outside central identity management. For a sensitive departure, coordinate the sequence through the approved personnel and security process.

The checklist below is a proposed operational worksheet, not a vendor-specific command sequence.

Access area Action to evaluate Evidence to retain
Central identity Block new sign-ins; revoke supported sessions and tokens Action time, administrator and result
Business applications Disable local accounts and terminate sessions using supported controls Application owner’s confirmation
Remote access Remove VPN and other remote-access permissions Relevant access-list change
Devices Follow approved lock, return and data-handling procedures Device inventory and disposition
Developer / service access Review personal keys, tokens and shared secrets known to the employee Revocation or controlled rotation record
Shared work Transfer ownership using supported admin features Named successor and access check
Records Apply retention or legal-hold decisions before deletion Responsible owner’s instruction

Microsoft’s former-employee guidance similarly separates access blocking, data preservation, device handling, ownership transfer and account or license removal. The exact operations depend on your environment. Microsoft 365 offboarding overview

A completed example should reveal unfinished work

Hypothetical example: A project coordinator leaves at 5 p.m. Their account signs into company email and several applications through central identity. A scheduling service also has a separate local login.

At 5:05, the identity administrator records that sign-in is blocked and supported sessions have been revoked. The scheduling owner reports that the local account is disabled but cannot yet confirm session termination. The ticket remains open for that application. “Main account disabled” is recorded as completed; “all access removed” is not.

At 5:20, the application owner records that the local account is disabled, but the service provides no confirmed result for terminating its existing sessions. The ticket retains an open session-revocation exception, assigned to the application owner for escalation to the service’s support/security contact. The coordinator schedules a 6 p.m. status review and documents the interim restrictions actually applied. Until supported revocation or expiry evidence is obtained, the record cannot say all access ended.

Separate preserving work from preserving access

A manager needing a former employee’s files does not justify leaving that employee’s login active. Use approved administrative transfer or delegated access features. Avoid handing a successor the former employee’s password.

Review automation before rotating a shared credential: identify dependent jobs, choose a controlled replacement and check that the business process still works. Record any temporary exception with an owner and an explicit expiry, rather than silently excluding it from the checklist.

Finish with a reconciliation against the application inventory, device list and access records. Retain evidence of actions and unresolved exceptions without copying passwords, tokens or unnecessary employee information into the ticket.

Research basis: Microsoft documentation reviewed November 16, 2026. The cross-system checklist and scenario are editorial synthesis; no production offboarding test was performed.