Skip to content

Power Apps

Can Power Apps connect to SharePoint?

By Suresh Girinathuni

Quick answer

Yes. Power Apps connects to SharePoint lists and document libraries through the SharePoint connector for reading, forms, patching, and approvals. It is the fastest path for departmental tools on data teams already own. The ceiling is delegation: filters and sorts on large lists only partly execute server-side, so design with indexed columns, delegable predicates, and modest list sizes — or move the model to Dataverse when relationships, role security, or scale demand it.

Key takeaways

  • SharePoint connector covers lists, libraries, forms, and patch.
  • User permissions carry through; design around delegation limits.
  • Graduate to Dataverse on relational, security, or scale triggers.

Detailed Explanation

Yes. Power Apps connects to SharePoint lists and document libraries through the SharePoint connector for reading, forms, patching, and approvals. It is the fastest path for departmental tools on data teams already own. The ceiling is delegation: filters and sorts on large lists only partly execute server-side, so design with indexed columns, delegable predicates, and modest list sizes — or move the model to Dataverse when relationships, role security, or scale demand it.

How it works

Add SharePoint as a data source, bind galleries and forms to lists, and write with Patch or SubmitForm. The connector runs under the app user’s SharePoint permissions, so list security carries straight through.

Limitations and considerations

Non-delegable queries silently return partial results past the row limit — the most common SharePoint-app bug. Complex relational logic and offline depth also outgrow lists quickly.

This Q&A page is the short-answer layer for “Can Power Apps connect to SharePoint?” Use the related guides below when you need implementation steps, architecture trade-offs, or troubleshooting detail.

For broader context, visit the Power Apps Code Hub. It connects this topic to surrounding Microsoft 365, Power Platform, SharePoint, Copilot Studio, Dataverse, migration, and Dynamics 365 guidance.

When to use it

Build on SharePoint for team tools under a few thousand rows with simple security; choose Dataverse for relational, audited, or enterprise apps.

Practical example

A leave-request app runs on one SharePoint list with a manager-approval flow, then migrates its history to Dataverse when HR adds cross-department reporting and role rules.

Related Questions

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.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.What is Microsoft Dataverse?Microsoft Dataverse is Microsoft’s cloud data platform for storing and managing business data used by Power Platform and Dynamics 365.Can Power Apps connect to SQL Server?Yes — the SQL Server connector reads and writes tables and views, including stored procedures. On-premises databases need an on-premises data gateway; verify premium-licensing implications per scenario.

Related nextM365 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.

Sources