How to find and reassign ownerless Power Apps and flows
Diesen Beitrag auf Deutsch lesen
A five-step process to identify ownerless Power Apps and Power Automate flows, assign accountable owners, retire unwanted automation and add ownership checks to offboarding.
TL;DR
Export Power Apps and Power Automate flows from every environment with owners, co-owners, creators and last modified dates. Compare owners with active and disabled Entra ID users, assign two new owners to important items, retire anything nobody will own, and repeat the check during offboarding and on a schedule.
Original by Torsten Mandelkow, on Rencore. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Add a co-owner to every business-critical app or flow so a departure does not leave it without someone who can edit, fix or retire it.
- Admins/CoE: Export assets across environments, compare owners with Entra ID status, prioritise high-impact items, and schedule recurring checks.
- Security/Compliance: Review flows that continue using departed users credentials, because unsupervised connections and permissions create a security finding and outage risk.
- Leadership/Business: Have the heaviest user or leavers manager take ownership, and retire assets nobody will accept responsibility for.
Frequently asked questions
How can I identify ownerless Power Apps across all environments?
Export each environment’s apps with owners and compare them against active and disabled Entra ID users. Flag missing, disabled or deleted owners.
What should happen to a Power Automate flow when its owner leaves?
Assign two new owners who understand the flow and its data. Without reassignment, it may continue using the departed user’s connections and permissions.
How should I retire a Power App nobody will own?
Turn off the flow, set the app aside for 30 days, delete it if nobody objects, and notify people who had access.