Power Automate troubleshooting

When a Power Automate flow owner leaves: what breaks, how to find orphaned flows, and the four fixes

When a Power Automate flow owner leaves the company, their flows rarely stop on day one. They keep running until a connection signed in as that person fails, a premium flow loses its owner’s licence, or something needs editing and nobody left has the rights. This guide is for the point where flows have already broken: how to find every flow the person owned, and which of four fixes — a co-owner, a new owner, a solution or a service account — fits each one.

It covers flows that broke because a person left. If nobody has left and Microsoft switched a flow off for inactivity, continuous errors or licence enforcement, that is a different cause with different fixes, covered in our guide to why a Power Automate flow gets turned off. If the same departure also left reports and semantic models without an owner, our guide to what happens when a Power BI report owner leaves covers the Power BI side. For the canvas apps they built, our guide to what happens when a Power Apps owner leaves explains who can still edit them and how an admin reassigns ownership. Every rule below was checked against Microsoft’s documentation on October 28, 2026.

What actually breaks when the person who built a flow leaves?

Usually nothing breaks on the day they leave. The flow keeps its trigger and keeps running until something it depends on stops working: a connection signed in as the departed user can fail once their account is disabled, a premium flow loses the owner’s licence, or a warning email lands in a mailbox nobody reads. Then it stops quietly.

Microsoft calls a flow with no valid owner an orphaned flow. Its troubleshooting article on orphaned flows (opens in new tab) notes that these flows can fail if they use connections tied to that user account. The table sets out the five things that depend on the owner and what happens to each.

What depends on a Power Automate flow owner, and what happens when they leave
Depends on the ownerWhat happens after they leaveWhat to do
Connections signed in as themActions using those connections can fail once the account is disabled, so automated and scheduled flows start showing failed runsRe-create the connections under a current owner, a service account or a service principal
Their Premium licenceAutomated and scheduled flows run in the owner’s licence context; Microsoft’s licensing FAQ says a premium flow whose owner loses Premium is downgraded to lower performance, owners are notified, and the flow is turned off in 14 days if no action is takenGive the flow a new owner who holds Premium, or assign it a Process licence
The right to editIf they were the only owner, nobody can change the flow until an admin assigns someoneAn admin adds a co-owner from the admin center or PowerShell
Warning emailsInactivity and failure notices go to owners and co-owners, so a sole owner’s warnings go unreadAdd a co-owner who is still here; the 90-day inactivity rule is covered in our flow-turned-off guide
Instant (manual) flowsThese run under the licence of whoever triggers them, so the owner’s licence ending does not affect who can run them; connections in the owner’s name can still failCheck the connections, and add a co-owner so the flow stays editable

Want this worked through for your own orphaned flows? A free consultation is the first step.

Book my free consultation →

In a small business the pattern is usually the same: one person built most of the automation, often in the default environment, and nobody else is listed as an owner. When that person leaves, the IT checklist disables their account and licence, and the flows they owned are not on it. If a flow is triggered by new form responses, the form usually belongs to the same person, and our guide to keeping a Microsoft Forms owner’s forms and responses after they leave covers moving it before the account is deleted.

How do you find the flows a departed employee owned?

Ask an admin to look in the Power Platform admin center: open the environment, go to Resources, then Flows, and look for rows with nothing in the Owners column. For a specific person, the Get-AdminFlow PowerShell cmdlet with the CreatedBy parameter lists every flow they created in that environment.

Three practical points from that process. First, only users with appropriate admin privileges can see flows that have no valid owner, and the admin center list loads in pages, so keep selecting Load more until the list ends. Second, the check is per environment; a tenant with several environments needs it in each one. Third, a flow that still has a co-owner listed will not look orphaned, even though it may still run on the departed person’s connections and licence — so search by creator as well as by empty owner.

For larger tenants, Microsoft publishes a sample script that loops through every flow with Get-AdminFlowOwnerRole and reports those with no owner who still exists in Microsoft Entra ID. The sample uses Get-AzureADUser from the AzureAD module, which Microsoft has deprecated in favour of Microsoft Graph PowerShell, so expect to adapt that lookup before running it.

Which fix fits: a co-owner, a new owner, a solution or a service account?

Pick by what the flow needs. A co-owner restores editing. Changing the owner gives someone current the licence context, run history and connection references, but only works for solution-aware flows. Adding the flow to a solution unlocks that change. A service account or service principal stops the next departure repeating the problem.

Four fixes for a Power Automate flow whose owner has left, compared
FixHowWorks forThe catch
1. Add a co-ownerAdmin center: select the flow, then Share; or Set-AdminFlowOwnerRole with the CanEdit roleAny cloud flowRestores editing, but automated and scheduled flows still run in the owner’s licence context, so it does not fix a premium licence gap
2. Change the primary ownerFlow Details, Edit, Primary owner; the old and new owner both become co-ownersSolution-aware flows only; an owner, co-owner or admin can do itThe new owner’s licence can take up to seven days to apply; a new owner without Premium gets a 30-day grace period on a premium flow
3. Put it in a solution, or copy itWith Dataverse, add the flow to a solution and then change the owner; without it, export and import, Save as, or Send a copyFlows created outside a solutionA copy is a new flow owned by whoever made it, so turn the old one off and update anything that referenced it
4. A service account or service principalMake a licensed service account the owner, or a service principal application user with the connections shared to itBusiness-critical flows that should outlive any one employeeA shared account with one Premium licence is multiplexing; a service principal has no user licence and cannot be a co-owner

