Ownership Is the Hardest Power Platform Governance Problem

Technical ownership, business accountability and connection identity are different responsibilities that inventories often collapse.

1 minute readBy Lucas North

Power Platform exposes an owner field, which encourages organisations to believe ownership is solved. That field often identifies a creator or connection identity. It says nothing about who funds the service, supports users or accepts its risk.

Separate responsibilities. The business owner is accountable for purpose and continuity. The technical owner maintains the solution. The platform team owns shared controls. Runtime connections use identities appropriate to the service, not whichever employee built it first.

Require more than one capable maintainer for supported workloads and test transfer before departure. Connect ownership to an organisational role where possible, while still naming current people.

Most orphan problems begin long before an account is disabled. They begin when creation is mistaken for enduring accountability and nobody notices while the maker is still available to ask.

Written by

Lucas North

I build enterprise software and write about the decisions, constraints and failure modes that rarely fit into a product announcement.

More about me →