Start free trial
Start free trial
How-to 5 steps 3 min read Updated 11 November 2026

How to find and reassign ownerless Power Apps and flows

Find Power Apps and Power Automate flows whose owner has left, then assign a new owner or retire them.

Torsten Mandelkow Works with
How-to

What is an ownerless Power App or flow?

An ownerless Power App or flow is an app or automation whose maker has left or no longer answers for it, so nobody can edit, fix, or retire it. Finding them and giving each a new owner, or retiring it, keeps automation running under someone's responsibility.

In short

  • Apps and flows are built by one person, so they follow that person's employment.
  • An ownerless flow can keep running under a departed user's credentials.
  • Add a co-owner to everything that matters so a departure is not a crisis.
  • If nobody will own an app or flow, retire it.

Step by step

Five steps find the orphaned items and make sure they do not come back.

  1. List apps and flows with their owners

    Export apps and flows from every environment with owner, co-owners, creator and last modified date. Compare the owners with your list of active and disabled users from Entra ID.

    In Rencore:

  2. Flag items without a valid owner

    Mark every item whose owner is disabled, deleted or missing. Sort by the connections used and the number of people the app is shared with, so the highest impact items come first.

    In Rencore:

  3. Find a new owner

    Ask the heaviest user or the leaver's manager to take over. Add them, and a second person, as owners. Confirm they know what the app or flow does and which data it touches.

    Tip: Add a co-owner to every business-critical app now, so the next departure needs no search.

    In Rencore:

  4. Retire what nobody wants

    If no owner can be found, turn the flow off, set the app aside for 30 days, and delete it if nobody objects. Tell the people who had access.

  5. Make it part of offboarding

    Add a step to your leaver process that lists the apps and flows the person owns and reassigns each one. Run the same check on a schedule to catch the ones that slip through.

Why Power Apps and flows lose their owner

Low-code apps and flows are usually built by one person in a business team. When that person leaves or changes role, the app keeps running with their connections and permissions, but nobody can edit it or decide to switch it off.

Standard offboarding focuses on the account, the mailbox and the laptop. Apps and flows are not on the list, so ownership drifts unnoticed until a flow fails or an auditor asks who is responsible for it.

Connectors in this How-to

Each connector page in the Rencore docs lists the objects, policies, reports and actions behind these steps.

Common questions about ownerless Power Apps and flows

What happens to a Power Automate flow when its owner leaves?
It usually keeps running, using the connections and permissions of the departed user, until the account is deleted or a connection breaks. Then it fails, often silently, and nobody is notified because the one person who would be is gone. Until then a flow can keep moving data under credentials nobody supervises, which is why an ownerless flow is both an outage risk and a security finding.
Can I find ownerless apps and flows in the Power Platform admin center?
Partly. The Power Platform admin center lets you open an environment, see its apps and flows with their owners, and assign a new owner, one item at a time. It does not give you one list across all environments of items whose owner is disabled or gone, or a reminder when the next one appears. Teams with a few environments manage with exports and a schedule, and larger estates need that list built for them.
Who should become the new owner of an orphaned app?
Start with the person or team that uses it most, then the leaver's manager, and make that person a co-owner before the leaver goes, so the question never arises. If nobody wants the app, that is your answer: retire it. An app or flow that no one will own is one nobody is using, and keeping it costs license money and carries risk for no return.
How does Rencore find ownerless Power Apps and flows?
Rencore Governance has policies that flag Power Apps without owners and flows without owners, and it flags Copilot Studio agents with an ownership gap. Actions add owner users or groups to Power Apps and flows, so you fix the finding where you find it. The inventory also shows each app's environment, connections and sharing, which helps you decide who should take over.

Last updated 11 November 2026

About the author

Torsten Mandelkow

Torsten is co-founder and CAA at Rencore. During his time as a SharePoint consultant, he always tried to improve and automate the SharePoint development process, first by creating the SharePoint Software Factory (SPSF), and later by creating the SharePoint code analysis tools, today known as SPCAF. After an intermezzo for 3 years at Microsoft, he is now part of the RENCORE team and is responsible for the further technical development of all our tools.

Related

See the apps and flows nobody owns

We will show the ownerless app and flow policies and the actions that assign a new owner in a short demo.

Request a demoGet started free
Rencore newsletter

Subscribe to our newsletter

Get the latest insights on governing Microsoft 365, Copilot and AI agents, delivered to your inbox.

Loading form