Microsoft’s guide to changing the owner of a cloud flow (opens in new tab) walks through fixes 2 and 4. One step people miss: an admin who wants to edit a flow must first make themselves an owner or co-owner; admin rights alone do not open the editor.

Why can’t you change the owner of some flows?

Because for a flow created outside a solution, the owner is part of the flow’s identity, so Microsoft does not let you swap it in place. If the environment has Dataverse, add the flow to a solution and then change the owner. If it does not, a co-owner makes a copy under a new owner instead.

Most flows built from the My flows page in a small business are not in a solution, which is why the change-owner option is often missing when people go looking for it. You can tell from the flow’s details: a solution-aware flow can be found under Solutions. Microsoft’s licensing FAQ adds one more route for a non-solution flow that has to keep running: assign it a Power Automate Process licence, which licenses the flow itself rather than any user.

What licensing catches come with each fix?

Four. A new owner without Premium gets 30 days before a premium flow is turned off. The switch to the new owner’s licence can take up to seven days. One Premium seat on a widely shared account is multiplexing. And a service principal has no licence, so it runs under Microsoft’s non-licensed request limits.

  • The 30-day grace period. If you assign a premium flow to an owner without a premium licence, Power Automate warns you, runs the flow for 30 days, then turns it off. It can be turned on again once the licence is bought. Separately, if a premium flow’s existing owner simply loses Premium — the usual situation when someone leaves — the licensing FAQ says owners are notified and the flow is turned off in 14 days if no action is taken.
  • The up-to-seven-day licence switch. After an ownership change, scheduled and automated flows move to the new owner’s licence and request limits, which can take up to seven days. Editing and saving the flow forces the switch immediately.
  • Multiplexing. Microsoft’s licensing guidance on multiplexing (opens in new tab) says one Premium licence on a service account that many users share is not compliant. Standard-connector flows need no licence; premium flows on a shared account need the account and its small set of users licensed, or a Process licence on the flow.
  • Service principal request limits. A service principal application user is a non-interactive user with no user licence, so its flows fall under non-licensed request limits. Microsoft’s options include pay-as-you-go, associating the flow with an app, a Process licence, or a flow group that shares one Process licence across up to 25 solution-aware flows.

Microsoft also recommends a service principal over a shared service account, because shared credentials are a security risk and make it hard to see who changed a flow. Where the seeded Microsoft 365 rights end and Premium begins is explained in our Power Automate licensing guide for small business.

How do you stop the next departure breaking flows?

Make flow ownership part of offboarding. Before an account is disabled, list the flows that person owns, move each one to a current owner or a service principal, and re-create the connections they signed in. Give every flow that matters a second owner now, so the next person who leaves is never the only one. The same gap shows up on team sites, which is why our guide to what to do when a SharePoint site owner leaves covers the matching SharePoint step.

That one step is what most offboarding checklists are missing, and the backlog of ownerless apps and flows grows quietly until a scheduled flow fails. Our Power Platform governance consulting includes an ownerless-resource review against your tenant inventory and writes the Power Platform step into your offboarding process, scoped as a fixed fee. If you would rather someone else watched the flows, fixed connections and handled each departure as it happens, that is what our Power Automate support and maintenance service covers.

FAQ

Questions people ask after a maker leaves

Yes. An admin can add a new co-owner from the flow list in the Power Platform admin center or with the Set-AdminFlowOwnerRole PowerShell cmdlet. To edit the flow itself, the admin must first make themselves an owner or co-owner. Changing the primary owner needs a solution-aware flow.

It fixes the access problem, not always the running problem. A co-owner can edit the flow and re-create broken connections. But automated and scheduled flows run in the context of the owner, so a premium flow whose owner has lost their licence still needs a new owner or a Process licence.

Yes, if it is licensed correctly. Standard-connector flows need no extra licence. For premium flows, Microsoft treats one Premium licence on an account that many people share as multiplexing, a licence violation. License the service account and the small, fixed set of users who share it, or put a Process licence on the flow.

For scheduled and automated flows, up to seven days after the ownership change. Microsoft's documented shortcut is to edit the flow and save it, which forces it onto the new owner's licence immediately. Manual flows are unaffected, because they always run under the licence of whoever triggers them.

Yes, and for a flow outside a solution in an environment without Dataverse it is the usual route. A co-owner can export and import it, or use Save as or Send a copy. The result is a new flow that they own, running on their licence, so turn the old one off once the copy works.

Want a second opinion on your orphaned flows?

A senior US-based engineer talks it through with you first, at no cost. If there is work worth doing, you get a written scope with one price, and you approve it before anything starts.

Free consultation · Written fixed price before any work starts · Reply within one business day

Book a free consultation

See what your Power Automate project would take

Tell us what you’re trying to fix. We reply within one business day, and you get a written fixed-fee proposal to approve before any work begins.

Step 1 of 2: What do you need?

How can we help? Pick one

Tap to add, or type your own:

Step 2 of 2: Where should we reply?

Used only to contact you about this inquiry.

We reply within one business day. Fixed price approved before any work begins. We don’t sell your information.

Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.

  • Fixed-fee scope agreed before any work starts
  • Senior, US-based Microsoft engineers — no handoffs
  • Typical 2–4 week delivery
  • 30 days of post-delivery hypercare included
Book my free consultation