Colour theme
Book a consultation

Finding cloud-app access left behind after departures

Audit former staff access across cloud apps, local logins, sharing links and integrations, then record verified removal and ownership transfers.

Close-up of a laptop keyboard and its USB and headphone ports.

A departure checklist can show a disabled mailbox and a returned laptop while another application still accepts the person’s login. A project tool, supplier portal or shared folder may have its own account and permissions.

An access audit checks the systems beyond the main staff directory. Its result should be a record of what was removed, what was transferred and what still needs a decision.

Build the application list from several places

Start with the identity provider’s connected applications. Add subscription and purchasing records, the password manager’s business records and lists from department owners. Ask teams which tools they use for client work, surveys, design, scheduling and file exchange.

A central directory won’t show every independently purchased application. Record the business owner, administrator, sign-in method and location of important records for each tool.

Keep the review to the business’s own systems. Don’t ask for former employees’ personal-account passwords or search private accounts to fill gaps in the inventory.

Compare the accounts with staff changes

Start with the last 12 months of departures, or as far back as your records go. Compare active users, guests and administrators with confirmed departures and role changes. Include contractors whose project access should have ended.

Check aliases and personal email addresses used as guests. A former staff member might have more than one identity in the same application.

An account with no recent login can still have access. Record whether it is enabled and what it can reach; don’t rely only on an activity timestamp.

Check sessions, local logins and integrations

Microsoft’s access-revocation guidance explains that applications can manage sessions independently of Entra. Disabling central sign-in can stop new authentication while an existing application session continues until the app ends it.

For each application, check:

  • whether its local password sign-in still works;
  • how administrators terminate active sessions;
  • API keys, personal access tokens and connected integrations;
  • recovery methods and administrator roles;
  • direct shares, guest invitations and public links.

Rotate or revoke exposed credentials after identifying the systems that depend on them. A token used by an ongoing integration needs a replacement owner and a tested migration before anyone deletes it.

Transfer records before deleting accounts

Ask the business owner which projects, automations and documents need to continue. Transfer ownership using the provider’s own process, and keep the records your retention rules require.

Remove access promptly through disabling, session termination and permission changes. Account deletion and licence removal are separate decisions: either can affect records, ownership or recovery options.

If the audit finds unexplained use after a departure, preserve the relevant logs and involve the incident-response lead. Don’t treat it as misconduct yet, and don’t disclose account activity beyond the people handling the review.

Verify automated removal

Microsoft’s provisioning documentation describes how disabling or unassigning a user can disable or delete the matching account in a connected app. What happens depends on the app and how the connection is configured. The central change can succeed while the app account stays active.

Check provisioning results and the application’s user state. Test the procedure with a test account, including local login and session behaviour. Record tools that still require manual action.

For each finding, keep the application, account, action, person responsible, completion time and evidence of verification. Give unresolved access a named owner and follow-up date.

Feed the findings into the departure process

Add missing applications to the inventory and assign someone to maintain their access records. Repeat the wider audit on a fixed schedule, such as every quarter, and check finance, file-sharing and client systems more often.

The onboarding and offboarding guide covers how to coordinate those actions at each departure. This audit provides the evidence needed to repair gaps in that process.


Featured Image Credit