What happens to the workflows when someone leaves

Problem

The person left. The wiring did not

Offboarding closes a login. It does not inventory the workflows that still run as that login, or the ones that only that person understood.

Consider a hypothetical office of about twenty people. Someone who handled a lot of the quiet coordination left six weeks ago. Offboarding closed their company login. A spreadsheet still appears every Monday. The weekly vendor chase that lived in their head does not.

Login closed; workflows still bound

A spreadsheet still appears every Monday. The weekly vendor chase that lived in their head does not.

Offboarding closes a login. It does not inventory the workflows that still run as that login, or the ones that only that person understood.

What vendor docs actually coverSourced note

Microsoft's former-employee series covers blocking sign-in, mailbox and OneDrive handover, devices, licenses, and deleting the user account.

Microsoft defines an orphaned flow as a flow that no longer has a valid owner, and states that such flows can fail if they use connections tied to that user account.

Microsoft documents that if a flow uses active or embedded connections belonging to a user who left, those specific actions might fail, and that another owner cannot change credentials for a connection they did not create.

Zapier's Team and Enterprise member-removal guide lets an admin choose whether a removed user's private app connections stay active for 30 days or until they expire, and states that shared connections continue working as long as the user's app account exists and until that app's expiration schedule.

Examples

Four things that can happen

What still runs, what silently stops, and what only they understood are different problems. Person-offboarding does not sort them.

Outcomes when ownership is unclear

What still runs, what silently stops, and what only they understood are different problems. Person-offboarding does not sort them.

After someone leaves, a workflow can keep running as their login, fail when a person-bound connection dies, remain visible but inoperable, or never have been written down at all.
What can happen	What it looks like	Who notices
Keeps running as them	Monday sheet still appears	Whoever still receives it
Fails when the connection dies	The flow is listed; the next run errors	Often nobody, until a customer asks
Visible, not operable	The definition is there; the connection is not theirs to change	The next person asked to just fix it
Never written down	The sequence lived in one person's week	The work simply stops

Documented mechanicsSourced note

Solutions

You cannot hand over what you cannot name

A workflow is not yours because it happens to keep running. It is yours when a named person can find it, say whose login it uses, stop it, and recover it.

For each row, write retire, rebuild, leave, or automate — with the reason. Do not treat account disable as the whole job.

Where leftover workflows hide

A named owner must be able to find each one. Lives in a former inbox and keeps filing or sending mail is not a closed offboarding item.

Where leftover workflows hide

Five ordinary places a departed login can still be doing work after the person can no longer sign in.

Mailbox rule or forwardLives in a former inbox and keeps filing or sending mail
Form to spreadsheetA personal connector still writes rows after they leave
Cloud flow in the personal spaceBuilt in the default environment every employee can use
Shared Zap or connectorStill authenticates as their app login until it expires
OAuth grantPermission that can outlast the human session

Register before rebuildSourced note

How Zoevin helps

Would you know what still runs as them?

One pass writes the register, names the login each workflow uses, and recommends retire, rebuild, leave, or automate for each row. I do not stay on afterwards to watch it.

A written register of what still runs.
The login each workflow uses.
Retire, rebuild, leave, or automate on each row.
A handover date — not a running watch.

Zoevin has no delivered automation projects yet. Discovery names the seam. If I build, I hand it over on a written date. You get the workflow, the logins, and the write-up. I don't stay on to run it. You buy the software.

See automation inventory and cleanup

Evidence

Sources

Primary reporting first. Open the sources yourself rather than taking this account alone.

primary source
Microsoft — Overview: Remove a former employee and secure data
First-party offboarding series covering sign-in, mailbox, devices, OneDrive, license, and account deletion. It does not inventory cloud flows, connectors, or OAuth grants.
primary source
Microsoft — Manage orphaned flows when the owner leaves the organization
First-party definition of an orphaned flow, connection-failure behaviour, admin-center identification, and PowerShell co-owner assignment. Last updated 15 June 2026.
primary source
Microsoft — Share a cloud flow
First-party documentation distinguishing owners from embedded connections, and warning that actions using a departed user's connections might fail.
primary source
Microsoft — Manage and govern the default Power Platform environment
First-party statement that every employee can use the default environment for personal productivity, and that a maker's apps and flows are in effect owner-less when they leave.
primary source
Zapier — Remove members from your Team or Enterprise account
First-party Team/Enterprise offboarding: transfer of Zaps and connections, 30-day or until-expiry private connections, shared connections that continue while the app account exists.
primary source
Zapier — Share app connections with members of your Team or Enterprise account
First-party documentation that connections are private by default, that a Zap pauses if it loses a connection, and that a shared mailbox-style app account is the safer share pattern.
primary source
OWASP — Non-Human Identities Top 10 2025, NHI1 Improper Offboarding
Independent project ranking inadequate deactivation of service accounts and access keys as the first NHI risk for 2025.