Power Automate
Straightforward within the Microsoft ecosystem, but vendor lock-in and licensing complexity make it a bigger commitment than it first appears.
Executive Summary
Power Automate is Microsoft's workflow automation platform, and it's genuinely useful if your business already runs on Microsoft 365. The basics come included with your M365 subscription, so simple automations like "save email attachments to SharePoint" or "post a Teams notification when a form is submitted" cost nothing extra. There are over 1,000 connectors available, covering most major business tools, and the platform is backed by Microsoft's full compliance stack.
The catch is licensing. The moment you need a "premium" connector (which includes things as common as SQL Server or HTTP requests), you're looking at $15 per user per month minimum. Costs escalate further if you need desktop automation (RPA) or AI features. Microsoft began enforcing these licence requirements in April 2025, so the days of running premium connectors without paying are over.
The bigger concern for most businesses is lock-in. Your flows are stored in a proprietary format with no way to export them to competing platforms. If you build 50 automations in Power Automate and later decide to move to Zapier or n8n, you're rebuilding from scratch. For businesses already committed to Microsoft, that's an acceptable trade-off. For everyone else, it's worth thinking carefully about before diving in.
What It Does
Power Automate is a workflow automation platform with three main pillars. Cloud flows handle event-driven or scheduled automations between cloud services, connecting over 1,000 apps and services. Desktop flows provide robotic process automation (RPA) for automating interactions with desktop applications, legacy systems, and web browsers. Process mining analyses operational data to identify bottlenecks and automation opportunities.
The target market is primarily "citizen developers" and business users who need automation without writing code, though IT departments and professional developers also use it for enterprise automation. The sweet spot is organisations already invested in Microsoft 365 or Dynamics 365, where the native integrations with SharePoint, Teams, Outlook, and OneDrive work particularly well.
Green Flags
- Basic automation is included free with Microsoft 365, which is hard to beat for organisations already paying for it.
- Microsoft's compliance credentials (SOC 2, HIPAA, ISO 27001, FedRAMP) are as strong as they come for regulated industries.
- The platform is backed by a $3 trillion company that's actively investing in it. This will be around in 10 years.
- Over 1,000 connectors and a large, active community mean most common integration scenarios are well-trodden ground.
Red Flags
- Heavy vendor lock-in with no portable export format. Moving away means rebuilding every automation from scratch.
- Licensing is genuinely confusing. The premium connector boundary catches businesses off guard, and costs escalate quickly across users and add-ons.
- Power Automate is a documented attack vector within compromised Microsoft 365 environments, with limited admin visibility into flow activity.
- The visual designer becomes painful for complex flows, and there's no built-in testing or native source control.
Licensing & Pricing
Power Automate has a tiered licensing model that starts free but can get expensive quickly. Basic cloud flows using standard connectors (Outlook, SharePoint, Teams) are included with most Microsoft 365 subscriptions at no extra cost. There's also a free developer environment for testing.
Once you need premium connectors, which include things like SQL Server, HTTP requests, Dataverse, or Salesforce, you'll need the Premium plan at roughly $15 per user per month. Desktop automation (RPA) with unattended bots starts at $150 per bot per month, and Microsoft-hosted bots run $215 per month. AI Builder and process mining are additional add-ons.
The standard-to-premium connector divide is the biggest licensing gotcha. A single premium connector in any flow forces the entire flow to require a premium licence. Microsoft began enforcing this in April 2025, so flows that were previously "getting away with it" now need proper licensing.
Vendor Lock-In Assessment
Vendor lock-in is the single biggest strategic concern with Power Automate. Flows are stored in a proprietary format with no export path to competing platforms. If you build your automation layer on Power Automate, you're committing to Microsoft for the long haul.
The lock-in goes deeper than just flow definitions. Custom connectors use C# and OpenAPI 2.0 only. Desktop flows depend on Windows. And the deeper you integrate with Dataverse, SharePoint, and Teams, the harder it becomes to extract yourself.
For organisations already committed to the Microsoft ecosystem, this may be an acceptable trade-off since you're locked into Microsoft anyway. But if you have a multi-cloud strategy or value vendor neutrality, Power Automate creates a significant dependency that's expensive to unwind.
Company Overview
Power Automate launched in November 2016 as "Microsoft Flow" and was rebranded in 2019 when it joined the Power Platform family alongside Power Apps and Power BI. Microsoft acquired Softomotive in 2020 to add desktop automation (RPA) capabilities and Minit in 2022 for process mining.
Microsoft is one of the most stable technology companies in the world, with a market capitalisation around $3 trillion and roughly 228,000 employees. The Power Platform division is a growing priority, crossing $2 billion in annual revenue with 48 million monthly active users. This is not a side project at risk of being sunset. Microsoft is actively investing in AI-powered automation features through Copilot integration, and the platform receives weekly updates.
API
Power Automate has a management API for creating and administering flows programmatically, plus over 1,000 pre-built connectors for third-party services. You can also build custom connectors for any REST API, though these require a premium licence.
Rate limits are generally adequate for normal business automation. The standard premium licence allows 40,000 API requests per user per day, which covers most scenarios. However, every action in a flow counts toward this limit, including simple operations like setting a variable. High-volume batch processing or data migration can hit walls, and connector-specific throttling varies. If you're syncing hundreds of records regularly, your integrator will need to plan for queuing and pacing.
The documentation is extensive on Microsoft Learn, covering common scenarios well. Custom connector documentation focuses on the visual builder rather than code-first approaches, and the management API itself is only semi-documented, with some endpoints officially "unsupported" and subject to change.
Webhooks
Power Automate supports inbound webhooks through the "When an HTTP request is received" trigger, which creates a unique URL endpoint for external systems to call. You can restrict access to anyone, your organisation, or specific users. Custom connectors can also define outbound webhook triggers. Note that Microsoft migrated all trigger URLs from logic.azure.com to api.powerplatform.com in late 2025, so any older integrations using the old domain will need updating.
Data Portability
You can export individual flows as ZIP packages containing JSON definitions, and solution-based flows can be exported and imported across environments and tenants. Microsoft improved the JSON format in 2022 to be more readable and source-control friendly.
However, there's a significant lock-in concern. The export format is proprietary to Power Automate. There are no migration tools to convert flows to Zapier, Make, n8n, or any other platform. If you decide to leave Power Automate, you're rebuilding every automation from scratch. Third-party migration tools are starting to emerge (Quest added Power Platform support in late 2024), but this space is still immature.
Within the Microsoft ecosystem, moving flows between environments is straightforward but still requires manual connection reconfiguration after import. Cross-tenant migrations are particularly painful.
Developer Experience
The visual flow designer is accessible for simple automations but becomes unwieldy for complex logic. The "new designer" UI has been widely criticised by users as buggy, with many still switching back to the classic designer for reliability. There's no text-based editing alternative.
Documentation on Microsoft Learn is comprehensive for common scenarios, with tutorials, learning paths, and a dedicated certification. The weak spots are edge cases, which often require piecing together information from blog posts and community forums.
Testing is a notable gap. There's no built-in unit testing framework for flows, and native Git integration doesn't exist (you can export and commit manually). Version control for desktop flows was only added in November 2025. Professional development practices like TDD, code review, and CI/CD pipelines are harder to implement compared to code-based alternatives. A free developer environment is available for testing, which is genuinely useful.
Compliance & Security
Power Automate inherits Microsoft's enterprise compliance infrastructure, which is as comprehensive as it gets. Data residency is configurable per environment, and administrators can restrict generative AI features from sending data outside their region.
The main security concern is not Microsoft's infrastructure but Power Automate itself as an attack surface. Security researchers have documented how compromised accounts can create flows that silently exfiltrate emails and files, with administrators having limited visibility into what flows are doing. A Vectra study found 71% of monitored accounts showed suspicious Power Automate activity. CVE-2025-29817 also disclosed an information disclosure vulnerability in Power Automate Desktop. Organisations need proper DLP policies and flow auditing in place.
Community & Support
Resources
Interested in Power Automate Integration?
Let's discuss how we can help you get the most out of your software.