SharePoint + Power Automate: Complete Workflow Automation Guide for 2026

# SharePoint + Power Automate: Complete Workflow Automation Guide for 2026

Power Automate (formerly Microsoft Flow) is the modern replacement for SharePoint Designer workflows and InfoPath forms. For organizations still running classic SharePoint workflows, those retire in 2026 — making this guide essential reading.

This guide covers everything from basic document approval workflows to enterprise-grade automation patterns.

---

Why Power Automate for SharePoint?

Classic SharePoint workflows (Designer 2010/2013 workflows) and InfoPath forms are end-of-life. Microsoft has confirmed these will be deprecated, with SharePoint Designer workflows retiring for SharePoint Online.

Power Automate advantages over classic workflows:

• No-code/low-code interface (no SharePoint Designer required)
• 600+ connectors to external systems (SAP, Salesforce, ServiceNow, etc.)
• Native Teams integration
• Mobile-friendly triggers and approvals
• Full audit trail in Power Automate run history
• AI Builder integration (document processing, form recognition)
• Better error handling and retry logic

---

Power Automate Trigger Types for SharePoint

Understanding triggers is fundamental to SharePoint automation:

SharePoint-Specific Triggers

| Trigger | When It Fires | Common Use |

|---------|--------------|-----------|

| When an item is created | New list item or file upload | Kickoff approval, send notification |

| When an item is modified | Any edit to existing item | Re-trigger approval, log changes |

| When an item is created or modified | Either of the above | General automation trigger |

| When a file is created in a folder | File upload to specific folder | Process incoming documents |

| When a file is classified in a library | Sensitivity label applied | Compliance workflow |

| For a selected item | User manually triggers from list | On-demand workflows |

| For a selected file | User manually triggers from library | On-demand document processing |

Manual Triggers (Instant Flows)

"For a selected item" and "For a selected file" let users trigger workflows from the SharePoint list/library toolbar. These are excellent for:

• On-demand PDF conversion
• Sending a document for signature (DocuSign, Adobe Sign)
• Copying a document to an archive library
• Generating a summary report

---

Document Approval Workflow: Step-by-Step

The most common SharePoint automation: document approval.

Basic Single-Approver Flow

```

Trigger: When an item is created (Documents library)

↓

Action: Start and wait for an approval

• Approval type: Approve/Reject
• Title: "Review: [Document Title]"
• Assigned to: Manager's email
• Details: Document link + submitter info

↓

Condition: If outcome is "Approve"

↓ (Yes)

Action: Update SharePoint item — Status = "Approved"

Action: Send email to submitter — "Your document was approved"

↓ (No)

Action: Update SharePoint item — Status = "Rejected"

Action: Send email to submitter — "Your document was rejected: [Comments]"

```

Multi-Stage Approval with Sequential Approvers

For documents requiring multiple approvals (legal → compliance → executive):

Flow structure:

• First approval: Legal team
• If approved, second approval: Compliance team
• If approved, third approval: Executive (for documents over $100K)
• Final: Update SharePoint status, notify submitter

Key pattern: Use the "Start and wait for an approval" action in sequence, passing the previous approver's comments to the next stage.

Parallel Approval (All Must Approve)

For documents requiring approval from multiple departments simultaneously:

Use "Create an approval" (not "Start and wait") to kick off multiple approvals in parallel, then use a "Wait for multiple approvals" pattern with a scope action.

---

Common SharePoint Automation Patterns

Pattern 1: New Employee Document Distribution

Trigger: When new item created in "New Employees" list

```

• Get employee details (name, department, start date, manager)
• Copy onboarding documents from template library to employee's OneDrive folder
• Share employee handbook with new employee
• Create Teams channel for new employee's team
• Send welcome email with document links
• Create task in Planner for manager's onboarding checklist

```

Pattern 2: Contract Expiration Alerts

Trigger: Recurrence (run daily at 7 AM)

```

• Get all items from Contracts library
• Filter for contracts expiring in 30 days
• For each contract:

a. Get contract owner from SharePoint column

b. Send adaptive card to Teams channel: "Contract [Name] expires [Date]"

c. Send email to contract owner with renewal reminder

d. Create task in Planner for renewal action

```

Pattern 3: Document Version Control Automation

Trigger: When file modified in Contracts library

```

• Check if document is in "Approved" status
• If yes: Set status back to "Draft" (editing an approved doc requires re-approval)
• Send notification to original approver: "[Document] has been modified and needs re-review"
• Log change to audit list: user, timestamp, previous version number

```

Pattern 4: Teams Message to SharePoint Item

