Others

How to Transfer Ownership of a Power Automate Flow from a Former Employee

Bushra Parveen Oct 21, 2026 869 views

Question details

The user needs to reassign ownership of a Power Automate flow that was created by an employee who has left the company.

How to Transfer Ownership of a Power Automate Flow from a Former Employee

Product: Microsoft Power Automate
Device & OS: not provided
Scenario: An employee has departed the organization, and their automated workflows need to be transferred to a new owner so that operations continue smoothly without connection failures.
Observed behavior: Flows owned by the former employee fail when their account connections are disabled, replaced, or when the flow is imported into another environment without proper ownership transfer.

Before you start

Ensure you have Power Platform administrator or environment administrator privileges, as these are generally required to change ownership of flows on behalf of former employees.

Solution 1Recommended

Transfer Ownership of a Solution-Aware Cloud Flow

The standard administrative method for reassigning ownership of flows that were built within a Power Platform solution.

Solution-aware flows are contained within a specific solution in the Power Platform environment. An administrator must perform the transfer to ensure all dependencies and connections are properly preserved.

Access Admin Settings

Locate the Flow

Navigate to the specific environment where the former employee's flow resides, then open the corresponding solution.

Change the Owner

Select the flow, click on 'Edit', and update the flow owner to a current, active user in the organization.

Update Connection References

Ensure that the new owner authorizes and updates all connection references used within the flow so it can run using active credentials.

Transfer Ownership of a Solution-Aware Cloud Flow

Administrator Requirement: Only an administrator can perform this action if the original owner's account has already been disabled.

Solution 2

Transfer Ownership of a Non-Solution Flow

A manual workaround for standalone flows that are not part of a broader solution.

Free Microsoft Office alternative

Experience Lightweight and Hassle-Free Office Productivity with WPS Office

While resolving complex Microsoft Power Automate flow ownership requires deep administrative access and troubleshooting, your daily document tasks shouldn't be a burden. WPS Office is a lightweight, fully-featured alternative to Microsoft Office that empowers your team with seamless collaboration and effortless document management without complicated account dependencies.

Fully compatible with Microsoft Excel, Word, and PowerPoint file formats.Free and lightweight, minimizing system resource consumption.Familiar tabbed interface guarantees zero learning curve for new employees.Built-in PDF editing tools out of the box.

microsoft office alternative - wps office

Frequently Asked Questions

Why does a Power Automate flow fail after the owner leaves the company?

Flows typically rely on the original creator's personal account connections (such as their Outlook or SharePoint login). When their user account is deactivated by IT, those connections break, causing the automated flow to fail.

Can I export and import the flow to fix the ownership issue?

Exporting and importing a flow is not recommended for transferring ownership. It often fails to preserve the original permissions, historical run data, and connection references. Using the admin center to reassign ownership is the proper method.

Who has the permission to change the owner of a flow?

To change the ownership of a flow without the original owner's involvement, you must be a Power Platform Administrator or a designated Environment Administrator.

Office Quick Solutions