Power Automate: What It Actually Does in 2026

Microsoft Power Automate is the automation tool that most enterprise workers already have access to and don't know about. It ships with most Microsoft 365 business plans, it integrates deeply with the Microsoft stack, and it has a desktop automation feature that can click through legacy software like a ghost employee. It is also one of the most confusing products Microsoft sells — which, given Microsoft's portfolio, is saying something.

What It Actually Does

Power Automate does two meaningfully different things, and Microsoft markets them as one product.

The first is cloud flows. These work like any other workflow automation tool: trigger fires, actions execute. New email in Outlook, create a row in SharePoint, post a message in Teams. If your trigger and your actions all live inside the Microsoft ecosystem, the experience is smooth in a way that Zapier and Make can't match. The connectors aren't bolted on — they're native. You get access to fields, metadata, and actions that third-party integrations can't see because they're operating through public APIs while Power Automate is operating through the back door.

This Microsoft-native depth is the actual product. Automatically processing emails in Outlook with specific conditions, routing SharePoint document approvals, syncing data between Excel Online and Dataverse, triggering notifications in Teams based on Planner task changes — if this sentence describes your workday, Power Automate does it better than anything else, because it was built for exactly this and nothing else matters.

The second thing is desktop flows — Microsoft's RPA (robotic process automation) play. Desktop flows record and replay clicks, keystrokes, and screen interactions on Windows applications. This is for automating legacy software that has no API: old ERP systems, internal tools from 2008, government portals that only work in Internet Explorer. Desktop flows watch you do something, record the sequence, and replay it. The technology works — genuinely works — for stable, predictable desktop workflows. It's the closest thing to hiring a human to click the same twelve buttons every morning at 7 AM.

Beyond those two, Power Automate has process mining (analyzing business processes for automation opportunities), AI Builder (adding pre-built AI models to flows — form processing, sentiment analysis, object detection), and what Microsoft calls "process advisor" for identifying bottlenecks. These features exist on paper. In practice, they range from "useful in specific enterprise contexts" to "things Microsoft shows in keynotes."

What The Demo Makes You Think

The Power Automate demo shows a business user building an approval workflow in five minutes. A document arrives in SharePoint, the right manager gets a Teams notification, they click approve, and the document moves to the right folder. Clean. Fast. Already included in your M365 subscription.

Here's what the demo doesn't show.

It doesn't show you connecting to anything outside Microsoft's orbit. The moment you need to connect Power Automate to Slack, Notion, Airtable, or any tool that isn't in the Microsoft stack, you enter a different product. The "premium connectors" — which is Microsoft's way of saying "connectors to non-Microsoft things" — cost extra. Not a little extra. They require either a per-user Power Automate plan ($15/user/month for the base, $40/user/month for premium including RPA [VERIFY: current pricing]) or per-flow licensing that gets expensive fast. That "included with M365" advantage evaporates the moment your workflow touches a non-Microsoft service.

It doesn't show you the connector quality gap. The SharePoint connector is excellent — deep, maintained, covers edge cases. The Salesforce connector is functional. The connector for that industry-specific SaaS tool you use is either basic, broken, or missing entirely. The long tail of Power Automate's connector list is significantly less reliable than the Microsoft-native integrations at the top.

It doesn't show you the builder experience for complex logic. Power Automate's visual builder works for linear flows. The moment you need branching, loops, error handling, or parallel execution, the interface becomes genuinely painful. Conditions nest inside conditions inside conditions, the visual representation becomes an unreadable cascade of collapsed nodes, and you find yourself doing things that would be three lines of code in any scripting language but require fifteen clicks and four modal dialogs in Power Automate. The expression language — a flavor of Azure Logic Apps functions — has its own syntax that is neither standard programming nor intuitive enough to learn by clicking around.

And it doesn't show you the licensing. Power Automate's licensing model is a masterclass in enterprise confusion. There's the version included with M365 (limited connectors, limited runs). There's the per-user plan (all connectors, unlimited runs for that user). There's the per-flow plan (all connectors, unlimited users for that flow, minimum five flows). There's the premium add-on for RPA. There's the unattended RPA add-on, which is different from the attended RPA add-on. If you can explain Microsoft's Power Platform licensing on the first try without checking the documentation, you should be charging consulting fees.

What's Coming

Microsoft is investing heavily in what they call "AI-powered automation" — Copilot integration in Power Automate that lets you describe a workflow in natural language and have it generate the flow. Early versions of this work for simple scenarios and produce confused results for anything complex, which is roughly the state of every AI-generates-automation feature across every platform right now.

The convergence of Power Automate with the broader Power Platform — Power Apps, Power BI, Power Pages, Dataverse — is the strategic play. Microsoft wants organizations to build their entire internal tooling layer on Power Platform, with Power Automate as the connective tissue. If your organization is already deep in this ecosystem, the integration between these products is getting tighter and more capable with every release.

Desktop flows are getting smarter about handling UI changes — the brittleness of "recorded a click at pixel coordinates that moved when someone resized a dialog" is a known problem, and Microsoft is applying AI to make desktop automation more resilient [VERIFY: current state of AI-assisted desktop flow stability]. Whether this reaches the point of genuinely reliable unattended desktop automation — reliable enough that you trust it to run overnight without supervision — remains to be seen.

Should you wait? If you're already in a Microsoft shop, you should be using Power Automate today for Microsoft-to-Microsoft workflows. The tool is mature enough for that use case and has been for years. If you're evaluating it for cross-platform automation or as a general-purpose workflow tool — look elsewhere. That's not what it's good at, and no amount of future development is going to change the fundamental architecture that makes it a Microsoft-first product.

The Verdict

Power Automate earns its place exactly where Microsoft put it: inside the Microsoft ecosystem. If your organization runs on Outlook, Teams, SharePoint, OneDrive, and Excel Online, Power Automate is the default choice, and it's a defensible one. The depth of integration with Microsoft services is unmatched by any competitor, and the fact that it's included in many M365 plans means the marginal cost for basic automation is effectively zero.

Outside the Microsoft ecosystem, it is not competitive. The premium connector pricing, the builder's clunkiness for complex logic, the expression language that feels designed by committee, and the licensing structure that requires a decoder ring — all of these are tolerable when offset by native Microsoft integration. Without that offset, you're paying more for a worse experience than Zapier, Make, or n8n.

The desktop flows / RPA capability is genuinely useful and meaningfully differentiated. If you have legacy Windows applications that need automation and no API exists, Power Automate Desktop is one of the few tools that actually solves this problem at a reasonable price point. This alone justifies evaluation for organizations drowning in manual processes on old software.

The honest summary: Power Automate is the best automation tool for Microsoft shops and an actively bad choice for everyone else. That's not a criticism — it's a product designed for a specific ecosystem, and it serves that ecosystem well. The problem is that Microsoft markets it as a general-purpose automation platform, which it isn't, and the licensing complexity ensures that figuring out what you're actually paying for takes longer than building your first workflow.

This is part of CustomClanker's Automation series — reality checks on every major workflow tool.