Trigger: When a specific keyword appears in Teams channel message

```

• User types "@LogIssue" in Teams channel
• Flow captures message text
• Creates item in SharePoint "Issue Tracker" list
• Extracts: assigned person (@mention), priority (#High), description
• Posts confirmation back to Teams: "Issue #123 logged and assigned to [Person]"

```

Pattern 5: File Metadata Auto-Population

Trigger: When file created in Documents library

```

• Read file name (e.g., "2026-03-15-Contract-AcmeCorp-v2.docx")
• Parse date from filename pattern
• Parse document type from filename pattern
• Update SharePoint item metadata:
• Document Date = 2026-03-15
• Document Type = Contract
• Client = AcmeCorp
• Version = v2

```

---

Migrating from Classic SharePoint Workflows

If you're running SharePoint Designer 2010/2013 workflows, here's how to migrate:

Migration Assessment

• Inventory all workflows: SharePoint Admin Center → Active sites → [Site] → Flows tab shows classic workflows
• Categorize by complexity: Simple notification (easy to recreate), multi-stage approval (moderate), complex calculations (advanced)
• Identify business owners: Who uses this workflow? Who approves it?

Migration Approach by Type

Simple notification workflows → Rebuild directly in Power Automate (1-2 hours)

Multi-stage approval workflows → Use Power Automate approval templates as starting point (1 day)

Complex workflows with calculations/custom code → May require Power Automate + Power Apps for form replacement

InfoPath Form Migration

InfoPath forms are replaced by:

• Power Apps: Full-featured form replacement with custom logic, calculations, cascading dropdowns
• SharePoint List Forms with JSON formatting: Simpler forms using SharePoint's built-in JSON form customization
• Microsoft Forms: For basic data collection (survey-style)

Decision guide:

• Complex forms with business logic → Power Apps
• Simple list forms with basic customization → JSON formatting
• External/public forms → Microsoft Forms

---

Power Automate Performance and Limits

Understanding limits prevents workflows from failing in production:

| Limit | Value | Workaround |

|-------|-------|-----------|

| Runs per day (Office 365) | 6,000 | Power Automate per-user plan |

| Apply to each concurrency | 50 items parallel | Chunk large batches |

| Timeout per action | 30 days | Use do-until with shorter loops |

| SharePoint items retrieved | 5,000 default (max 100,000) | Use pagination + filters |

| API calls per minute | 600 | Batch actions, use delays |

| File size limit | 100MB for most actions | Use SharePoint direct for large files |

---

Error Handling Best Practices

Production workflows need robust error handling:

```

• Configure "Run after" settings on actions to handle failures
• Add a "Configure run after" scope that catches errors
• On error: Send Teams notification to flow owner
• Log error details to SharePoint "Flow Errors" list
• Use "Terminate" action with status "Failed" and error message

```

Always configure:

• Email or Teams alert to flow owner on failure
• Error logging to SharePoint list (timestamp, error message, flow name, run ID)
• "Retry policy" on HTTP and SharePoint actions (3 retries, exponential backoff)

---

Governance for Power Automate

Without governance, Power Automate becomes as unmanageable as classic workflows were.

DLP (Data Loss Prevention) Policies

Configure DLP policies in Power Platform Admin Center to:

• Block flows that connect SharePoint to unauthorized external services
• Require IT approval for flows using sensitive connectors (Salesforce, custom HTTP)
• Allow only approved connectors for business-critical environments

Flow Ownership and Documentation

• Every production flow must have a documented owner
• Flows not triggered in 90 days: auto-disable notification to owner
• Quarterly review of all active flows
• Maintain flow documentation in SharePoint (purpose, trigger, approver, last modified)

---

Power Automate Licensing for SharePoint

| Scenario | License Required |

|---------|----------------|

| Automated flows triggered by SharePoint | Office 365/M365 license |

| Instant flows triggered by user | Office 365/M365 license |

| Flows using premium connectors (SAP, Dynamics, HTTP) | Power Automate per-user plan ($15/user/mo) |

| High-volume flows (>6K runs/day) | Power Automate per-user plan |

| Flows running as service account | Power Automate per-flow plan ($100/flow/mo) |

---

Ready to Automate Your SharePoint Workflows?

Migrating from classic workflows and building new Power Automate automation requires expertise in both SharePoint data architecture and Power Platform capabilities.

[Schedule a workflow automation consultation →](/services/sharepoint-consulting)

Or explore our [SharePoint Copilot Services](/services/sharepoint-copilot) to combine AI with workflow automation.