Use a cloud flow when a trigger or schedule starts the automation, an agent flow when an agent calls it, and a desktop flow for apps with no API. Cloud flows use Power Automate licenses, while agent flows and Copilot Studio workflows bill Copilot Credits per action. Have someone review every flow Copilot drafts before it goes live.
When you need this
- Teams build agents in Copilot Studio that need to act in business systems.
- A process depends on a legacy Windows or web application with no API.
- Makers want Copilot or another AI to build flows for them.
Evaluation criteria
Cloud flow or agent flow
Does an agent call this automation, or a trigger or schedule?
Look forCloud flows run on Power Automate licenses. Agent flows live in Copilot Studio, run deterministic steps, and bill 13 Copilot Credits per 100 actions. A solution-aware cloud flow can convert to an agent flow, but the change cannot be reversed.
Which Copilot Studio experience
Which Copilot Studio experience are makers using?
Look forCopilot Studio offers two build experiences, which Microsoft calls harnesses. The standard one calls these automations agent flows. The GitHub Copilot experience calls them workflows and adds AI nodes, agent handoffs, and node-level testing. Microsoft has offered it for production since June 2026, and it has been generally available since August 2026. Both bill Copilot Studio capacity per action.
Who triggers the agent flow
Are agent flows triggered by Microsoft 365 Copilot licensed users?
Look forActions carry no charge when a Microsoft 365 Copilot licensed user calls the flow through an agent with the When an agent calls the flow trigger. Every other trigger bills credits. When prepaid capacity runs out, new runs stop until someone reallocates capacity or links pay-as-you-go billing.
Long-running steps
Can the agent wait for the flow to finish?
Look forUse asynchronous responses, which Microsoft added in May 2026, for agent flows that run past the two-minute limit. Time long jobs in testing before an agent depends on the flow.
Desktop flows for applications without APIs
Does the application have an API or a connector?
Look forIf it has neither, a desktop flow drives its screens. Attended runs need Premium. Unattended runs need Process, and each bot runs one flow at a time. Hosted Process, at US$215 per bot per month, runs bots on Microsoft-hosted machines that scale in groups. Developers migrating from UiPath report weaker structured error handling.
Desktop actions under data policies
Which desktop actions can a flow use?
Look forClassify desktop flow modules as business, non-business, or blocked, because policies skip unclassified modules. Test classification changes first, since they suspend desktop flows that break the policy.
Copilot for building flows
Will makers build flows with Copilot?
Look forReview every Copilot change in the designer. Microsoft's FAQ says Copilot supports only some connectors and cannot fix flow errors. Of the public accounts GILD read, 9 describe Copilot failing to build or explain flows. One MVP scored a generated flow 4.5 out of 10. Several builders use Claude, GitHub Copilot, or ChatGPT for flow definitions instead.
Questions to ask vendors
- Which agents call flows, and are the people triggering them Copilot-licensed?
- Which high-volume flows should stay cloud flows on Process licenses?
- Which desktop flows depend on screens that change when an application updates?
- Who reviews flows that Copilot or another AI drafted before they go live?
Red flags
- High-volume cloud flows converted to agent flows without pricing the per-action credits.
- Agent flows with nobody watching Copilot Credit use before enforcement blocks new runs.
- A single unattended bot serving a process that needs parallel runs.
- Flows drafted by Copilot published without a designer review.
Products in this piece
Sources
- Official documentation
- 13
- Public source
- 6
- Microsoft Learn: Agent flows overview (Copilot Studio)
- Microsoft Learn: Agent flows FAQ (Copilot Studio)
- Microsoft Learn: Workflows overview, GitHub Copilot harness (Copilot Studio)
- Microsoft Learn: Copilot Studio billing rates and management
- Microsoft Learn: What's new in Copilot Studio
- Microsoft Copilot Blog: What's new in Copilot Studio, August 2026: GitHub Copilot harness (Sep 2, 2026)
- Microsoft Learn: Introduction to desktop flows
- Microsoft Learn: Hosted RPA overview
- Microsoft Learn: Data loss prevention for desktop flows
- Microsoft Learn: Types of Power Automate licenses
- Microsoft Learn: Copilot in Power Automate
- Microsoft Learn: FAQ for Copilot in cloud flows
- Microsoft Learn: Generative actions overview
- David Wyatt: Code Reviewing Copilot in Power Automate (Jul 28, 2025)
- Reddit r/PowerAutomate: Why is Copilot so bad at creating flows? (May 21, 2026)
- Reddit r/MicrosoftFlow: Claude Code vs GitHub Copilot when working in Power Automate (Apr 7, 2026)
- Reddit r/rpa: three years migrating UiPath bots to Power Automate for desktop (Sep 21, 2025)
- Reddit r/rpa: a company leaving Power Automate for desktop after two years (Oct 6, 2025)
- Hacker News comment on deploying Copilot Studio and the Power Platform in GCC (Dec 3, 2025)