Only flows within a solution can be transferred during an owner change. Here is how to check whether your flow stays recoverable.
Whether ownership of a Power Automate flow can be transferred is decided by a single technical switch: whether the flow is part of a solution or not. For a solution-aware flow, you change the owner directly in the Edit dialog. For a flow outside a solution, this is not possible according to Microsoft documentation, because the owner is a fixed part of the flow identity. Anyone who wants to ensure that a flow remains recoverable when an employee leaves must put it into a solution beforehand. As of: July 2026.
According to the Microsoft documentation on solution-aware flows, a solution is a container that makes flows and other components portable, allowing them to be moved between environments, for example from a sandbox environment to a test environment and from there to the production environment. Flows that you create within a solution are called solution-aware flows, and a solution can bundle several of them. The prerequisite is Dataverse in the respective environment and a platform version of 9.1.0.267 or higher. Without Dataverse there are no solutions and therefore no direct owner change.
For a solution-aware flow, owners, co-owners or administrators can transfer ownership to another person in the Details area via the Edit button. After the change, the previous and the new owner are jointly co-owners of the flow, and the new owner gains access to the run history and connection references. For scheduled or automated flows, it can take up to seven days before the flow actually runs under the new owner's license, unless you manually edit and save the flow again to force the change immediately. For manually triggered flows, the license of the person currently running the flow always applies. For a flow without a solution, however, an in-place change is, according to the Microsoft documentation on changing the flow owner simply not provided for, because the owner is part of the flow identity itself, not just an interchangeable attribute.
For a standalone flow, according to Microsoft, two paths remain. If Dataverse already exists in the environment, the existing flow can be added to a solution afterwards, after which the owner change works as described above. If Dataverse is missing, the only option is the detour via export and import, via the Save As function, or via Send a Copy, in each case creating a new, technically independent copy of the flow rather than the original flow itself changing owner. For more on the consequences when a flow owner leaves the company, see our article Power Automate flow owner leaves the company.
For governance in small and medium-sized companies, this means: the decision whether a flow sits in a solution should not happen by chance, but be made deliberately when the flow is created. Anyone who builds flows in a solution from the start secures the ability to transfer ownership later without data loss and without a new copy. Anyone who has flows built outside a solution, for example because the team works without Dataverse, should know that a personnel change will then always require an export-import exercise. At NordFlux, we place automated processes in digitalization projects into solutions by default, so that control stays within the company regardless of who originally created the flow. For more on our approach, see Power Automate. One limitation remains, though: a solution does not replace documentation of who maintains which flow and why, that remains an organizational task.
Yes, provided Dataverse is available in the environment. You add the existing flow to a solution, after which the regular owner change is available to you via the Details area. Without Dataverse this path is not possible, then only export and import or Save As remain.
The previous owner is not removed, but becomes a co-owner. Both people then have full access to the flow until someone actively revokes that access.
Solutions themselves require Dataverse, not a specific license tier. Whether a flow needs a premium license depends on the connectors used and is independent of whether the flow sits in a solution.
For scheduled or automated flows, up to seven days if you do nothing further. If you edit and save the flow again after the owner change, the new license applies immediately. For manually started flows, the license of the person running it always applies anyway.
Founder of NordFlux. Spent four years automating processes at enterprise scale at Dräger, and now brings that depth to the mid-market — pragmatic and with full data sovereignty.
Certifications
Scope organizes, Condition decides yes/no, Switch branches multiple ways: comparing the three control structure building blocks in Power Automate.
Only flows inside a solution can be transferred cleanly to a new owner; all the others quickly become an orphaned risk the moment someone leaves. NordFlux checks your existing flow landscape for exactly this gap and sets up governance that absorbs the loss of any single person.
