SharePoint + Power Automate Workflow Guide for 2026

SharePoint + Power Automate: The Enterprise Workflow Guide

Power Automate has fully replaced SharePoint Designer workflows and legacy SharePoint 2013/2010 workflows. In 2026, it is the only supported workflow engine for SharePoint Online. Every organization using SharePoint needs Power Automate competency to handle document approvals, notifications, data synchronization, and process automation.

This guide covers practical workflow patterns drawn from enterprise deployments, with real configurations you can adapt for your environment.

---

Why Power Automate Replaced SharePoint Workflows

SharePoint Designer workflows ran directly on SharePoint servers and were limited to single-site scope, could not call external APIs, had no modern UI, and were deprecated with no further development. Power Automate runs in Azure, connects to 1,000+ services, has a modern visual designer, and receives monthly feature updates.

The migration from legacy workflows to Power Automate is non-negotiable. Microsoft has announced end-of-support timelines for SharePoint 2013 workflows in SharePoint Online, and organizations still running them should treat migration as urgent.

---

Core SharePoint Triggers

Every Power Automate flow starts with a trigger. The SharePoint connector provides these triggers.

When an item is created fires when a new item is added to a list or a new file is uploaded to a library. Use this for new document processing, metadata validation, and notification of new content.

When an item is created or modified fires on any change to an item. This is the most commonly used trigger but can generate high volumes in active libraries. Use trigger conditions to filter.

When a file is created (properties only) fires for new files but returns only metadata, not file content. Useful when you need to route or tag files without downloading them.

For a selected item creates a manual trigger that users invoke from the list or library command bar. Ideal for on-demand actions like submitting for approval or generating a document.

When an item is deleted fires when items are sent to the recycle bin. Use for audit logging or notifications.

Trigger Conditions

Trigger conditions prevent flows from firing unnecessarily. Add conditions directly on the trigger to filter events before the flow runs, which saves flow runs and avoids throttling.

```

Example trigger condition (fire only when Status equals "Submitted"):

@equals(triggerOutputs()?['body/Status/Value'], 'Submitted')

```

---

Essential Workflow Patterns

Pattern 1: Document Approval

The most common SharePoint workflow. A user uploads a document or sets a status to Submitted, the flow routes it to one or more approvers, and the outcome is written back to SharePoint.

Flow structure:

• Trigger: When an item is created or modified (condition: Status = Submitted)
• Action: Start and wait for an approval (type: Approve/Reject)
• Condition: Check approval outcome
• If approved: Update item (Status = Approved, Approved By = approver name, Approved Date = now)
• If rejected: Update item (Status = Rejected), Send email to submitter with comments

Multi-stage approvals: Chain multiple approval actions sequentially. The first approval must complete before the second starts. Use parallel branches for approvals that can happen simultaneously.

Dynamic approvers: Pull approver names from a SharePoint list or from the user profile using the Office 365 Users connector. This avoids hard-coding approver emails in the flow.

Pattern 2: Document Processing Pipeline

Automate what happens after a document is uploaded: extract metadata, classify the document, move it to the correct library, and notify stakeholders.

Flow structure:

• Trigger: When a file is created in the Intake library
• Action: Get file content
• Action: AI Builder - Extract information from document (for invoices, contracts, forms)
• Action: Update file properties with extracted metadata
• Action: Copy file to the appropriate destination library based on document type
• Action: Delete original from Intake library
• Action: Send notification to document owner

Pattern 3: Scheduled Content Review

Automatically identify content that needs review based on age, metadata, or modification date.

Flow structure:

• Trigger: Recurrence (weekly)
• Action: Get items (filter: Modified less than 180 days ago AND ReviewDate less than today)
• Action: Apply to each item
• Sub-action: Send email to content owner requesting review
• Sub-action: Update item (ReviewNotificationSent = Yes, NotificationDate = today)

Pattern 4: Cross-Site Data Synchronization

Keep data consistent between SharePoint lists across different sites. Useful for master data management where a central list feeds departmental lists.

Flow structure:

• Trigger: When an item is created or modified in the master list
• Action: Get items from the target list (filter by unique identifier)
• Condition: Does the item exist in the target list?
• If yes: Update item in target list with master data
• If no: Create item in target list with master data

