Skip to content

Power Apps

What are connectors in Power Apps?

By Suresh Girinathuni

Quick answer

Connectors let Power Apps read and write outside itself without custom code: standard connectors cover Microsoft 365 sources, premium connectors reach SQL, Dataverse, and third-party systems, and custom connectors wrap any REST API for reuse. The connector choice shapes the app — delegation limits differ per source, connections run under the app user’s permissions, and premium or Dataverse use changes licensing. Pick the data source first; the connector follows.

Key takeaways

  • Standard, premium, and custom connectors cover the data landscape.
  • Delegation and permissions follow the connector, not the app.
  • Prototype the biggest query first; verify licensing early.

Detailed Explanation

Connectors let Power Apps read and write outside itself without custom code: standard connectors cover Microsoft 365 sources, premium connectors reach SQL, Dataverse, and third-party systems, and custom connectors wrap any REST API for reuse. The connector choice shapes the app — delegation limits differ per source, connections run under the app user’s permissions, and premium or Dataverse use changes licensing. Pick the data source first; the connector follows.

How it works

When the app runs, each connector call executes under the signed-in user’s permissions against the source system, subject to that connector’s delegation rules — delegable predicates filter server-side, the rest pulls rows down for local evaluation. Custom connectors package the API definition plus its auth once, so every app reuses the same governed path.

Limitations and considerations

Delegation varies by connector and silently truncates large queries. Premium and on-premises (gateway) connectors add licensing and ownership burdens — verify per scenario.

For broader context, see the Power Apps Code Hub — it collects the guides around this topic.

When to use it

Map every data need to a connector during design, and prototype the largest query first to expose delegation ceilings early.

Practical example

A dashboard app mixes a SharePoint orders list (standard, delegable filters) with a SQL inventory view (premium, gateway) — two connectors, two cost and behavior profiles, decided up front.

Related Questions

What is Power Apps?Power Apps is Microsoft’s low-code app platform with three paths: canvas apps for pixel-perfect task screens, model-driven apps generated from Dataverse data models, and Power Apps Code for pro-code React development.Can Power Apps connect to SharePoint?Yes — SharePoint lists and libraries are first-class Power Apps data sources via the SharePoint connector, ideal for departmental apps. Plan for delegation limits on large lists and graduate to Dataverse when relational needs grow.What is Power Automate?Power Automate is Microsoft’s cloud automation platform for creating workflows between apps, services, data, and APIs.When should I use Dataverse instead of SharePoint for Power Apps?Choose Dataverse when the app needs table relationships, row-level security, auditing, solution ALM, or Dynamics 365 integration. Stay on SharePoint for simple team tools with flat data and list-level permissions.

Related nxtM365 Guides

Power AppsConnect Power Apps Code Apps to Any Data Source — Dataverse, Azure SQL, SharePoint, Copilot Studio & MoreA complete developer guide to connecting Power Apps Code apps to any data source: Dataverse, Azure SQL, SharePoint, Copilot Studio agents, table metadata and REST APIs. See how to add each data source with PAC CLI, what each supports, how to choose the right one, and Microsoft best practices.Power AutomatePower Automate Cloud Flows Explained: Complete Beginner GuideLearn the basics of Power Automate cloud flows, including automated, instant, scheduled, and business process flow examples for beginners.

Sources