Post

Change a Power Automate Flow Owner Without Breaking It

Diesen Beitrag auf Deutsch lesen

Make the flow solution-aware and add a co-owner instead of exporting and re-importing — connections and run history stay untouched.

TL;DR

Make the flow solution-aware, open its details, and add a new owner — the original and new owner become co-owners so nothing breaks, connection references and run history stay intact, and no export/import is needed. For scheduled flows the new owner’s licence takes effect within about 7 days unless you edit and re-save to apply it immediately.

Original by Marcel Lehmann, on PowerPlatformTip. Read the original

This is our own summary, not a republication or full translation. Both publications are edited by Marcel Lehmann.

Governance takeaway

  • Admins/CoE: replace the export/import runbook with this co-owner step during offboarding — it takes seconds and never touches connection references. Turn “does this flow have an active owner” into a field you check, not a chase you run after someone has already left.
  • Makers: when you inherit a flow, you keep its full run history instead of starting trust in a fresh copy from zero.

Frequently asked questions

Is it possible to hand a cloud flow to a new owner without export and import?

Yes, if the flow is solution-aware. Add it to a solution in a Dataverse-enabled environment, open the flow details, choose Edit and add the new owner.

Do the old and the new flow owner both stay on the flow?

Yes. The original owner and the new owner become co-owners, so nothing breaks.

How long until the new owner license applies to a scheduled flow?

For scheduled or automated flows, the license of the new owner takes effect within about 7 days. Editing and saving the flow again applies it immediately.

This post is licensed under CC BY 4.0 by the author.