Who Owns the Power Apps Built Outside the IT Team?
Who owns the Power Apps and flows built outside the IT team? Here's why ungoverned low-code estates break down and what firms can do to fix it.
AI summary
Back in 2021, Gartner predicted that by 2026, around 80% of the people using low-code tools would come from outside formal IT departments, up from about 60%. That prediction has more or less come true. Power Apps, flows and connectors are now scattered across organisations, built by whoever had a problem in front of them, often running on personal accounts that IT has never even heard of.
Microsoft has now retired the Centre of Excellence Starter Kit as of May, and Copilot Studio automatically gives every new agent its own Entra identity with no way to opt out at the environment level. Governance has gone from "nice to have" to "you'll regret ignoring this". So what actually falls apart when these apps have no owner, and what will it take to sort that out?
The App That Disappears When Its Creator Leaves
This one happens constantly. A person in operations builds a Power App that handles an approval chain, and for months the thing works brilliantly. Then that person leaves the company, their account gets disabled during offboarding, and the app dies because its flows were tied to their credentials. SharePoint lists, Dataverse tables, third-party services and internal APIs all lose access at once because the connectors were running under a single user's login.
IT won't even know until a team turns up asking why a process they've relied on for months has suddenly gone quiet. By then, there's no documentation explaining how the app was built, no record of what data it touches, and often no one in the team who even knew the app existed. In a mid-sized organisation, you'll find dozens of apps sitting in exactly the same position, each of them one resignation away from going dark.
Duplicate Apps, Shared Connectors and the Data Problem
Without clear ownership, waste and risk grow side by side. Three different departments building their own expense approval app is completely normal where there's no inventory of what already exists, and each of those apps will have its own connector configuration, potentially pulling data across environment boundaries that were never meant to be crossed.
Picture a connector set up by a marketing coordinator that's quietly copying customer data into a personal OneDrive folder. Without a proper record of what's running and who signed off on it, that kind of exposure won't come to light until an audit catches it or something breaks in a visible way. The retirement of the CoE Starter Kit makes this worse, because teams that depended on it for visibility now need to rebuild that capability through the admin centre or bring in a third-party tool to fill the gap.
What It Actually Takes to Bring an Ungoverned Estate Under Control
Getting on top of this means auditing every app, flow and connector running across all environments, then deciding what to keep, what to rebuild, what to merge and what to bin. Apps without an owner either get assigned to a person or get decommissioned. Flows that run on personal credentials get migrated to service accounts, and connectors that breach data policy get shut down. After that, development moves into managed environments with proper ownership records, DLP policies and environment-level controls in place.
For most companies, this is where the internal team runs out of road, because the work demands deep knowledge of the Power Platform estate and the capacity to audit, fix and restructure everything at scale. The fix most of them land on is an experienced Power Platform Consultancy, since specialists who’ve worked across multiple tenants will have already dealt with every version of this mess, and they’ll move through it far quicker than a team encountering it for the first time.
The Cost of Leaving Ownership Unanswered
Ungoverned Power Apps estates don't blow up overnight. They degrade quietly, one broken flow at a time, until the accumulated risk gets too big to wave away. Companies that get ahead of this will assign every app and flow a named owner, document what each connector does, and wire all of that into offboarding so nothing goes silent when a staff member moves on.
With the CoE Starter Kit winding down and agent identities now baked into the platform by default, governance can't be treated as optional any longer. Every month without a proper inventory is another month of apps running on personal credentials with no record of what they touch. Whether the audit happens internally or with outside help, putting it off only makes the job bigger.
Follow the story
About this article
- Length
- 754 words · 4 min read
- Published
- November 17, 2026
- Byline
- Partner
- Source
- Techloy