---

Advanced Techniques

HTTP Actions for SharePoint REST API

When the standard SharePoint connector actions are not sufficient, use the Send an HTTP request to SharePoint action to call the SharePoint REST API directly.

Break role inheritance on an item:

```json

{

"method": "POST",

"uri": "_api/web/lists/getbytitle('Documents')/items(itemId)/breakroleinheritance(copyRoleAssignments=false, clearSubscopes=true)",

"headers": {

"Accept": "application/json;odata=verbose"

}

}

```

Get items with CAML query (for complex filtering):

```json

{

"method": "POST",

"uri": "_api/web/lists/getbytitle('Documents')/getitems",

"headers": {

"Accept": "application/json;odata=verbose",

"Content-Type": "application/json;odata=verbose"

},

"body": {

"query": {

"__metadata": { "type": "SP.CamlQuery" },

"ViewXml": "Active"

}

}

}

```

Expression Functions

Power Automate expressions extend what you can do with data. Essential functions for SharePoint workflows include formatDateTime for date formatting, concat for building strings, if for conditional values, length for counting array items, and first and last for getting array elements.

Example: Calculate business days until a deadline

```

addDays(utcNow(), 5)

```

Example: Extract file extension

```

last(split(triggerOutputs()?['body/{FilenameWithExtension}'], '.'))

```

Error Handling

Production workflows must handle errors gracefully. Use Configure run after settings on actions to run alternative paths when a previous action fails. Implement a Scope action to group related steps, then add a parallel Scope that runs after the first scope fails to handle the error, log it to a SharePoint list, and notify administrators.

Concurrency and Throttling

SharePoint connector actions are subject to API throttling. For flows processing many items, set concurrency control on Apply to each loops to 1 (sequential) to avoid throttling. Add delay actions between batches of SharePoint API calls. Use the Retry policy settings on individual actions to handle transient failures.

---

Governance and Management

Flow Ownership

Every production flow should have at least two owners. Single-owner flows become orphaned when employees leave. Use the Power Platform admin center to manage flow ownership and add co-owners.

Environment Strategy

Use separate Power Platform environments for development, testing, and production. Promote flows through environments using solutions. This prevents untested flows from running against production SharePoint data.

Monitoring

Monitor flow runs through the Power Automate portal and the Power Platform admin center. Set up alerts for flow failures. Create a SharePoint list to log flow executions with status, duration, and error details for long-term tracking.

Naming Conventions

Adopt a consistent naming convention for flows. A recommended pattern is [Site/Scope] - [Action] - [Trigger Type]. For example: HR Benefits - Document Approval - On Upload, or Finance - Invoice Processing - Daily Scheduled.

---

Migration from Legacy Workflows

If you still have SharePoint 2013 workflows running in SharePoint Online, migrate them now. The process involves documenting existing workflow logic and conditions, rebuilding the logic in Power Automate (there is no automated migration tool), testing thoroughly with production-like data, running old and new workflows in parallel for a validation period, and deactivating the legacy workflow once the Power Automate flow is confirmed working.

For complex legacy workflows with dozens of conditions and multiple stages, budget 2-5 hours per workflow for migration and testing.

---

Frequently Asked Questions

How many flow runs are included in my license?

Microsoft 365 E3/E5 licenses include Power Automate for standard connectors with a daily limit of API calls. Premium connectors (like SQL Server or HTTP) require a Power Automate per-user or per-flow license. Check Microsoft's current licensing documentation for exact limits.

Can Power Automate flows run on SharePoint on-premises?

Yes, using the on-premises data gateway. Install the gateway on a server with access to your SharePoint farm and configure the SharePoint connector to use the gateway connection. Performance is slower than SharePoint Online due to the gateway hop.

What happens to running flows when SharePoint throttles requests?

The flow action fails with a 429 (Too Many Requests) error. If retry policies are configured, Power Automate retries the action after the throttling period. Without retry policies, the flow fails and must be resubmitted.

---

For help building enterprise Power Automate workflows for SharePoint, [contact our automation team](/contact) for a workflow assessment. We build production-grade automation solutions for organizations in [regulated industries](/services) where every workflow must meet audit and compliance requirements.