Reassigning Power Apps Ownership: Three Methods Every Admin Should Know

One of the administrative tasks that often catches teams off guard is transferring ownership of a canvas app after the original creator has left the organisation. Without a current owner, performing updates, modifying permissions, or even deleting the app becomes unnecessarily complicated. This article walks through three reliable approaches to reassign ownership so you can keep the app under active management.

Why Ownership Transfer Matters

Imagine a Sales Tracker app built by a developer in the Contoso Electronics sales team. That developer departed six months ago, but the app still runs daily. Now the sales director needs to add a new view, and only the app owner can publish changes. Without ownership transfer, the team would have to recreate the app from scratch.

Whether you’re dealing with a single app or dozens, knowing how to change the owner efficiently saves hours of manual work.

Information You’ll Need Before You Start

Every transfer method requires three identifiers. Collect them ahead of time to avoid interruptions.

• Environment ID – From the Power Apps maker portal, open the gear icon > Developer resources. The Environment GUID is displayed at the top of the panel.
• App ID – In the maker portal, go to Apps, select the app’s details (⋮ > Details). The App GUID appears in the details pane.
• User Object ID – Sign in to the Azure portal, search for the user who will become the new owner, and copy the Object ID from their profile page.

Method 1: Automate With Power Automate

If you prefer a no‑code solution, the Power Apps for Admins connector provides a Set App Owner action. This method is ideal when you need to transfer ownership infrequently and want a repeatable process.

1. Create a new Power Automate flow with any instant trigger, such as Manually trigger a flow.
2. Add the action Set App Owner (from the Power Apps for Admins connector).
3. Fill in the three identifiers:
   • Environment Name – paste your Environment ID
   • Power App Name – paste your App ID
   • New PowerApp Owner – paste the new owner’s Object ID
4. Run the flow.

The action does not require any additional configuration. If the flow completes successfully, the new owner appears in the app’s details page immediately.

Method 2: Use PowerShell for Bulk Operations

Admins who manage multiple environments or handle frequent transfers will appreciate the PowerShell approach. The Set-AdminPowerAppOwner cmdlet is part of the Microsoft.PowerApps.Administration.PowerShell module.

Save the following script as Transfer-Owner.ps1 and replace the placeholder GUIDs with your own values.

# Provide the values you collected earlier
$EnvironmentName = "Default-f1b8b509-50a4-4a5c-8e48-bf3d3e7c10ed"
$AppName         = "3b328263-ef5e-4db8-b360-d74eb474b8af"
$NewAppOwner     = "6857d910-10c3-485e-a492-6456ce2f1625"

Set-AdminPowerAppOwner -AppName $AppName -AppOwner $NewAppOwner -EnvironmentName $EnvironmentName

Run the script in an elevated PowerShell console. If the cmdlet returns without errors, the ownership has been changed.

Method 3: Leverage the CoE Starter Kit

The Microsoft Center of Excellence (CoE) Starter Kit includes a ready‑built canvas app called Admin – App Permission Center that allows admins to manage app ownership through a graphical interface.

1. Open the Admin – App Permission Center app (usually installed in your CoE environment).
2. Browse to the environment that contains your app.
3. Select the app you want to transfer from the list.
4. Click Add Permissions.
5. Search for the new owner, select their account, and assign the role Owner.
6. Click Save.

The CoE solution automatically validates that the new owner has the necessary licenses and exists in the tenant. It also logs the change for audit purposes.

Security and Permissions Considerations

• To change the owner via any method, you must have the Power Platform admin role or the Environment admin role in the target environment.
• The current owner does not lose their access unless you explicitly remove their permissions after the transfer. If the former owner is already disabled, this is irrelevant.
• Azure AD guest users can become owners as long as they meet licensing requirements.
• PowerShell and Power Automate actions only require the Object ID; you do not need the user’s display name or email.

Common Mistakes

Mistaking the Environment ID for the Environment URL – The flow and PowerShell cmdlet expect the full GUID, not the make.powerapps.com URL segment.

Using the original owner’s account – Ensure the NewAppOwner parameter is the Object ID of the new owner.

Skipping the Power Apps for Admins connector – The standard Power Apps connector does not have the Set App Owner action. Use the Power Apps for Admins connector.

Forgetting to install the PowerShell module – Running the cmdlet without importing the module will produce a “command not found” error.

Which Method Should You Use?

For a one‑off transfer, the CoE Starter Kit app is the simplest if you already have it deployed. If you cannot install the CoE kit, Power Automate offers a quick no‑code path. PowerShell is the best choice for automation scripts, bulk transfers, or when you need to integrate the task into a larger DevOps pipeline.

Whichever route you take, always verify that the new owner can access and edit the app immediately after the transfer. Ask them to open the app in Power Apps Studio and make a trivial change, such as modifying a label, then publish.

References

• Original source article by Matthew Devaney: 3 Simple Ways To Change The Owner Of A Power Apps App
• Microsoft documentation for Power Apps admin cmdlets: Microsoft.PowerApps.Administration.PowerShell
• CoE Starter Kit overview: Microsoft Center of Excellence Starter Kit