Blog · Automation

When a Power Automate Flow Owner Leaves: How to Keep Their Flows Running

November 2026 · Behavior as described in Microsoft's Power Automate documentation cited below — confirm against your own tenant

Most Power Automate flows are built by one person to solve one problem, and they keep running long after anyone remembers who built them. Then that person leaves. Their account is disabled, their license is reclaimed, and a few days or weeks later the lead routing, the invoice filing or the weekly report stops. Nobody changed the flow. It simply belonged to someone who is no longer there. This post covers what Microsoft says happens to a departed owner's flows, the order to hand them over in, and how to make the next departure a non-event.

What happens to a flow when its owner leaves

Microsoft calls a flow with no valid owner an orphaned flow, and its troubleshooting article is direct about the risk: these flows "can fail if they use connections tied to that user account." Connections are the signed-in links to Outlook, SharePoint, Dataverse and the rest, and a flow built by one person usually runs on that person's connections.

Licensing is the second clock. Power Automate's licensing FAQ addresses this exact case: when the owner of a flow has left the organization, the flow is downgraded to lower performance, all flow owners are notified, and the flow is turned off in 14 days if no action is taken. A scheduled or automated flow runs under its owner's license, so when the owner goes, the flow loses the license it was running on.

Why the warning often lands nowhere

That notification goes to the flow's owners. If the only owner is the person who left, the email arrives in a mailbox nobody reads, and the first sign of trouble is the absence of whatever the flow used to produce. We covered the other rules that switch flows off, and a routine for noticing, in why Power Automate turns your flow off. A departure is the case where all of that advice gets tested at once.

The handover, in order

1. Find every flow the person owns. Do this before the account is disabled, while the flows still show the owner's name. An admin can list them with the Get-AdminFlow cmdlet and its -CreatedBy parameter, or look through an environment's flows in the Power Platform admin center. Ask the person which ones matter; they know which flows other teams quietly depend on.

2. Add a co-owner to each flow that matters. A co-owner keeps someone in the loop who can edit the flow, receive its notices and, for flows that are not in a solution, export and re-import it later. It is the cheapest step and the one that makes every later step possible.

3. Move the ownership itself. How depends on the kind of flow:

Solution-aware flows can have their owner changed in place. In Power Automate, open the flow, select Edit in the Details section, remove the current primary owner and enter the new one. The new owner gets the run history and connection references, and the previous owner stays on as a co-owner. Microsoft notes the switch to the new owner's license can take up to seven days to take effect for scheduled and automated flows; editing and saving the flow forces it immediately.

Flows outside a solution cannot have their owner changed in place, because the owner is part of the flow's identity. If the environment has Dataverse, add the flow to a solution first and then change the owner. If it does not, a co-owner can export and import the flow (or use Save as); the imported copy is a new flow that the co-owner owns and that runs on their license. Turn the old copy off once the new one is confirmed running, so the work does not happen twice.

4. Check licenses and connections. If the flow uses premium features and the new owner does not hold a premium license, Power Automate warns at the handover; Microsoft's documentation says the flow keeps running for 30 days to give the new owner time to get one, then turns off. Open each flow and replace any connection still signed in as the departed user with one the new owner controls, then trigger a test run and read the run history.

If the account is already gone

Admins can still recover. In the Power Platform admin center, open the environment, go to Resources, then Flows, and look for flows with nothing in the Owners column. Select one, choose Share and add a new owner. For many flows at once, Microsoft documents the Get-AdminFlowOwnerRole and Set-AdminFlowOwnerRole cmdlets and an example script that lists every flow in an environment without a valid owner. Once a new co-owner is in place, continue from step 3 above.

Make the next departure boring

The durable fix is to stop tying business-critical flows to one person's account. Microsoft supports a service principal application user as a flow's owner: a non-human identity that cannot resign. You share the flow's connections with it and change the owner through the same Details edit dialog. It comes with its own trade-offs, since a service principal has no user license and is subject to non-licensed request limits, so read Microsoft's licensing notes before moving a high-volume flow.

Short of that, two habits cover most of the risk: every flow that matters has at least two owners, and "list and hand over your flows" is a line on the offboarding checklist next to returning the laptop.

The takeaway

A flow does not know its builder has left until the license and the connections stop answering. Finding the person's flows before the account goes, adding a co-owner, moving ownership properly and re-pointing connections turns a silent failure into a twenty-minute handover. If the flows that matter are also the ones running close to their limits, our guides to the 429 rate-limit error and credit consumption are the next read.

Sources: Microsoft Learn, Manage orphaned flows when owner leaves organization; Microsoft Learn, Change the owner of a cloud flow in Power Automate; Microsoft Learn, Power Automate licensing FAQ.

Automation that depends on one person is a staffing risk, not a system. The audit maps which flows your operations lean on and who can actually maintain them.

Book an audit

← All posts