Automate workflows and tasks across apps and systems
Microsoft Power Automate is Microsoft’s workflow and RPA platform for building cloud flows, automating Windows desktops, and orchestrating approvals across Microsoft 365, Dynamics 365, and hundreds of connectors. It suits organizations standardized on Microsoft 365 that want citizen developers and IT to co‑author governed automations. Pricing spans a free Windows desktop RPA experience, a $15/user Premium plan, $100/flow licensing, and a $150/bot unattended add‑on.
Microsoft Power Automate is Microsoft’s automation and workflow platform for creating cloud flows, desktop (RPA) flows, and business process flows that connect Microsoft 365, Dynamics 365 and hundreds of third-party services. It automates repetitive tasks like approvals, data syncs, and document processing, with built-in connectors and an online flow designer plus Power Automate Desktop for attended and unattended RPA. The key differentiator is tight integration with the Microsoft ecosystem (Teams, SharePoint, Azure) and a large connector library. It serves IT admins, business analysts, and power users across enterprises and SMBs. Pricing includes a limited free experience and per-user or per-flow paid plans for broader automation.
Microsoft Power Automate launched as part of Microsoft’s Power Platform to bring low-code automation to business users and IT teams. Originating from Microsoft’s acquisition and evolution of earlier workflow tools, Power Automate is positioned alongside Power BI and Power Apps as a core automation service that spans cloud connectors, AI-assisted actions, and robotic process automation (RPA). Its core value proposition is enabling organizations to replace manual, repetitive processes with repeatable, auditable workflows that run in the cloud or on desktop endpoints, while leveraging Azure Active Directory identity, Microsoft 365 data, and enterprise governance controls.
Power Automate’s feature set combines cloud flow builders, desktop RPA, and AI capabilities. The cloud flows support 900+ connectors (including SharePoint, Outlook, Dynamics 365, Salesforce, and SQL Server) for triggers/actions and condition logic; Power Automate Desktop provides UI-based RPA with recorded actions, UI element selectors, and credential vaulting for attended or unattended automation; and AI Builder components (form processing, object detection, prediction) add prebuilt AI models for extracting structured data from documents. Additional features include approval flows integrated into Teams and Outlook, built-in error handling and run history, environment and data loss prevention (DLP) policies, and the ability to call Azure Logic Apps or custom connectors for enterprise scenarios.
Pricing is split across free use, per-user and per-flow paid models. There is a free tier available to Microsoft 365 subscribers with limited capabilities and templates; standalone paid plans start with “Per user” at a monthly rate for a single user creating unlimited cloud flows and individual desktop flows, and a “Per flow” plan billed per flow per month for organization-level capacity. Add-ons include unattended RPA add-ons priced per bot and capacity-based licensing for AI Builder.
Microsoft also offers Enterprise Agreement and volume licensing pricing for larger deployments; detailed prices vary by region and may be procured via Microsoft resellers or the Azure portal. Typical users range from a finance analyst automating invoice approvals to an IT admin scheduling data syncs across systems. For example, a Finance Manager might use Power Automate to reduce invoice processing time by automating approvals and SharePoint updates, and a Service Desk Lead can use unattended desktop flows to nightly reconcile tickets across legacy systems.
Large enterprises benefit from governance and DLP, while SMBs use prebuilt templates. Compared to UiPath, Power Automate’s advantage is integrated Microsoft 365 and Azure identity and connectors, though UiPath still often leads in advanced RPA and attended automation tooling.
Three capabilities that set Microsoft Power Automate apart from its nearest competitors.
Which tier and workflow actually fits depends on how you work. Here's the specific recommendation by role.
Consider only if you already live in Microsoft 365; otherwise overhead and licensing complexity may outweigh benefits.
Buy for Microsoft 365-centric teams to standardize approvals, client onboarding, and cross-app data syncs with minimal IT lift.
Buy for large-scale Microsoft estates needing governed automation, SAP/legacy RPA, and DLP with centralized admin.
Current tiers and what you get at each price point. Verified against the vendor's pricing page.
| Plan | Price | What you get | Best for |
|---|---|---|---|
| Power Automate for desktop (Free) | Free | Windows‑only attended RPA; no premium connectors, cloud flows, or unattended bots | Individuals testing attended desktop automation on Windows |
| Power Automate Premium (per user) | $15/user/month | Unlimited flows per user; premium connectors; attended desktop RPA included | Microsoft 365 tenants enabling governed citizen automation |
| Power Automate per flow | $100/flow/month | Organization‑owned license per flow; premium connectors; unlimited users; production use | Enterprise teams licensing a process for unlimited users |
| Unattended RPA add‑on (per bot) | $150/bot/month | Run desktop flows unattended on hosted or physical bots; requires Premium | Automating legacy Windows systems without human supervision |
Scenario: Automate 600 approvals, 200 data sync updates, and 10 monthly report distributions
Microsoft Power Automate: $15/month (1 user on Power Automate Premium) ·
Manual equivalent: $1,680/month (42 hours at $40/hr operations admin) ·
You save: $1,665/month (~99%) after license cost
Caveat: Initial build/governance effort and connector throttling can limit burst throughput; complex RPA or AI scenarios may require extra licenses/credits.
The numbers that matter — context limits, quotas, and what the tool actually supports.
What you actually get — a representative prompt and response.
Copy these into Microsoft Power Automate as-is. Each targets a different high-value workflow.
You are an expert Power Automate flow builder. Create a one-shot cloud flow design that posts a Teams channel message whenever a new file is added to a specified SharePoint folder. Constraints: use the 'When a file is created (properties only)' SharePoint trigger, use the Microsoft Teams connector to post an Adaptive Card or message, include filename, uploader display name, file URL, and simple retry policy and error notification (email to admin). Output format: numbered step-by-step actions ready to implement in Power Automate (trigger name, required fields, action names, key dynamic content mappings). Example message: 'New invoice uploaded: Invoice_123.pdf by John Doe — [Open]({FileLink})'.
You are a practical Power Automate designer. Produce a one-shot scheduled cloud flow that runs a provided SQL query daily, saves results as a CSV to a OneDrive for Business folder, and emails the report link. Constraints: use the 'Recurrence' trigger (daily at specified time), use the Azure SQL or SQL Server connector (include gateway note if on-prem), convert result set to CSV, name file with yyyy-MM-dd prefix, and attach or link in email. Output format: concise step list with connector configurations, sample SQL placeholder, CSV generation method, file naming expression, and example email subject/body. Example filename: invoices_2026-04-01.csv.
You are a Power Automate business analyst. Design a cloud approval flow triggered when an invoice document is added to a SharePoint library with metadata (Amount, Vendor, InvoiceNumber). Constraints: start an Approval action assigning approver(s) from a SharePoint 'Approvers' column, implement conditional escalation when Amount > 5000 to route to Manager; set a 72-hour timeout and auto-remind after 24 hours; on approval update SharePoint status and add a comment in Teams channel; on rejection create a SharePoint exception item. Output format: structured JSON-like list of steps including trigger, conditions, sample expressions (e.g., greater-than), approval configuration, and required metadata fields. Example metadata: Amount: 6200, Vendor: Acme Ltd.
You are a Power Automate integration specialist. Create a scheduled cloud flow that nightly reads a CSV from SFTP, matches rows to Dynamics 365 records by ExternalID, flags and creates 'correction' records for discrepancies beyond configurable thresholds, and writes a reconciliation log to a SharePoint list. Constraints: handle CSV batching (e.g., 500 rows per run), use efficient lookup (Get record by key, not list scan), include retry and dead-letter handling for failures, and summarize results in an emailed report. Output format: stepwise plan with connector actions, batching pattern, sample matching pseudo-code or expressions, and sample SharePoint log schema. Example: CSV column ExternalID, AmountCSV, AmountD365.
You are a senior RPA and Power Automate Desktop architect. Provide a multi-step desktop flow design to process scanned invoice PDFs: use OCR (AI Builder or desktop OCR) to extract header and line-item data, validate totals and VAT rules (example: if parsed total differs >1% from sum(lines) flag exception), open the SAP GUI and enter validated invoices, and on failure send a Teams alert and create an exception item in SharePoint with OCR output and screenshots. Constraints: include selectors for SAP screens, retry logic (3 attempts), timeout, and secure credential retrieval. Output format: detailed pseudo-JSON runbook with actions, selectors, retry policies, OCR field mapping (examples), validation rules, and exception handling steps. Example mapping: InvoiceNumber -> 'Invoice No', Lines -> array of {Qty, UnitPrice, NetAmount}.
You are the Power Platform administrator writing an automated governance playbook. Design a scheduled flow that uses the Power Platform Admin connectors and Microsoft Graph to identify flows and connectors unused for >90 days, compile a CSV report of owner, last run, connectors used and license cost, then automatically disable or remove flows meeting criteria (with owner notification and 14-day soft-disable window). Constraints: include required admin permissions, output audit entries to Azure Log Analytics, post summary to Teams, and provide an opt-out mechanism for business-critical flows. Output format: runbook steps with API calls, required permissions, sample queries/filters, notification templates, soft-disable schedule, and remediation actions. Example threshold: 90 days idle and <5 runs/month historically.
Choose Microsoft Power Automate over Zapier if you run Microsoft 365, need governed data loss prevention and Dataverse integration, and want Windows desktop RPA included for attended scenarios.
Head-to-head comparisons between Microsoft Power Automate and top alternatives:
Real pain points users report — and how to work around each.