Skip to content
StitchOps

Blog

Orphaned accounts: the SaaS risk SCIM was supposed to fix

When someone leaves, their accounts should end the same day. In most apps they do not, because the app cannot be told to remove them. Why that happens and how to close it.

, Cofounder and CEO ·

An orphaned account is an app login that outlived the job it was created for. The person left. The account still works.

Most companies believe their identity provider prevents this. Turn off the user in the identity provider, and access ends. That is true for sign in through the identity provider. It is not true for the account inside each app.

Why deactivating the user is not enough

When your identity provider deactivates someone, three things can still work in an app that is not told to remove them.

  • A local password. Many apps allow a direct login alongside single sign on, especially for admins.
  • API tokens and integrations. Tokens a person created keep running under their name.
  • Shared logins. A team account whose password the leaver knew is still valid until someone changes it.

Removing the account in the app is what closes all three. That step is called deprovisioning, and it is what SCIM was designed to automate.

The numbers behind the gap

We reviewed the public Okta Integration Network on November 17, 2026. Of 8,430 integrations, 837 support both creating and deactivating users. That is about 10%. Another 68 can create a user but cannot remove one, so they automate the easy half of the lifecycle and leave the risky half to a ticket.

Where SCIM does exist, vendors often sell it only on their top plan. Teams that skip the SCIM tax keep the manual step. Either way, the removal depends on a person remembering.

How orphaned accounts get found today

  • Access reviews. A reviewer compares app user lists to HR, usually monthly or quarterly. Findings arrive weeks after the termination.
  • License true ups. Finance notices seats paid for people who left.
  • Incidents. Someone uses an account that should not exist.

Each of these finds the problem after the exposure, not before it.

Close the gap at the source

  1. Make HR the trigger. A termination in your HR system should deactivate the user in your identity provider on the last day, with no ticket in between. See how to connect any HR system to Okta.
  2. Make the identity provider the instruction. Okta, Microsoft Entra ID or Google Workspace already knows who should have access to what.
  3. Make every app follow it. For apps with SCIM on your plan, use it. For the rest, StitchOps removes the account through the app's API or its own admin interface, anywhere a person can log in and act, and rotates shared passwords the leaver knew.
  4. Keep the evidence. Every removal is logged with the app, the time and the result. Access reviews become a check, not a cleanup.

Start with the apps that matter most

List the apps that hold customer data, money or source code. For each one, write down whether a termination in HR removes the account automatically today. Where the answer is no, that is your orphaned account risk. The SCIM tax calculator shows what closing it through vendor upgrades would cost, and pricing shows what it costs on the plans you have.

Frequently asked questions

What is an orphaned account?
An account in an app that belongs to someone who no longer works for the company, or to no one at all, and that still works.
Why do orphaned accounts happen if we use an identity provider?
Deactivating a user in the identity provider ends single sign on. It does not remove the account inside an app unless that app supports automated deprovisioning. Local passwords, API tokens and shared logins keep working.
How common is the gap?
In our November 2026 research on the Okta Integration Network, about 10% of 8,430 integrations support both creating and deactivating users. 68 can create a user but cannot remove one.
Do access reviews fix orphaned accounts?
Reviews find them, usually weeks later. They do not remove them unless someone acts on every finding in every app.
How does StitchOps remove accounts in apps without SCIM?
When your identity provider deactivates a user, StitchOps removes the account in each connected app through its API or its own admin interface, anywhere a person can log in and act, and records evidence of each removal.

Okta is a trademark of Okta, Inc. Catalog counts are from StitchOps' review of the public Okta Integration Network catalog on November 17, 2026.

Start with one workflow that never had an API.

Fifteen minutes on your top three manual processes. We tell you which one to run first.