Changing the owner of power platform elements

Table of contents

What you need
Administration
Requirements for the new owner
Changing the owner of …
Power Automate Flows
As a maker
As an admin
Power Apps
Using a flow
Connection References, Environment variables, AI Models
Chatbots
Changelog

☝

TL;DR - Changing the owner of flows, apps, environment variables or connection references is sadly not always possible for a maker. This article describes the current possibilities for makers and admins. I will update this soon with some automation and Power Automate. In the meantime, use the CoE Toolkit for this.

What you need

Administration

You will need an account that has either Power Platform Administrator rights or is in the role of System Administrator for the environment you want to change owners in.

In both cases you should check if you have the security role of System Administrator assigned to that account in the environment you want to change those in.

💡

For some elements (apps or flows) you can also use the CoE Toolkit to have a nicer interface for it. I highly recommend installing it.

Requirements for the new owner

When changing the owner of any of those elements, make sure the new owner has:

optionally a Premium license if any of the elements requires it
has at least the Environment Maker and Basic User security roles assigned in that environment (if its the default environment, you are good, otherwise add those roles directly or via a group to that user)

Changing the owner of …

Power Automate Flows

As a maker

This is available from the Power Automate Maker Portal.

🚨

The flow needs to be solution-aware, meaning it has to be part of a solution. Otherwise, you basically would have to create a copy of the flow when you are allowed to edit. https://learn.microsoft.com/en-us/power-automate/change-cloud-flow-owner#change-the-owner-of-a-non-solution-cloud-flow

If you flow is solution-aware:

Open the details of each flow, then click “Set primary owner”.

Select the new owner from the people picker box at the bottom, click save. You might need to save twice, the interface is not very responsive from time to time.

As an admin

Use Center of Excellence Toolkit.

Power Apps

Either use the Center of Excellence Toolkit or built a quick flow to change the owner.

Using a flow

🚨

You will need the Power Apps for Admins connector, which might be blocked by a data policy. You can create an extra admin environment and only allow that connector there.

Create an instant flow
Add the action “Set App Owner” and create a connection if necessary.
Configure the action as follows:

Environment Name = Environment id (take this ID from the Power Platform Admin Center.
PowerApp Name = App Id (take the ID from the app details)
Add from advanced parameters: New PowerApp Owner = User ID of new owner (take the ID from Entra ID or use a Office 365 user action before to get the ID from the users email)
Optionally: Role For Old App Owner = Set to CanEdit or CanView

Connection References, Environment variables, AI Models

🚨

As of December 2025 Microsoft is rolling out their new “Environment settings app” (Source: https://learn.microsoft.com/en-us/power-platform/admin/environment-settings-app), which breaks this method of re-assigning owners. You will have to use the CoE Toolkit for this now. Environment variables and AI models are sadly not supported yet. Connection references can be reassigned. The classic version used the advanced settings from the power apps maker portal per environment.

Chatbots

Coming soon, but only via PowerShell for now.

GA 30th June 2025: https://admin.microsoft.com/#/MessageCenter/:/messages/MC1085991

Thanks for reading! 💕

Changelog

Date	Changes
09.06.2025	Initial creation
18.12.2025	Updated connection reference, environment variable and AI Models method