Copilot Studio agent flows and Power Automate cloud flows are the same automation engine wearing two different licenses. Both are deterministic, both use the same visual designer and connectors, and both run rule-based steps that produce the same output every time. The real difference is not what they can build — it is who owns the automation, how it is billed, and whether it needs to live inside an AI agent. Agent flows are billed through Copilot Studio in Copilot Credits and run as tools an agent calls; Power Automate cloud flows are licensed per user or per bot and run as standalone business processes.

This guide is written for the IT directors, process owners, and Power Platform architects who open Copilot Studio, see a screen asking whether to build an Agent or a Workflow, and need a defensible answer that holds up in a licensing review. We map the two side by side on cost, governance, RPA support, and portability, then give you a decision framework you can apply this week.

Key takeaways

• They share one engine, not one price: agent flows and Power Automate cloud flows use the same designer and connectors, but agent flows bill in Copilot Credits while cloud flows need a Power Automate license.
• Agent flows are metered, not seated: Microsoft bills agent flow actions at 13 Copilot Credits per 100 actions, so the cost scales with execution volume rather than headcount.
• The “free” path is narrow: agent flow runs are only no-charge when triggered by “When an agent calls the flow” and the user is licensed for Microsoft 365 Copilot — every other trigger consumes credits at the standard rate.
• RPA still belongs to Power Automate: attended desktop automation lives in Power Automate Premium ($15/user/month) and unattended RPA in Power Automate Process ($150/bot/month), not in agent flows.
• Governance differs sharply: agent flows cannot be copied, shared, co-owned, or given run-only permissions, so a standalone, reusable process is often better built as a cloud flow.
• You are not locked in: Copilot Studio can convert a Power Automate cloud flow into an agent flow, so the practical move is to build where the work runs today and migrate when an agent needs it.

The short answer: which one should you use?

Use the trigger and the owner as your decision pivot, not the canvas. If a reasoning AI agent needs to run a reliable, repeatable step mid-conversation, build an agent flow. If the process stands on its own, runs on a schedule or system event, and must be shared and owned across a team, build a Power Automate cloud flow.

• Build an agent flow when: an AI agent triggers the automation, you want consumption-based billing through Copilot Studio, and you do not need to share or co-own the flow.
• Build a Power Automate cloud flow when: the automation is a standalone business process, needs co-owners or run-only users, runs on a non-agent trigger, or has to move through managed ALM pipelines.
• Use Power Automate for RPA when: the work touches desktop or legacy apps with no API — attended or unattended desktop flows are a Power Automate capability.
• Use both together when: an agent handles the ambiguous, judgment-heavy part and calls deterministic flows to execute the steps that must behave identically every time.

What are agent flows, and how do they differ from cloud flows?

Agent flows are automated sequences of a trigger plus one or more actions, built inside Copilot Studio and part of its standard harness experience. They are deterministic — the same input always produces the same output — which is exactly what you want for the repeatable parts of a process that cannot be left to a model's discretion, according to Microsoft's agent flows overview.

Functionally, they are close to identical to Power Automate cloud flows: the same visual designer, the same connectors including premium ones, and the same expressions, loops, and conditions. Microsoft's own FAQ frames the split cleanly — cloud flows require a Power Automate license and are general-purpose automations, while agent flows are billed through Copilot Studio consumption and are optimized to run as tools inside an agent, per the agent flows FAQ. There is one more wrinkle worth knowing: Microsoft now also ships a newer Workflows experience in Copilot Studio, while agent flows are managed in the classic experience, as noted in the agent flows launch announcement.

Do agent flows need a Power Automate license?

No. That is the single biggest reason the two exist. Agent flows are billed through Copilot Studio based on consumption and do not require an individual Power Automate license, which is what lets an organization scale automation across an agent estate without buying a seat for every maker, per Microsoft's FAQ.

The trade-off is control. Because agent flows are scoped to Copilot Studio, they cannot be copied, shared, given co-owners, or assigned run-only permissions the way cloud flows can. For a process that multiple teams need to own, hand off, and maintain independently, that limitation alone can be the reason to keep it in Power Automate.

What do agent flows actually cost?

Agent flow actions are metered in Copilot Credits, and Microsoft's published rate is 13 Copilot Credits per 100 actions. A Copilot Credit lists at roughly $0.01, and capacity is typically bought as a prepaid pack of 25,000 credits for $200 per month or drawn pay-as-you-go through Azure — the same meter we break down in our guide to what AI agents actually cost in Microsoft 365.

The catch that surprises finance teams is the “no charge” fine print. Agent flow runs are only free when they are triggered by the “When an agent calls the flow” trigger and the interacting user is licensed with Microsoft 365 Copilot; any other trigger consumes credits at the standard rate, according to Microsoft's billing rates. In other words, a scheduled or event-driven agent flow is a billable meter, while the same logic wrapped as a Copilot-invoked tool for licensed users may not be.

The tool you pick is not a design choice — it is a licensing decision wearing a designer.

This is where scoping goes wrong quietly. Teams prototype an agent flow because it is fast, ship it on a schedule trigger, and only discover at the first invoice that they have been paying a consumption meter for work a $15 cloud flow would have run under a flat license. Getting the trigger and the license model right before you build is the difference between predictable and surprising spend. BabyBots runs fixed-fee Power Platform automation assessments that map each process to the right build surface and licensing model before a single flow ships.

