Deprovisioning: Why locking accounts isn't enough

Written by Milutin Jokić | Nov 11, 2026, 4:28:07 PM

One in three employees in Germany could still reach their former employer's digital resources after leaving, and more than half of them kept using that access. That is the result of a survey by market research firm Censuswide among 2,000 full-time employees.

Carelessness is rarely the reason. In most companies, the Google or Microsoft account gets locked on time, and with that the exit counts as done. What stays open is everything that is not tied to that account. The design tool with its own password is one example, the shared login for the social media tool another, and so is the API key that keeps running in the background.

Key takeaways

  • Deprovisioning means taking back all accounts, permissions and licenses when an employee leaves.
  • Locking the main account only affects tools that are connected through single sign-on.
  • Hardly any mid-sized company runs this fully automatically. In most tools, a person removes the access in the end.
  • What makes the difference is a complete access list with an owner and a deadline for every tool.

What deprovisioning means

When employees join, they get accounts, roles and licenses. This is called provisioning. Deprovisioning is the way back at the end of the employment. It is one part of offboarding, not all of it. Device returns, handover and the reference letter are covered in our offboarding checklist.

You are only done when the person can no longer sign in anywhere, their data and admin roles sit with someone else, and the freed-up license has been reassigned or canceled.

Why access stays open

Locking an account takes a minute per tool. The hard part is the question before that, namely where the person has an account in the first place. A company with 100 employees quickly ends up with several dozen tools, and IT only knows some of them. We see four causes again and again.

Tools with their own login. Anyone who signs in with email and password still gets in after the main account is locked.

Self-purchased software. Teams book tools with the company card or on a free plan. This shadow IT is on nobody's list.

Shared access. A password that five people know stays the same after someone leaves.

No follow-up. The task goes out by email or chat, and nobody checks whether it was done.

What can be automated and what cannot

Many vendors promise offboarding at the push of a button. Technically, that only holds for some of your tools.

Access is locked automatically when the tool is connected to your central login. If you lock the account in Google Workspace or Microsoft Entra, the person can no longer get in there. Their user account inside the tool usually remains, though, and keeps occupying a license. For that account to disappear on its own, the tool needs an interface called SCIM. Many vendors only unlock it in their expensive plans.

For all other tools, two options remain. Someone on your team removes the access by hand, or you hire a service provider. The provider takes work off your plate, but needs admin rights in every single tool and usually only covers a limited selection.

In practice, this comes down to a mixed process. Part of it is handled through the main account, the rest are tasks for people. It only becomes reliable once each of these tasks has an owner and a deadline.

Three types of access

Type of accessExamplesWhat to doOwner
Through the central loginTools with “Sign in with Google” or single sign-onLock the main account, then remove the account in the tool and free up the licenseIT or workspace admin
Own login in the toolSign-in with email and password, often booked by individual teamsTransfer content and the admin role, then deactivate the account in the toolOwner of the tool
Shared and technical accessShared passwords, API keys, accounts at clientsChange the password, regenerate the key, have the client remove the personTeam lead

One point is often overlooked in the first group. If the person is still signed in to a tool, that session often stays alive until it expires on its own. For tools with customer, financial or HR data, you should therefore also sign the person out or remove them directly in the tool.

The order on the last working day

  1. Finalize the access list. A few days ahead, it is clear which tools the person uses and who is responsible for each.
  2. Hand over admin roles and content. Transfer first, then lock. Otherwise a tool is left without an admin or files get lost.
  3. Lock the main account. At the end of the last working day. Deletion comes later.
  4. Revoke the remaining access. Tools with sensitive data first, then the rest. Change shared passwords the same day.
  5. Free up licenses and check again. After a week, one person goes through the list and closes whatever is still open.

In case of a termination without notice or a garden leave, you move steps 3 and 4 to the front. An admin then takes care of the handover afterwards.

Template for the access list

The template lists all tools per employee with type of access, owner, deadline and status. One more column records whether the license was reassigned or canceled. That way you see at a glance what is still open, and you have proof at hand for an audit.

You can download it without signing up.

How Sovaro helps

Sovaro knows the tools and licenses of every employee. That includes software teams booked themselves and tools you built in-house. When someone leaves, this becomes the access list, and every owner gets their task with a deadline. Your team still removes the access in each tool. Sovaro shows what is done and what is still open, and documents every step. Try it for free

Frequently asked questions

What is the difference between deprovisioning and offboarding?

Offboarding covers the entire exit, from handover to device return. Deprovisioning is the part where accounts, permissions and licenses are taken back.

Is it enough to lock the Google or Microsoft account?

No. The lock only affects tools where the sign-in runs through that account. Access with its own password, shared logins and API keys are not touched by it.

By when does access have to be revoked?

By the end of the last working day at the latest. In case of garden leave or termination without notice, right away.

Lock or delete?

Lock first. An account is only deleted once files, mailbox and admin roles have been transferred.