# What is Power Automate? Uses, licensing and limits

Power Automate is Microsoft's workflow automation service. A flow starts from a trigger, such as a new email, a form response or a schedule, and then runs actions in other systems through connectors. Most Microsoft 365 licenses include cloud flows with standard connectors, while premium connectors, robotic desktop automation and higher daily limits need a paid Power Automate license.

By Shai Goldenberg. Updated: 2026-11-14.

## What Power Automate does

Power Automate is the automation service in the Microsoft Power Platform. You describe a process as a flow: something happens, and a series of steps follows. A form is submitted, so a row is added to a list, an approval is sent to a manager and a message is posted in Teams. Nobody copies data between windows.

Microsoft's documentation describes three types of flows: cloud flows, desktop flows and generative actions, which are still in preview. Most business automation is built from the first two.

From an IT engineer's point of view, the product is easy to start and easy to get wrong. A flow built in an afternoon by one employee can become something the finance team depends on, with no owner, no documentation and a license that does not cover it. The sections below explain the parts, then the licensing and limits that decide whether a design will hold.

## Cloud flows and desktop flows

| | Cloud flow | Desktop flow |
|---|---|---|
| Where it runs | Microsoft's cloud | A Windows machine, yours or Microsoft-hosted |
| How it reaches systems | Connectors and APIs | The application's user interface |
| Typical use | Approvals, notifications, moving data between cloud apps | Legacy desktop software, terminal emulators, apps with no API |
| Main risk | Hitting connector or daily action limits | Breaking when a screen layout changes |

### Cloud flows

A cloud flow is triggered in one of three ways, in Microsoft's terms:

- **Automated.** An event starts it, for example a file is created in a SharePoint library.
- **Instant.** A person starts it with a button, from a mobile device, Teams or a list item.
- **Scheduled.** It runs at a set time or interval.

### Desktop flows

Desktop flows are Microsoft's robotic process automation (RPA). The flow drives an application through its screens using UI elements, images or coordinates. Use them only when there is no connector and no API, because they depend on the screen staying the same.

A desktop flow runs in one of two modes. **Attended** means it runs on a machine while a person is signed in and present. **Unattended** means a bot signs in to a machine, runs the flow and signs out with nobody watching. Unattended runs need a capacity license, described below.

## Connectors: standard, premium and custom

A connector is a packaged wrapper around a system's API. It gives the flow ready-made triggers and actions for that system.

- **Standard connectors** cover Microsoft 365 services such as SharePoint, Outlook, OneDrive and Teams, plus a range of other services.
- **Premium connectors** cover many third-party business systems and require a paid Power Automate license.
- **Custom connectors** are ones you build for a system that has an API but no prebuilt connector.

For data that lives on your own servers, the on-premises data gateway acts as a bridge between the cloud service and the local data source. Microsoft lists the gateway as an entitlement of the paid licenses.

The practical rule: decide which connectors a process needs before you promise anyone a date. One premium connector changes the license requirement for the whole flow.

## Common Power Automate examples

These are typical use cases, not a list of client projects.

- **Document approval.** A file added to a library triggers an approval. The outcome is written back to the file's metadata. This is the most common pairing with [SharePoint consulting](https://goldenroz.com/sharepoint-consulting/) work, because the library structure decides how clean the flow can be.
- **Employee onboarding.** A new row in an HR list creates tasks, sends a welcome email and requests equipment.
- **Form intake.** A Microsoft Forms response becomes a list item and a Teams notification, with routing by category.
- **Scheduled reports.** A flow collects figures every morning and emails a summary.
- **Invoice data entry.** A desktop flow types invoice data into an accounting application that has no API.
- **Alert handling.** A monitoring email is parsed and turned into a ticket in the service desk.

## Power Automate licensing in plain terms

Microsoft licenses Power Automate in two ways: per user and per automation. The table follows Microsoft's "Types of Power Automate licenses" documentation.

| License | Applied to | What it covers |
|---|---|---|
| Microsoft 365 (seeded) | User | Cloud flows with standard connectors only. No premium or custom connectors, no gateway. |
| Power Automate Premium | User | Standard, premium and custom connectors, attended desktop flows on the user's registered machine, process mining. |
| Power Automate Process | A cloud flow or a machine | Lets one flow use premium connectors regardless of who triggers it, or turns a machine into an unattended bot that runs one desktop flow at a time. |
| Power Automate Hosted Process | A Microsoft-hosted machine | Unattended desktop automation on a virtual machine that Microsoft runs, so you manage no hardware. |

Each license also carries a daily action limit. Microsoft's documentation lists 6,000 actions per user per day for Microsoft 365 seeded licenses, 40,000 per user per day for Premium and 250,000 per day for each Process license, and notes that higher limits apply during a transition period.

On price: as of November 2026, Microsoft's Power Automate pricing page lists Premium at $15 per user per month, Process at $150 per bot per month and Hosted Process at $215 per bot per month, each paid yearly. Treat those as list prices to confirm with Microsoft or your licensing provider. We are independent and do not resell Microsoft licenses.

Two licensing traps come up often. First, a flow that works for its author can fail for colleagues if it uses a premium connector and they hold only Microsoft 365 licenses. Second, a Process license can be assigned only to a flow that lives inside a solution, so flows built casually in the default environment have to be repackaged first.

