Agent flows

What it does

Agent flows are cloud flows that live in Copilot Studio and bill against Copilot Studio capacity rather than Power Automate licensing. They're built and managed on the Workflows page in Copilot Studio, and an agent's orchestrator can call one as a tool at runtime.

Key facts

Agent flows are deterministic. Same trigger, same input, same output — the reasoning sits in the agent that calls them, not in the flow itself.
Every action an agent flow executes consumes Copilot Studio capacity. Once an environment's prepaid capacity is fully consumed, new agent flow runs are blocked until capacity frees up or pay-as-you-go is turned on. In-flight runs finish.
Test runs from the flow designer or the agent's test chat don't consume capacity.
Running a flow from a topic costs one Classic answer plus the flow's actions; running it through generative orchestration costs one Autonomous action plus the flow's actions.
You can convert an existing Power Automate cloud flow to an agent flow from the flow's detail page by changing its plan to Copilot Studio. The flow must be in a solution and in an environment with Copilot Studio capacity. The conversion is one-way and can't be reversed.
Workflows are a separate, newer public preview (as at July 2026) — a redesigned canvas with native AI actions, agent handoffs and node-level testing. You can't convert a Power Automate flow into a workflow, only into an agent flow.
Alongside the action types you'd expect (connectors, control structures, child flows), agent flows expose AI capability actions and human-in-the-loop actions such as approvals.

When to use / skip

Use agent flows when an agent genuinely needs a reliable, repeatable action taken on its behalf — write a record, call a line-of-business API, kick off an approval. The agent decides whether and when; the flow decides how, and you want that part boring and predictable. Skip converting your existing flow estate wholesale. Conversion is one-way, and moving a high-volume flow onto Copilot Studio capacity can change your cost profile in ways nobody modelled. Convert the flows an agent actually calls, and leave the rest on Power Automate billing.

Configuration decisions

Which flows genuinely belong to an agent, and which are background automation that should stay on Power Automate licensing.
Whether the environment runs on prepaid Copilot Studio capacity, pay-as-you-go, or both — and who watches the capacity meter.
Whether flows are exposed at agent level (orchestrator can call them any time) or topic level (scoped to one topic).
How you'll handle capacity exhaustion: block and alert, or fall back to a non-agent path.

Gotchas

Conversion to an agent flow can't be undone. If you're unsure, clone the flow first and convert the clone.
Capacity exhaustion blocks new runs silently from the maker's point of view. The flow looks fine; it just doesn't start. Put a monitor on the Agent flow actions figure in the Power Platform admin center under Licensing > Copilot Studio.
Because test runs are free, everything looks cheap in build. The bill arrives when the agent goes live and the orchestrator starts calling flows on its own initiative.

Consultant notes

Set the expectation early that agent flows are the deterministic half of an agentic solution. Clients often assume "agent flow" means the flow reasons — it doesn't.
Do the capacity maths before the design workshop, not after UAT. Actions-per-run multiplied by expected runs is the number that matters, and it's easy to underestimate once an orchestrator is choosing when to call.
Keep agent flows small and single-purpose. A flow that does one thing is easier for an orchestrator to select correctly and cheaper when it picks wrong.
Flag the Workflows preview to clients as a direction of travel, not something to build production on yet.

Worth another look once Workflows leaves preview, or the next time Copilot Studio capacity pricing shifts