Power Apps troubleshooting
When a Power Apps owner leaves: who can still run, edit, delete and reassign the app
When a Power Apps owner leaves the company, the canvas apps they built usually keep working. Everyone the app was shared with can still open it, and any co-owner can still edit it. What goes missing is the short list of things only the owner can do — delete the app or hand it to someone else — plus whatever the app quietly borrowed from that person’s account. Fixing ownership takes an admin and PowerShell.
That makes an app different from the other two things a departing maker leaves behind. A scheduled flow runs on its owner’s licence and connections, so it tends to stop on its own; that is covered in our guide to what breaks when a Power Automate flow owner leaves. Reports, workspaces and semantic models have their own ownership rules, covered in what happens when a Power BI report owner leaves. This guide is about canvas apps, and every rule below was checked against Microsoft’s documentation on October 30, 2026.
What still works after the app owner leaves?
Almost everything users touch. A canvas app runs under each user’s own identity and, for most connectors, each user’s own connection, so the people it was shared with keep opening it. Co-owners keep editing and sharing. The gaps are the owner-only actions, connections the maker shared implicitly, and data stored in the maker’s own OneDrive.
Microsoft’s guide to sharing a canvas app (opens in new tab) defines the two roles: a user can use the app only, and a co-owner can use, edit and share it but not delete it or change owners. The table sets out what depends on the owner specifically, and what happens to each piece when they go.
| Depends on the owner | What happens after they leave | What to do |
|---|---|---|
| Running the app | Nothing changes for users. Each person signs in as themselves, and an app with premium connectors or components already needs each user’s own Power Apps licence, not the owner’s | No action, unless the app was only ever shared with the person who left |
| Editing and sharing | Co-owners keep both. If there was no co-owner, nobody left in the business can change the app | A remaining co-owner adds another from Share; otherwise an admin runs Set-AdminPowerAppRoleAssignment with the CanEdit role |
| Deleting the app or changing its owner | Owner-only. Co-owners see Delete greyed out and cannot change the owner | An admin deletes it from the admin center, or assigns a new owner with Set-AdminPowerAppOwner |
| Implicitly shared connections | Connections such as SQL Server with SQL or Windows authentication were created by the maker and shared with the app, so the app depends on a connection that belongs to the departed account | Re-create the connection under an account that will stay, point the app at it and republish |
| Files in their OneDrive | An Excel workbook the app reads from the maker’s OneDrive is deleted with that OneDrive once the account is removed and the retention period ends | Move the file to a SharePoint site before the account goes, then repoint the app |
| Flows the app calls | The flow belongs to the maker, and only its creator can customise its parameters | Treat it as an orphaned flow and give it a current owner |
If your situation doesn’t fit neatly into one row, tell us what you’re seeing.
Describe my situation →In a small business the pattern is usually the same. One person built the app in the default environment, shared it with a team or a security group, and never added a co-owner. IT disables the account and removes the licence on the last day, the app keeps working, and the problem only surfaces months later when someone needs a field changed and nobody can open the app in Studio.
Who can change the owner of a Power Apps app?
Only an admin. Power Apps has no change-owner option for makers, and Microsoft’s sharing rules stop co-owners changing the owner. An environment admin or Power Platform admin runs the Set-AdminPowerAppOwner PowerShell cmdlet, or the Set App Owner action in the Power Apps for Admins connector, with the environment ID, app ID and new owner’s object ID.
The admin center will not do it for you. Microsoft’s page on managing Power Apps as an admin (opens in new tab) lists two actions on an app, Share and Delete, and nothing for ownership. The Set-AdminPowerAppOwner reference (opens in new tab) says the cmdlet sets the new owner and changes the current owner to the Can View role, so the departed account is downgraded to an ordinary user rather than removed. The three ways practitioners usually run it:
- PowerShell. Install the Microsoft.PowerApps.Administration.PowerShell module, sign in as an admin, and run Set-AdminPowerAppOwner with -AppName, -EnvironmentName and -AppOwner. All three values are IDs, not display names.
- A one-off admin flow. The Power Apps for Admins connector has a Set App Owner action that takes the same three IDs, which suits an admin who would rather not install PowerShell modules.
- The CoE Starter Kit. Tenants that already run Microsoft’s Center of Excellence Starter Kit can reassign an owner from its app permission tooling instead of a script.
To find what a departed person owned before you start, Get-AdminPowerApp takes an -Owner parameter that accepts an email address or object ID and searches every environment the admin can see. Run it before the account is deleted, while the address still resolves.
Should you add a co-owner or change the owner?
Add a co-owner when the app only needs someone who can maintain it; a remaining co-owner can do this from the Share panel, otherwise an admin can. Change the owner when the app needs one current person accountable for it, including the right to delete it.
For most small-business apps the better pattern is both: a named owner who is still here, plus co-owner rights granted to a small security group for the people who maintain the app. Microsoft’s sharing rules mean anyone who leaves that group loses access through it, so the next departure takes care of itself. One catch: for an app created inside a solution, the sharing panel will not let you make a security group a co-owner, but Set-AdminPowerAppRoleAssignment with -PrincipalType Group and -RoleName CanEdit will.
Is anything different for model-driven apps?
Yes. Microsoft’s own ownership guidance notes that canvas apps, unlike model-driven apps, can be co-owned or have the owner replaced. Access to a model-driven app comes from Dataverse security roles, so a departure rarely locks anyone out; the clean-up is the Dataverse records the person owned, which an admin can reassign.
Those records are the part worth checking. Rows owned by a disabled user stay owned by that user, so views filtered to “my records” and any sharing built on record ownership stop showing them to anyone useful. Reassigning them to a current user or a team is the step that matters, not the app itself.
How do you stop the next departure orphaning an app?
Make it an offboarding step. Before an account is disabled, list the apps the person owns in every environment, give each business app a new owner or a co-owner group, move workbooks the app reads out of their OneDrive into a SharePoint site, and re-create any connection they shared with the app under an account that will stay.
That step is missing from most offboarding checklists, which is why the backlog of ownerless apps and flows grows unnoticed. Our Power Platform governance consulting includes an ownerless-resource review against your tenant inventory and writes the Power Platform step into your offboarding process, scoped as a fixed fee. If you would rather someone else kept the apps maintained, re-pointed connections and handled each departure as it happens, that is what our Power Apps support and maintenance service covers.
FAQ
Questions people ask after an app maker leaves
No. The app stays available to everyone it was shared with, and co-owners can still edit and share it. What can break is anything that depended on the person rather than the app: a connection they created and shared implicitly, a flow they owned, or an Excel file kept in their OneDrive.
Partly. A co-owner can use, edit and share the app, which covers day-to-day maintenance. Microsoft's sharing rules stop a co-owner from deleting the app or changing its owner, so a co-owner cannot make themselves the owner. That last step needs an environment admin or Power Platform admin and PowerShell or the Power Apps for Admins connector.
Microsoft's documentation for Set-AdminPowerAppOwner says the cmdlet sets the new owner and changes the current owner to the Can View role, so the departed account is left as an ordinary user. Users the app was shared with keep their access; the ownership change does not alter who can run it.
No. Unlike a scheduled flow, a canvas app runs under the licence of each person using it, not the owner's. Users of an app with premium connectors or components already need their own Power Apps licence, and the owner leaving changes nothing about that. Removing the owner's licence affects only what that account could do.
An admin. Co-owners see the delete option greyed out, because only the owner can delete a canvas app. An environment admin or Power Platform admin can delete it from the environment's Power Apps list in the Power Platform admin center, or assign a new owner first if someone should keep managing it.
Talk through your orphaned apps with a senior engineer
No hourly meter and no retainer. We scope the work in writing, you approve one fixed price, and the engineer who scoped it does the work.
Free consultation · Written fixed price before any work starts · Reply within one business day
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
- Fixed-fee scope agreed before any work starts
- Senior, US-based Microsoft engineers — no handoffs
- Typical 2–4 week delivery
- 30 days of post-delivery hypercare included
Related reading
Keeping apps, flows and reports owned after people move on
Power Platform Governance Consulting
An ownerless-resource review of your tenant, plus the Power Platform step your offboarding checklist is missing.
When a Flow Owner Leaves
Flows run on their owner’s licence and connections, so they break differently: how to find them and the four fixes.
Power Apps Support & Maintenance
Fixes, connection repairs and ownership hand-overs for the apps your business depends on.