## Limits to design around

These figures come from Microsoft's "Limits of automated, scheduled, and instant flows" page, dated November 2026.

| Limit | Value | What it means in practice |
|---|---|---|
| Actions per flow | 500 | Split long processes into child flows |
| Nesting depth | 8 levels | Deep condition trees need restructuring |
| Run duration | 30 days | An approval nobody answers times out after 30 days |
| Run history retention | 30 days | Export run data if you need a longer audit trail |
| Minimum recurrence | 60 seconds | Not a tool for sub-minute polling |
| Flows with continuous errors | Turned off after 14 days | A failing flow stops itself, and someone has to notice |
| Flows with no trigger activity | May be turned off after 90 days | Applies to flows not covered by a premium or Process license |

The last two rows explain a common support call: a yearly process that silently stopped. Microsoft notifies owners before a flow is suspended, which only helps if the owner still works at the company.

## Governance: what IT should set up first

A Power Platform tenant with no rules fills up with personal flows that hold business processes. Four controls prevent most of the damage.

1. **Environments.** Keep development, test and production apart. Do not run business-critical flows in the default environment where every user can build.
2. **Data policies.** In the Power Platform admin center, administrators can limit access to a whole connector or to specific actions of a connector. Microsoft notes that a policy change usually takes effect within an hour and can take up to 24 hours in large tenants, and that flows violating a policy are suspended.
3. **Ownership.** Give important flows a service account or more than one owner, and package them in solutions. A flow owned by one person breaks when that person's account is disabled.
4. **Monitoring.** Decide who receives failure notifications and who acts on them.

These controls sit inside wider tenant governance, which is the subject of our [Microsoft 365 consulting](https://goldenroz.com/microsoft-365-consulting/) work. Where flows depend on files, read [SharePoint vs OneDrive](https://goldenroz.com/blog/sharepoint-vs-onedrive/) first: a flow attached to a personal OneDrive folder inherits that person's lifecycle.

## Power Automate vs Zapier

Both products connect applications with triggers and actions. The difference is where they sit.

Power Automate is part of Microsoft's platform. Flows sign in with Microsoft Entra ID, are governed in the same admin center as the rest of the tenant, and can use desktop flows and the on-premises gateway to reach systems inside your network. That matters for organizations with legacy software and compliance requirements.

Zapier is an independent automation service that is not tied to one vendor's suite. Teams whose tools are mostly outside Microsoft 365 often find it faster to start with. Compare on three points: which of your systems each product has connectors for, how each is billed at your run volume, and who will administer it.

## When Power Automate is the wrong tool

- High-volume, low-latency integration between systems. Use an integration platform or code.
- Complex business logic with many branches. A flow with hundreds of actions is hard to test and review.
- Processes where the real problem is the process. Automating a bad approval chain makes it fail faster.

## What to do next

List the three manual processes that cost your team the most hours, and for each one write down the systems involved. Check each system against Microsoft's connector reference to see whether it is standard, premium or missing. That tells you the license you need before anything is built.

If you want the design, licensing check, governance setup and build done for you, see our [Power Automate consulting](https://goldenroz.com/power-automate-consulting/) page. Projects start at $25,000 at a fixed price per phase. For ongoing administration of the tenant after the build, [managed IT services](https://goldenroz.com/managed-it-services/) is a monthly retainer quoted after an assessment.

## Questions buyers ask

### Is Power Automate included in Microsoft 365?

Partly. Microsoft's licensing documentation says Microsoft 365 licenses entitle a user to create and run cloud flows with standard connectors, with a lower daily action limit than the paid licenses. Premium connectors, custom connectors, the on-premises data gateway and unattended desktop automation are not included and need a Power Automate Premium or Process license.

### What is the difference between a cloud flow and a desktop flow?

A cloud flow runs in Microsoft's cloud and talks to systems through connectors and APIs. A desktop flow runs on a Windows machine and operates applications through their user interface, the way a person would with a mouse and keyboard. Desktop flows are for applications that have no connector and no API.

### What is a premium connector in Power Automate?

Microsoft sorts connectors into standard and premium. Standard connectors, such as SharePoint, Outlook and Teams, are covered by Microsoft 365 licenses. Premium connectors, which include many third-party business systems, require a paid Power Automate license or a Process license assigned to the flow. Check the connector reference before you design a flow, because one premium step changes the license the whole flow needs.

### How much does Power Automate cost?

As of November 2026, Microsoft's Power Automate pricing page lists Power Automate Premium at $15 per user per month, Power Automate Process at $150 per bot per month and Power Automate Hosted Process at $215 per bot per month, all paid yearly. Prices vary by region and agreement, so confirm on Microsoft's page before budgeting. Goldenroz does not resell licenses.

### Is Power Automate better than Zapier?

It depends on where your systems and your identity live. Power Automate fits organizations that already run Microsoft 365, because flows use the same sign-in, admin center and data policies, and it adds desktop automation for legacy applications. Zapier is an independent service that suits teams whose tools are mostly outside the Microsoft stack.

---
Page: https://goldenroz.com/blog/what-is-power-automate/
Book a free one-hour call: https://calendly.com/daniarozin/daniel-rozin-consultation-1-hour-clone
