Power AutomateWhat happens to Power Automate flows when the maker leaves (and how to fix it)

When the person who built a Power Automate flow leaves and their account is disabled, the flow usually keeps existing but stops working, because it runs on that person's connections and, often, their licence. Nothing warns the business until an approval goes missing or a report does not arrive. The fix is to find ownerless flows before the account is removed, move them to a service account or co-owner, and build future flows so they never depend on one person.

At the time of writing (October 2026). Power Platform admin tooling changes often. The menus, PowerShell cmdlets and retention windows mentioned here reflect Microsoft documentation at the time of writing. Check current documentation before relying on a specific step.

Why flows break when someone leaves

A cloud flow depends on three things that are usually tied to its maker.

There are quieter problems too:

• Files in the leaver's OneDrive. A flow that reads a spreadsheet from a personal OneDrive breaks when that OneDrive is deleted after its retention period.
• Emails sent as the leaver. Notifications that came from the leaver's mailbox stop, or come from a disabled account.
• Inactive flows. At the time of writing Microsoft can turn off flows on Microsoft 365 licences that have not run for an extended period, with an email warning to the owner, which nobody reads once they have gone.

Signs you already have a problem

• An approval or notification process has gone silent.
• Failed run emails are going to a mailbox nobody monitors.
• Nobody can explain who built a business-critical flow.
• The flow shows in the admin centre but not in anyone's "My flows" list.
• A connection shows as broken or needing to be fixed.

Our ownerless flows use case describes what a typical rescue involves.

Step 1: Find ownerless and at-risk flows

You have three main options, depending on the size of your estate.

• Power Platform admin centre. Admins can browse flows by environment and see owners. Useful for a small number of environments.
• PowerShell. The Power Apps administration PowerShell module lets admins list flows across environments with their owners, then compare those owners against disabled or deleted accounts in Microsoft Entra ID.
• CoE Starter Kit. The kit's inventory flags flows whose owners no longer exist and can notify admins. See our CoE Starter Kit guide.

For each flow found, record the environment, owner, last run date, connectors used, whether it is in a solution and who in the business depends on it.

Step 2: Recover access

Act before the account is deleted if you possibly can. Once an account has gone, recovery is harder.

If the account is disabled but still exists

• Add a co-owner. Admins can add owners to flows they cannot otherwise see, through the admin centre or PowerShell.
• For flows in solutions in a Dataverse environment, change the owner to a service account.

If the account has been deleted

• Microsoft Entra ID keeps deleted user accounts in a soft-deleted state for a limited period, typically 30 days. Restoring the account temporarily can be the quickest way to regain control.
• Admins can still reassign or add owners to many flows from the admin side.
• If a flow itself was deleted, admins can restore some non-solution flows using PowerShell within a limited window (Microsoft documents around 20 days at the time of writing).

Step 3: Repair the flow

Gaining ownership is only half the job. The flow still runs on the leaver's connections.

• Replace each connection with one owned by a service account or the new owner.
• Move files from the leaver's OneDrive to a SharePoint site the team owns.
• Change "send from" settings to a shared mailbox where appropriate.
• Check the licence. If the flow uses premium connectors, the new owner needs premium licensing, or attach a Power Automate Process licence to the flow itself.
• Test with real data, then watch the next few runs.

If the flow is not in a solution, this is a good moment to add it to one, with connection references so future changes are a single update.

Step 4: Stop it happening again

Use a service account for business-critical flows

A licensed, non-personal account owned by IT, with multi-factor authentication and a named custodian. Business-critical flows run on its connections. It does not leave when people do.

Build in solutions with connection references

Solutions let you move flows between environments, and connection references mean one connection can be swapped for another without editing every action.

Always add a co-owner

Every flow that matters should have at least two owners, ideally a team or security group rather than an individual.

Consider Process licences for shared flows

A Process licence attaches to the flow, not to a person, so licence coverage does not disappear with a leaver.

Add Power Platform to the leavers process

Most offboarding checklists cover email and files but not flows. Add a step that checks for flows, apps and agents owned by the leaver before their account is disabled.

Monitor failures centrally

Send failure notifications to a shared mailbox or Teams channel, not the maker's inbox.

Our governance service sets up these controls, and a monthly Care Plan (from £495 a month) includes monitoring and fixing broken flows.

Leaver checklist for Power Platform

• Identify flows, apps and Copilot Studio agents owned by the leaver.
• Confirm with their manager which are still needed.
• Add a co-owner or change ownership to a service account.
• Replace connections that use the leaver's account.
• Move files from their OneDrive to SharePoint.
• Reassign or add licences where premium connectors are used.
• Update failure notification recipients.
• Disable the account only after the above is complete.
• Record what was changed and where.

A worked example

This is an illustration, not a client case study. A purchase approval flow was built by an operations manager who has since left. It reads a spreadsheet in their OneDrive, posts approvals to Teams and emails suppliers from their mailbox. Their account is disabled on their last day.

The next morning approvals stop. An admin finds the flow through the admin centre, adds a service account as co-owner, moves the spreadsheet to the operations SharePoint site, swaps each connection to the service account and changes the supplier emails to come from a shared mailbox. The flow is added to a solution and given a second human owner. Total effort is modest; the expensive part was the days of missed approvals before anyone noticed.

Frequently asked questions

Do flows stop immediately when someone leaves?

Usually when their account is disabled or their licence is removed. Some flows fail on the next run; others fail when a token expires. Either way, assume they will stop.

Can an admin see flows they do not own?

Yes. Power Platform admins can list flows across environments in the admin centre or through PowerShell, and can add themselves or others as owners.

Should we use a shared service account for all flows?

For business-critical flows, a dedicated, licensed service account with a named custodian is good practice. Personal productivity flows can stay with individuals.

Does a Process licence fix ownership problems?

It fixes the licence dependency, not ownership or connections. Combine it with co-owners, service account connections and solutions.

We have already lost a flow. Can it be recovered?

Often, if you act quickly. A soft-deleted account can be restored for a limited period, and some deleted flows can be restored by an admin. Our support service handles urgent recovery.

Key takeaways

• Flows depend on their maker's ownership, connections and licence, so leavers break them.
• Find at-risk flows before accounts are disabled, using the admin centre, PowerShell or the CoE Starter Kit.
• Recover access, then replace connections, move files and check licences.
• Prevent repeats with service accounts, solutions, co-owners and a leavers checklist.
• If flows have already stopped, book a call below and we will help you triage.