Skip to main content

Decision brief

Power Automate Review: What to Settle Before Flows Run Your Processes

Default to Power Automate in Microsoft 365, where standard-connector flows come with the license. Premium connectors, Word templates, and unattended bots each add a paid license.

Reading time
3 min read
Sources
21 cited
In this piece
Power Automate−6 Mixed

GILD verdict

Choose Power Automate when your processes already run in Microsoft 365, or when you need desktop RPA for less than a dedicated RPA vendor charges.

Before more teams depend on it, decide the license each flow runs under and move critical flows into solutions owned by a service principal.

Power Automate

Workflow Automation by Microsoft

−6 Mixed
Product page

Fit and limits

Who it fits

  • Processes run in Outlook, Teams, SharePoint, Excel, and Dataverse: Microsoft 365 licenses already include cloud flows with standard connectors, at up to 6,000 Power Platform requests per user a day.
  • Legacy Windows or web applications have no API. Desktop flows drive them through the user interface, attended under Premium at US$15 per user per month and unattended under Process at US$150 per bot per month, paid yearly.
  • IT wants automation governed in the tenant it already runs: data policies classify connectors and desktop flow actions, and Managed Environments add sharing limits, pipelines, and usage insights.
  • Business staff will build their own flows. Of 88 public accounts, 8 describe staff without programming backgrounds building and running flows, and one of them now does it full time.

Where it falls short

  • Anything beyond standard connectors needs a paid license: Premium per maker, Process per flow, or US$0.60 per premium run on pay-as-you-go. A service account shared by many users breaches Microsoft's multiplexing rules.
  • Flows belong to the person who built them, and only solution-aware flows can change owner in place. A premium flow owned by a service principal needs a Process license, a flow group, or a designated licensed user.
  • Run history is kept for 30 days, a flow that fails for 14 days is turned off, and Copilot is on by default and turns off only at the tenant level.
  • AI costs moved to Copilot Credits. New customers have bought Copilot Credits for AI Builder since November 1, 2025, and licenses bought or renewed from November 1, 2026 carry no seeded AI Builder credits.
  • Generative actions, which let AI choose steps inside a cloud flow, are still a preview, and Microsoft says previews are not meant for production use.
  • Microsoft now offers a second automation builder. Copilot Studio Workflows, generally available since August 2026, bill Copilot Studio capacity per action and stop new runs once prepaid capacity runs out.

Implementation reality

  1. Inventory flows and owners first

    Use Inventory and Usage in the Power Platform admin center, which replace the CoE Starter Kit that Microsoft no longer maintains, to list flows, their owners, and the connectors they use. Flag business-critical flows owned by individuals.

  2. Set environments and data policies

    Keep experiments in the default environment and production flows in managed environments. Group connectors in data policies before teams build, because a policy change suspends apps and flows that break it, desktop flows included.

  3. Move critical flows into solutions

    Only solution-aware flows can change owner in place, use connection references, and move through pipelines. Make a service principal the owner of mission-critical flows, and license them with Process or a flow group of up to 25 flows sharing 250,000 actions a day.

  4. License each flow on purpose

    Standard connectors run on Microsoft 365 rights. Give makers who build premium or desktop flows Premium, and give each core process a Process license. Use pay-as-you-go for occasional premium runs, which break even with Process at 250 runs a month (calculated). Standard-tier AI Builder prompts cost 1.5 Copilot Credits per 1,000 tokens, and admins see each charge on the AI Builder Activity page.

What to measure in your pilot

  • Count new automations built as Copilot Studio Workflows against new cloud flows each quarter, and shift budget toward Copilot Credits once Workflows reach half of new builds.
  • Before your first renewal without seeded AI Builder credits, log a month of AI Builder use on the AI Builder Activity page and size the Copilot Credit purchase from it.
  • Test generative actions in a sandbox environment only, and log how often a person corrects the steps the AI chose before letting one touch a production flow.

Sources

Official documentation
21
  1. Microsoft Power Automate pricingOfficial documentationmicrosoft.com
  2. Microsoft Learn: Types of Power Automate licensesOfficial documentationlearn.microsoft.com
  3. Microsoft Learn: Power Automate licensing FAQOfficial documentationlearn.microsoft.com
  4. Microsoft Learn: Requests limits and allocationsOfficial documentationlearn.microsoft.com
  5. Microsoft Learn: Pay-as-you-go metersOfficial documentationlearn.microsoft.com
  6. Microsoft Learn: Limits of automated, scheduled, and instant flowsOfficial documentationlearn.microsoft.com
  7. Microsoft Learn: Introduction to desktop flowsOfficial documentationlearn.microsoft.com
  8. Microsoft Learn: Data policiesOfficial documentationlearn.microsoft.com
  9. Microsoft Learn: Data loss prevention for desktop flowsOfficial documentationlearn.microsoft.com
  10. Microsoft Learn: Managed Environments overviewOfficial documentationlearn.microsoft.com
  11. Microsoft Learn: Change the owner of a cloud flowOfficial documentationlearn.microsoft.com
  12. Microsoft Learn: Support for service principal owned flowsOfficial documentationlearn.microsoft.com
  13. Microsoft Learn: CoE Starter Kit transition to the Power Platform admin centerOfficial documentationlearn.microsoft.com
  14. Microsoft Learn: Copilot in Power AutomateOfficial documentationlearn.microsoft.com
  15. Microsoft Learn: Generative actions overviewOfficial documentationlearn.microsoft.com
  16. Microsoft Learn: AI Builder licensing overviewOfficial documentationlearn.microsoft.com
  17. Microsoft Learn: Workflows overview, GitHub Copilot harness (Copilot Studio)Official documentationlearn.microsoft.com
  18. Microsoft Learn: What's new in Copilot StudioOfficial documentationlearn.microsoft.com
  19. Microsoft Copilot Blog: What's new in Copilot Studio, August 2026: GitHub Copilot harness (Sep 2, 2026)Official documentationmicrosoft.com
  20. Microsoft Learn: AI Builder licensing and Copilot CreditsOfficial documentationlearn.microsoft.com
  21. Microsoft Learn: Use generative actions in cloud flows (preview)Official documentationlearn.microsoft.com

Keep reading

  1. Buyer guidePower Automate Rollout PlaybookThe environments, ownership rules, review practice, and licensing to settle before business teams build flows that others depend on.
  2. Buyer guidePower Automate Licensing & Capacity ChecklistPick the license each flow runs under, from Microsoft 365 rights, Premium, Process, flow groups, and pay-as-you-go, and check it against request limits.
  3. Buyer guidePower Automate Admin, Data & Copilot Controls ChecklistData policies, Managed Environments, ownership, run history, regions, and the Copilot settings to review before flows touch sensitive data.
Read the research