Panda SW

Software, Decoded Daily

Breaking News
Patch Notes

Power Apps Built Outside IT Pose Ownership Risks

By Siti Abdullah November 17, 2026
Power Apps Built Outside IT Pose Ownership Risks - power apps
For instance, a connector set up by a marketing coordinator might quietly copy customer data into a personal OneDrive folder.

In 2021, Gartner predicted that by 2026, around 80% of people using low-code tools would come from outside formal IT departments, up from 60%. That forecast has largely materialized. Power Apps, flows, and connectors are now spread across organizations, often built by individuals outside IT, sometimes running on personal accounts unknown to IT teams.

The App That Disappears When Its Creator Leaves

A common issue arises when an employee builds a Power App that handles a critical process, such as an approval chain. When that person leaves, their account is disabled, and the app stops functioning because its flows rely on their credentials. This disrupts access to SharePoint lists, Dataverse tables, third-party services, and internal APIs.

IT often remains unaware until a team reports the issue. By then, there’s no documentation, no record of the app’s data usage, and sometimes no one left who even knew it existed. In mid-sized organizations, dozens of such apps may be at risk of failing due to a single resignation.

Waste and Risk in Ungoverned Environments

Without clear ownership, inefficiency and risk grow. Multiple departments may build similar apps, like expense approval tools, without knowing others exist. Each app has its own connector configuration, potentially crossing data boundaries that should remain separate.

Read Also: Cancer Society Updates Prostate Screening Guidelines

For instance, a connector set up by a marketing coordinator might quietly copy customer data into a personal OneDrive folder. Such risks often go unnoticed until an audit or a visible failure occurs. The retirement of the Centre of Excellence Starter Kit exacerbates this, as teams now need to rebuild visibility through the admin centre or adopt third-party tools.

Bringing Ungoverned Estates Under Control

Addressing this issue requires auditing every app, flow, and connector across all environments. Decisions must be made on what to keep, rebuild, merge, or decommission. Apps without owners must be assigned, and flows relying on personal credentials must be migrated to service accounts. Connectors violating data policies must be shut down.

The Cost of Ignoring Ownership

Ungoverned Power Apps estates don’t fail suddenly. They degrade gradually, one broken flow at a time, until the accumulated risk becomes unmanageable. Proactive companies assign named owners to every app and flow, document connector functions, and integrate these measures into offboarding processes to prevent apps from going silent when employees leave.

Leave a Reply

Your email address will not be published. Required fields are marked *

© 2026 Panda SW. All rights reserved.