Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 38 ยท Getting Started

Power Automate Flow Types and Licensing Explained

Compare automated, instant, scheduled, desktop and business process flows, and understand seeded versus premium licensing, limits and how to plan costs.

Before you build, you need to pick the right kind of flow and know what it will cost to run. Power Automate has several flow types, and the license decides which connectors you may use and how many runs you get. Prices and limits change, so this lesson explains the model and tells you where to check the current numbers instead of quoting them.

The five flow types

Choose by how it starts

Automated An event fires it
Instant A person presses a button
Scheduled A clock fires it

These three are all cloud flows.

1 / 2
Type Starts when Runs where Typical use
Automated cloud flow An event happens in a service Cloud New email, new row, file created
Instant cloud flow A person clicks a button, or an app calls it Cloud "Send reminder" button in Teams or a mobile app
Scheduled cloud flow A recurrence is reached Cloud Daily report at 7:00
Desktop flow Called by a cloud flow or run by hand Windows PC Entering data in an old desktop program
Business process flow A person opens a record Dataverse app Stages for a sales lead

The first three are all cloud flows: they share one designer and differ only in the trigger. You can change the trigger of an existing flow only by creating a new flow, so choose the type with care.

What makes a flow "premium"

A flow is classed by the connectors, triggers and actions it uses:

  • Standard connectors (SharePoint, Outlook, Teams, OneDrive, Excel Online, Forms, and many more) are covered by the plans that come with Microsoft 365.
  • Premium connectors (HTTP, SQL Server, Dataverse in most cases, many third-party SaaS products) require a Power Automate license.
  • Custom connectors count as premium.

In the designer, premium items show a diamond icon. A flow that contains any premium element can only be run by people who have a premium license, or by a license assigned to the flow itself.

Licensing models in plain words

Names and prices change, so verify them on the official licensing page. The structure stays the same.

  1. Seeded rights. Microsoft 365 plans include the right to build flows with standard connectors, mostly for work that stays inside Microsoft 365.
  2. Per user plans. A person gets a license and can run premium flows, and often desktop flows with attended automation.
  3. Per flow plans. A flow gets its own license so that all users of the flow are covered, which suits processes used by many people.
  4. Process plans / unattended capacity. A desktop flow running without a signed-in person needs an extra capacity license.
  5. Pay as you go. An Azure subscription is linked to an environment and usage is billed by the run.

Every plan also has request limits per 24 hours. Flows that exceed them get slowed (throttled) instead of broken, but heavy automations need higher capacity.

Ask your administrator for the license list before you design anything. A flow built with a premium connector in a team that only has seeded rights will fail when somebody else tries to run it.

Planning cost with a stand-in

The idea of counting "actions per day" is the first step in capacity planning. This stand-in is plain Python with made-up limits, not a real price calculator.

Python Stand-in: will this flow stay within a daily action limit?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Loops multiply the count: a loop with 100 items and three actions inside makes 300 actions, not three. You will meet this again in Approvals and control flow.

Which flow type should I pick?

Use this decision order.

  1. Is the target app a Windows desktop program with no API? Use a desktop flow, called from a cloud flow.
  2. Does an event in a service start the work? Use an automated flow.
  3. Does a person need to decide when it runs? Use an instant flow.
  4. Does it run on a clock? Use a scheduled flow.
  5. Are you steering people through stages of a record? Consider a business process flow.
Python Stand-in: pick a flow type from three questions

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common mistakes

  • Choosing an automated flow when the process is really a schedule, which leaves the flow waiting for an event that never comes.
  • Using a personal connection in a flow that the whole team depends on.
  • Ignoring the diamond icon until the flow stops working for a colleague.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which three types are cloud flows?

    Automated, instant and scheduled flows share the cloud designer and differ only in the trigger.
  2. 2. What does the diamond icon next to a connector mean?

    The diamond marks premium items, which need a premium license.
  3. 3. A flow runs a loop of 50 items with 4 actions inside. Roughly how many actions does one run use?

    Actions inside a loop are counted for every iteration: 50 times 4 is 200.
  4. 4. Which flow type fits a legacy Windows program that has no API?

    Desktop flows use the user interface when there is no API to call.

Summary

  • Cloud flows come in automated, instant and scheduled forms; desktop and business process flows are separate tools.
  • Standard connectors are covered by Microsoft 365; premium and custom connectors need a Power Automate license.
  • Licensing is by user, by flow, by process capacity or pay as you go, and all plans have daily request limits.
  • Loops multiply actions, so count them when you plan capacity.

Next: Your first cloud flow