All insights
POWER PLATFORM AT SCALE

Integration — Connectors, APIs, and Authentication Patterns

Integration design is not about connecting to things — it is about connecting in ways that survive the changes that will inevitably occur. How durable integrations are built on Power Platform.

“Integration design is not about connecting to things — it is about connecting in ways that survive the changes that will inevitably occur.”

Every integration a solution builds is a dependency on something outside itself. Those dependencies outlast their original designers. The connector that seemed reliable at build time changes. The personal credential used for authentication expires. Durable integration design makes three commitments: connections are portable, authentication does not depend on individuals, and breaking changes are detected before they create operational impact.


What Durable Integration Looks Like

Connection references make integrations portable — they abstract the specific connection from the solution logic, so when a solution moves from development to production, the connection updates without requiring a rebuild. Service principals replace personal credentials for unattended flows — so the integration continues when the individual leaves or changes role.


What Power Platform Provides

Connection references are available for every Power Platform connector and are the required pattern for all solutions above Tier 2. Service principal support across Power Automate, Dataverse, and custom connector configurations. The on-premises data gateway for hybrid connectivity. Data Loss Prevention policies govern which connectors can interact — enforcing integration governance at the platform level.


The Enterprise Gap

Integration sprawl — connectors enabled without a governance policy, data moving between systems through unmapped paths — is the second most common FRACTS pattern. The gap is often discovered when a data subject access request arrives and the organisation cannot trace where personal data has flowed.


One Action

Require connection references on every new solution above Tier 1. For existing solutions using personal credentials on unattended flows, schedule a migration to service principals. Start with the most business-critical flows first.


Part 21 of 36 | #PowerPlatformAtScale

The full integration governance model, including the connection reference guide and service principal setup, are in the book.