What Are SharePoint Connectors Connecting PowerApps And Microsoft Flow

SharePoint Connectors: Connecting Power Apps and Power Automate to SharePoint

SharePoint connectors integrate SharePoint Online with Power Apps and Power Automate. They let you build canvas apps that read and write SharePoint lists, and automated workflows that trigger on SharePoint events. This guide covers standard SharePoint connector actions, HTTP requests to the SharePoint REST API, throttling, and governance.

Key facts

• The SharePoint connector is one of the most-used connectors in the Microsoft Power Platform ecosystem.
• Standard connector actions cover: Get items, Get item, Create item, Update item, Delete item, Get files, Create file, and Get file content.
• The "Send an HTTP request to SharePoint" action calls any SharePoint REST API endpoint — enabling operations not available through standard actions.
• SharePoint connector throttling: 600 calls per minute per connection. Use batch operations and retry policies to stay under limit.
• EPC Group builds SharePoint, Power Apps, and Power Automate solutions for Fortune 500 and regulated-industry clients.
• EPC Group holds core Microsoft Solutions Partner designations including Modern Work and Digital & App Innovation.

What SharePoint Connectors Do

SharePoint connectors act as the integration bridge between SharePoint Online and the Microsoft Power Platform. They connect two systems without custom code.

• In Power Apps — Connect a canvas app to SharePoint lists and document libraries. Users can read, create, edit, and delete SharePoint data directly from the app.
• In Power Automate — Trigger flows on SharePoint events. Create automated workflows that respond to new items, file uploads, column changes, and approvals.
• In Logic Apps — Enterprise integration scenarios using the same SharePoint connector actions as Power Automate.

Standard SharePoint Connector Actions

The SharePoint connector provides these standard actions for lists and document libraries.

List Actions

• Get items — Retrieve multiple list items with optional OData filter, select, and order.
• Get item — Retrieve a single list item by ID.
• Create item — Add a new item to a SharePoint list.
• Update item — Modify specific columns of an existing list item.
• Delete item — Remove a list item by ID.
• Get attachments — Retrieve file attachments from a list item.

Document Library Actions

• Get files — List files in a document library folder.
• Get file content — Retrieve a file's binary content for processing or email attachment.
• Create file — Upload a new file to a document library.
• Copy file — Copy a file to another location within SharePoint.
• Get file properties — Retrieve metadata columns (title, status, approver, etc.) from a document library file.

The HTTP Request to SharePoint Action

The "Send an HTTP request to SharePoint" action calls any SharePoint REST API endpoint directly. It unlocks operations not available through standard connector actions.

• Break permission inheritance on a list item or site.
• Manage content types programmatically.
• Execute complex CAML queries for large list retrieval.
• Grant or revoke site collection administrator rights.
• Interact with the SharePoint Search REST API for custom search-driven flows.

Use this action when standard connector actions hit a limitation. It requires understanding SharePoint REST API endpoints and authentication headers.

SharePoint Connector Throttling

SharePoint throttles Power Automate calls at 600 calls per minute per connection. Exceeding this limit causes flows to fail. Use these five techniques to stay under the limit.

1. Use the "Apply to each" concurrency control to limit parallel operations — set concurrency to 1 for sequential processing.
2. Add delay actions between batch operations to space out API calls.
3. Implement retry policies on individual actions with exponential backoff.
4. Use the SharePoint batch API via HTTP requests to combine multiple operations into fewer calls.
5. Schedule resource-intensive flows during off-peak hours (evenings and weekends) to avoid peak tenant throttling.

SharePoint Connector Governance

SharePoint connector governance prevents unauthorized data flows between SharePoint and external services. Configure these controls in the Power Platform admin center.

• DLP policies — Control which connectors can share data with the SharePoint connector. Block personal email, social media, and unapproved cloud storage connectors.
• Environment strategy — Separate production SharePoint environments from developer sandbox environments.
• Connection authentication — Use service principal connections instead of user connections for production flows. Service principals are not affected by user account changes.
• Microsoft Purview sensitivity labels — Sensitivity labels on SharePoint content apply to data flowing through Power Automate. Labels restrict what connectors can do with classified content.

Microsoft Purview and SharePoint Connectors

Microsoft Purview information protection integrates with SharePoint connectors in 2026. Three protection mechanisms apply.

• Sensitivity labels auto-classify SharePoint content based on Microsoft 365 Copilot grounding hints.
• Container labels enforce sharing controls at the site level — preventing labeled sites from connecting to unapproved external connectors.
• Purview content explorer surfaces unauthorized PHI/PII exposure in real time — useful for auditing which flows are accessing sensitive SharePoint content.

Frequently asked questions

What is the SharePoint connector in Power Automate?

The SharePoint connector lets Power Automate flows interact with SharePoint Online lists and document libraries. You can trigger flows on SharePoint events and create, read, update, and delete SharePoint list items and files from flows.

What is the difference between the SharePoint connector and the HTTP action?

The standard SharePoint connector provides pre-built actions for common list and library operations. The "Send an HTTP request to SharePoint" action calls any SharePoint REST API endpoint — useful for complex operations like breaking permission inheritance or executing CAML queries.

How do I handle SharePoint throttling in Power Automate?

Limit parallel "Apply to each" concurrency to 1, add delay actions between operations, implement exponential backoff retry policies, use batch HTTP requests to combine multiple operations, and schedule heavy flows during off-peak hours.

Can the SharePoint connector access SharePoint on-premises?

Yes, with an on-premises data gateway configured. The gateway creates a secure connection between Power Automate in the cloud and your on-premises SharePoint Server. Gateway configuration and licensing are additional requirements.

Does EPC Group build Power Automate flows with SharePoint?

Yes. EPC Group architects and deploys SharePoint-connected Power Automate solutions including approval workflows, document automation, governance flows, and compliance reporting. We implement DLP policies, service principal connections, and Purview sensitivity label integration. Engagements start at $25,000.

Schedule a Power Platform consultation

Talk to an EPC Group Power Platform architect about your SharePoint automation, Power Apps integration, or governance framework. Call (888) 381-9725 or request a 30-minute discovery call.