Transfer PowerApp Ownership
Diesen Beitrag auf Deutsch lesen
Two ways to reassign a Power App's owner: the CoE Starter Kit admin app, or Set-AdminPowerAppOwner via PowerShell for scripted bulk transfers.
TL;DR
Reassign a Power App’s owner two ways: run the CoE Starter Kit admin app for a UI-driven bulk transfer, or use Set-AdminPowerAppOwner -AppName <AppId> -EnvironmentName <EnvId> -AppOwner <UserObjectId> per app via PowerShell. Either way you need Power Platform, environment, or Global admin rights — the previous owner keeps read access but loses ownership, with data and connections intact.
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: for a single offboarding, run the CoE Starter Kit app without touching PowerShell; for a whole departed team, use
Set-AdminPowerAppOwnerin a loop instead, since the admin app isn’t built for bulk transfers — a two-tier process, the app for occasional one-off changes and the script kept ready for when a team leaves all at once.
Frequently asked questions
How do I reassign a Power App when its maker has left?
Use either the CoE Starter Kit admin apps, which give a graphical interface for the inventory and for ownership transfers, or the Set-AdminPowerAppOwner cmdlet from the Microsoft.PowerApps.Administration.PowerShell module.
What happens to the previous owner after Set-AdminPowerAppOwner runs?
The previous owner becomes Can View, which keeps read access but removes ownership privileges. Data and connections of the app stay intact during the transfer.
Which permissions do I need to change the owner of an app I do not own?
You need Power Platform admin, environment admin or Global admin credentials. Standard maker permissions are not enough.