Power Platform integration patterns: connecting to the systems that matter

A Power Platform solution that only works with Dataverse data is often solving the wrong problem. The data that matters lives in SAP, Salesforce, ServiceNow, legacy databases, and dozens of other systems.

Standard connectors: the easy path

Power Platform has hundreds of standard and premium connectors: SQL Server, Salesforce, ServiceNow, SAP, Dynamics 365, and many more. Where a standard connector exists and covers your use case, use it.

HTTP connector: the flexible middle path

The HTTP connector (premium) calls any REST API. If a system exposes REST and there is no standard connector, the HTTP connector reaches it. Trade-offs: you handle authentication manually, parse response structure yourself, implement retry logic yourself.

Custom connectors: wrapping APIs for reuse

When the HTTP pattern is repeated across multiple flows, a custom connector encapsulates the API definition, authentication, and actions in a reusable form. Any maker in your environment can use it without knowing the underlying API details.

On-premises data gateway

Legacy systems and internal APIs not exposed to the internet need the on-premises data gateway. Cluster multiple gateways for high availability. Monitor gateway health — a failed gateway means failed flows.

SAP integration

SAP connector via gateway works for straightforward read/write. For complex, high-volume, or transactional SAP integration, an integration middleware layer is usually the better architecture.

Map integration requirements against available connector options before making architecture decisions. In most cases the right pattern already exists.