Agent flows vs. Power Automate cloud flows, compared

Agent flows (Copilot Studio)

• Billing: Copilot Credits, 13 credits per 100 actions; no charge only via the “When an agent calls the flow” trigger for Microsoft 365 Copilot-licensed users.
• Ownership: cannot be copied, shared, co-owned, or given run-only permissions.
• Best for: deterministic steps an AI agent calls at runtime inside Copilot Studio.
• RPA: not the home for desktop automation.

Power Automate cloud flows

• Billing: licensed — seeded standard connectors in Microsoft 365, or Power Automate Premium at $15/user/month for premium connectors and attended RPA.
• Ownership: full sharing, co-owners, run-only users, and managed ALM through solutions.
• Best for: standalone business processes on schedules, events, or approvals.
• RPA: attended in Premium; unattended in Power Automate Process ($150/bot/month) or Hosted Process ($215/bot/month).

What about RPA and desktop automation?

If your process reaches into desktop applications, legacy systems, or anything without a clean API, that is Power Automate's territory, not agent flows'. Attended desktop flows are included in Power Automate Premium at $15 per user per month, while unattended RPA runs on Power Automate Process at $150 per bot per month, and a Microsoft-hosted RPA VM runs on Hosted Process at $215 per bot per month.

The practical rule: agent flows and cloud flows both automate cloud actions well, but robotic process automation over a screen remains a licensed Power Automate capability. Design the agent to call a Power Automate flow for the RPA leg rather than trying to force desktop automation into an agent flow.

Can you convert a Power Automate flow into an agent flow?

Yes — Copilot Studio supports converting an existing Power Automate cloud flow into an agent flow, which is what makes the “build where it runs today, migrate when an agent needs it” strategy safe rather than a rework gamble, per Microsoft's agent flows overview. Because the underlying logic and connectors are shared, most of the investment carries over.

This portability is why the tool decision does not have to be permanent. Start a standalone process in Power Automate where you get ownership, sharing, and flat licensing; if an AI agent later needs that logic as a callable tool, convert it. Just re-check the billing implications after conversion, since the meter and trigger rules change.

Frequently asked questions

Are agent flows and Power Automate cloud flows really the same thing?

Under the hood they are nearly identical — same designer, same connectors, same expressions and control logic. The differences are licensing and context: agent flows bill through Copilot Studio in Copilot Credits and are meant to be called by an agent, while cloud flows require a Power Automate license and run as standalone processes with full sharing and ownership.

How much does an agent flow cost to run?

Agent flow actions are billed at 13 Copilot Credits per 100 actions, with credits listing at about $0.01 each, typically purchased as a 25,000-credit pack for $200 per month or pay-as-you-go. Runs are only free when triggered by “When an agent calls the flow” for a Microsoft 365 Copilot-licensed user; other triggers consume credits at the standard rate.

Do I need Power Automate to build agent flows?

No. Agent flows are created and billed inside Copilot Studio and do not require an individual Power Automate license. However, they cannot be copied, shared, co-owned, or given run-only permissions, so processes that need those capabilities are better built as Power Automate cloud flows.

Can agent flows do RPA or desktop automation?

Desktop and screen automation remain a Power Automate capability. Attended desktop flows are included in Power Automate Premium, and unattended RPA runs on Power Automate Process or Hosted Process. Have your agent call a Power Automate flow for the RPA step rather than building it as an agent flow.

Should I use agent flows or Power Automate for a scheduled business process?

For a standalone scheduled process with no AI agent in the loop, Power Automate cloud flows are usually the better fit: you get flat licensing, sharing, co-ownership, and managed ALM. A scheduled agent flow is a billable Copilot Credits meter because it is not using the no-charge agent-invoked trigger.

What is the difference between agent flows and Copilot Studio Workflows?

Agent flows are the deterministic automations managed in Copilot Studio's classic experience. Workflows are Microsoft's newer automation experience in Copilot Studio built around agentic, event-driven scenarios. Both aim to combine reliable execution with AI, but if you are standardizing today, confirm which experience your tenant exposes before you commit a pattern.

Where this is heading

Microsoft is deliberately pulling the automation canvas into Copilot Studio, positioning agents and workflows as complementary building blocks rather than an either-or choice — agents for reasoning and ambiguity, deterministic flows for the steps that must run the same way every time. Expect the naming and surfaces to keep shifting as Workflows matures alongside agent flows. The stable decision principle underneath the churn will not change: choose the build surface by owner, trigger, and billing model, and keep RPA in Power Automate.

Build it on the right surface the first time

The costliest automation mistakes in Copilot Studio are not broken flows — they are correctly built flows on the wrong licensing surface, discovered at the first invoice. Book a BabyBots automation build-surface assessment, and we will map your candidate processes to agent flows, Power Automate cloud flows, or RPA — with the credit-and-license math attached — in a single working session, so you scope for predictable spend before anyone starts building.

Sources

• Microsoft Learn — Agent flows overview (Copilot Studio)
• Microsoft Learn — Agent flows in Microsoft Copilot Studio FAQ
• Microsoft Learn — Billing rates and management (Copilot Studio)
• Microsoft Copilot Blog — Automate business processes with agents plus workflows
• Microsoft Copilot Blog — Introducing agent flows
• Microsoft — Power Automate pricing