If the mailbox is disabled but nobody can explain what happened to VPN, cloud storage, Remote Desktop, shared accounts or data on a personal device, the offboarding process is not closed.
This guide gives an SMB IT owner or outsourced IT partner a readback-oriented sequence. It is vendor-neutral and does not pretend that one command can resolve every environment; the goal is to give every access path a state, an owner and a next action.
Remember: disabling an account is one action. Closing access is a set of verifiable results.
The short answer: start with five object groups
Do not start with “was the mailbox disabled?” Start with the employee’s real work path and classify the objects:
- Identities: email, SSO, chat, project tools, code repositories, cloud platforms and business systems.
- Access paths: VPN, Remote Desktop, jump hosts, NAS, wireless networks and external collaboration spaces.
- Credentials: passwords, MFA devices, recovery methods, personal tokens, SSH keys, API keys and certificates.
- Assets: laptops, phones, access cards, removable media, licenses and peripherals.
- Data and jobs: local files, cloud-sync folders, mail, chats, scheduled automations and notifications.
If an item cannot be mapped to an object, state, owner and evidence, it should not live only in a ticket note. For a continuing operating model around assets, access and handover records, see Yuqi’s enterprise IT managed services and infrastructure path.
Do not collapse three different moments into one status
An offboarding event has at least three moments: HR or business notification, account disablement, and IT readback with exceptions closed. They answer different questions:
- Notification: who is leaving, when does it take effect, and who approved the scope?
- Disablement: which identities and routes can no longer be used?
- Closure: what evidence exists for sessions, credentials, devices, data and exceptions?
“Mailbox disabled” only proves a small part of the second layer. It does not prove that mobile or desktop sessions ended, that shared passwords and API keys were rotated, or that access cards and sync folders were handled.
Handle the access paths that can outlive the identity
After the identity is disabled, read back the following in order:
- Active sessions: check the revocation behavior for SSO, VPN, Remote Desktop, cloud consoles and mobile clients. A web sign-out does not prove every session ended.
- Recovery paths: check aliases, forwarding, delegation, recovery mailboxes, MFA devices and remembered personal devices.
- Shared credentials: list shared passwords, service accounts, SSH keys and API keys known to the departing employee. Confirm that rotation or revocation will not break automations, scripts or backups.
- Non-account entry points: handle access cards, device management, remote-control software, wireless access and local sync clients.
Write a real state—disabled, revoked, rotated or awaiting business confirmation—for each action. Do not let one “completed” label hide four different operations.
Hand over devices and data without losing the decision context
Collecting a laptop is not the same as completing asset handover. Record the asset identifier, device state, encryption state, synchronization state and successor before deciding how files should be handled.
Do not delete immediately when:
- project material has no named business owner;
- company data is on a personal device without an authorized retention or cleanup decision;
- an automation, scheduled job or notification remains tied to a personal account;
- contract, dispute, audit or legal-hold requirements are not understood.
Access revocation and data deletion are different decisions. When recovery, retention and handover need to become an operating design, see Yuqi’s enterprise backup and disaster-recovery path; the company’s authorized owners still decide what to retain, delete or preserve.
What must be left before the ticket is closed
The final readback does not need to be a long report, but it should answer four questions:
- Identities and accounts: who read back disablement, aliases/forwarding and active sessions?
- Credentials and devices: what happened to tokens, MFA, keys, laptops and access cards?
- Data and jobs: who owns the files, sync folders, automations and notifications, and how was the handover confirmed?
- Exceptions and approvals: why is something retained, who approved it, when is it reviewed, and who owns the interim risk?
A useful row format is: Object | Current state | Owner | Evidence location | Next readback date. The record remains usable even when the handover person changes.
Fast actions that leave gaps
- Disable email but skip VPN, Remote Desktop, SaaS and active sessions.
- Delete the account before retention, audit or handover requirements are understood.
- Leave shared passwords and API keys unchanged while closing the ticket.
- Collect the laptop but ignore access cards, personal-device sync folders and removable media.
- Leave “confirm later” in a note with no owner and no review date.
If the immediate problem is a Remote Desktop or Windows update issue, compare the Windows update and RDP check sequence, but do not treat a single incident guide as a complete offboarding process.
Evidence boundaries and sources
CISA, NIST and CIS guidance support timely access disablement, authenticator or credential revocation, system-property recovery and accountable records. They do not set one universal “complete within X minutes” deadline for every organization. The actual timing must be aligned with HR, legal, business continuity and authorization boundaries.
- CISA: Managing Risk of Adverse Involuntary Employee Separations: offboarding risk, access disablement, asset recovery and accountability.
- NIST SP 800-171r3: disabling system access, revoking authenticators and retrieving system property at termination or transfer.
- CIS Control 6.7: a defined and timely access-revocation process.
This is a public guidance summary. It does not claim that Yuqi has inspected or changed your systems, and it does not decide whether your organization should delete, retain, preserve or disclose data. Production actions should be confirmed object by object by HR, legal, the business owner and IT.
