Power Platform Community Forum Thread Details

Hi there,

I am curious how others navigate flow ownership in mid-size companies considering flows must be run off a single-user account. Ie. when employees leave, there is no quick/ streamlined way to transfer flows to a group ownership or even another individual (I know how to copy flows but this is still cumbersome). Also, this silos content and workflows- any updates or workarounds?

Categories:

General topics

Hey@MF-14012119-0 For mid-size orgs work around this by using a service account to own production flows, adding multiple co-owners, and placing flows inside Solutions so Environment Admins can manage them if the original creator leaves.

Some links for your reference:

You can change the owner of a solution-aware flow (e.g., solution flows can be reassigned to another user) — but for regular flows you often need to export/import or use co-owners as a workaround. (Microsoft Learn)

Official Microsoft guidance on flow ownership and best practices:

Power Automate docs explain different ownership models (service principal vs user) and how co-owners work. (Microsoft Learn)

Managing flows when the owner leaves:

Microsoft has a troubleshooting page on how to handle orphaned flows and adding new owners/co-owners when someone leaves. (Microsoft Learn)

You can include one or more of these in your answer with links such as:

This gives your forum post an authoritative link explaining why service accounts and solutions are recommended for continuity.

If it helped you, please click "Does this answer your question?" and give it a like or mark it as Solution, it helps others in the community find answers more easily!
Connect With Me:
💼 LinkedIn: Clavin Fernandes
📺 YouTube: Clavin Fernandes
📝 Blog: clavinfernandes.wordpress.com
🌐 Community Website: PPUG.org
👥 Join our Community: Power Platform User Group