The small requests that reach an IT team every week look alike. Copy this from Outlook into Excel, file that attachment in SharePoint, update the order in Dynamics 365 when the customer's email arrives. Microsoft Power Automate, which most Microsoft 365 users already have, turns each one into a flow that someone outside IT can often build, so the request never reaches your engineers and their time goes on the work that needs them. A flow is a trigger, such as an email arriving or a row changing, followed by the actions that should happen next, joined with connectors instead of code.
Whether that lightens your team's load or adds to it shows up a year later. A flow stops when its owner's account is disabled, another needs a premium connector nobody budgeted for, and invoice flows lose their AI Builder credits on 1 November 2026.
Most of that is settled before the hundredth flow, by which licences you buy, which connectors you allow and who owns each flow, and it's worth deciding early which requests should come to your engineers as software instead.
Updated by the TechFabric editors in October 2026.
Three kinds of flow
Cloud flows run in Microsoft's cloud. They're triggered automatically by an event, on a schedule, or instantly from a button, and they cover most business automation.
Desktop flows are robotic process automation (RPA). Microsoft describes them as automating "all repetitive desktop processes" by driving an application's screens, the way a person would, which is how you automate an old system that has no API. Data entry into a legacy ERP is Microsoft's own example.
Agent flows are the newest. They're built in Copilot Studio, can call AI actions such as running a prompt or processing a document, and are billed through Copilot Studio capacity rather than Power Automate licences (agent flows).
What it costs
This is where most rollouts stall, so it's worth being exact. List prices from Microsoft's Power Automate pricing page, annual commitment:
| Licence | Price | What it covers |
|---|---|---|
| Included with Microsoft 365 | No extra cost | Cloud flows with standard connectors only |
| Power Automate Premium | $15 per user per month | Cloud flows with premium connectors, attended desktop flows, process mining with 50 MB of data |
| Power Automate Process | $150 per bot per month | One flow or one unattended desktop bot, for flows that serve the whole organisation |
| Power Automate Hosted Process | $215 per bot per month | Process, plus a Microsoft-hosted virtual machine to run the bot |
Windows users can also run desktop flows locally without a paid licence, but only attended and without cloud orchestration (licence details).
The rule of thumb that falls out of the table is that a flow one person uses for their own work needs that person licensed. A flow that serves everyone, such as invoice intake for the whole finance team, is usually cheaper on a single Process licence than on Premium for every user it touches.
The premium connector trap
The Microsoft 365 licence covers standard connectors only. SharePoint, Outlook and Teams are standard. SQL Server, Salesforce, Dataverse, ServiceNow, Azure Blob Storage, MySQL and PostgreSQL are premium. The way teams find this out is a proof of concept built by someone with a trial licence, approved, and then rolled out to people whose licence can't run it.
Before you build, list every connector the flow touches and check the premium list. There's one useful exception. A Dynamics 365 or Power Apps licence covers premium connectors when the flow runs in the context of that application.
The X connector still exists, but Microsoft's shared app was withdrawn and it now needs your own X application on a paid X enterprise tier (X connector). That's why "works with hundreds of apps" deserves a check against the specific app.
The limits a flow runs into
Microsoft publishes the limits for cloud flows, and four of them shape how you should design one.
- 30 days. A single run can't last longer, and that includes waiting. An approval nobody answers for a month times out.
- 500 actions per flow, nested up to eight levels. Past that, split the work into child flows.
- Apply to each runs one item at a time by default. Turning on concurrency, up to 50 parallel iterations, is often the difference between a flow that finishes in two minutes and one that takes an hour.
- Requests per 24 hours. The official allocation is 40,000 a day for a Premium user and 250,000 for a Process licence, and 6,000 for a Microsoft 365 user (request limits). Microsoft currently applies higher transition limits per flow, but a flow that loops over thousands of rows a day should be designed for the official number. Exceed it and the flow slows down. Stay throttled for 14 days and it's switched off.
One more, which catches seasonal flows. A flow whose trigger hasn't fired for 90 days may be turned off, unless its owner holds a Premium or Process licence.
AI: what changes on 1 November 2026
AI Builder is the part of Power Automate that reads invoices, receipts and ID documents, extracts entities, and classifies text. Its prebuilt models include invoice processing, receipt processing and sentiment analysis (prebuilt models).
How you pay for it is changing. Microsoft stopped selling AI Builder capacity add-ons on 1 November 2025, and on 1 November 2026 the AI Builder credits bundled with premium licences reach end of life. The features stay; they run on Copilot Credits instead, and if a flow has neither kind of credit available, its AI Builder actions are blocked. There's no automatic conversion (AI Builder credits end of life).
If you have invoice or document processing flows in production, check this month which credits they're drawing on and who owns the Copilot Credits budget. A flow that stops reading invoices in November won't announce itself; payables will just notice that nothing arrived.
Separately, Copilot in cloud flows lets you describe a flow in plain English and have the designer build the trigger, actions and connections, then edit or troubleshoot it the same way (Copilot in cloud flows). It only works in the new designer. It's a good way to get a first draft, and the draft still needs someone to check the connector list and the limits above.
A first flow worth building
Supplier invoices that arrive as PDF attachments in a shared mailbox are a good first project, because the work is repetitive, the volume is steady and the result is easy to check:
- Trigger on a new email with an attachment in the accounts payable mailbox.
- Run the attachment through the AI Builder invoice processing model to pull out the supplier, invoice number, date, amount and lines.
- Write the result to a SharePoint list, with the PDF saved to a document library.
- If the amount is above a threshold, start an approval for the budget holder.
- When approved, create the purchase invoice in the ERP, or hand it to whoever does.
Steps 1, 3 and 4 run on standard connectors. Step 2 consumes credits. Step 5 depends on the ERP's connector, which is often premium. That one flow touches every licensing question above, which is exactly why it's worth building first.
Governance before the hundredth flow
Power Automate spreads, which is the point of it. A few settings keep that from turning into a problem.
- Build flows inside solutions. Solution-aware flows can be moved from a test environment to production, and a Process licence can only be assigned to a flow in a solution (solution flows).
- Set data policies. Every connector is classed as Business, Non-Business or Blocked, and a flow can't mix Business and Non-Business connectors. New connectors default to Non-Business (data policies). This is how you stop a flow from copying customer records into a personal Dropbox.
- Use Managed Environments for production, which add sharing limits, deployment pipelines and the solution checker, and are included with standalone Power Automate licences (Managed Environments).
- Give every flow a second owner. A flow owned by one person stops when their account is disabled.
Signs a flow should be software
Power Automate is excellent at the work between people and systems. Notifications, approvals, moving documents and keeping two records in step are what it was built for. It's less suited to high-volume integration, such as syncing tens of thousands of order lines an hour, or to processes that must survive failures halfway through and resume exactly where they stopped. Those belong in code, in Azure Functions or Logic Apps, or in a durable workflow engine like Temporal when a lost step costs money.
A useful test is this. If the flow needs more than 500 actions, runs longer than 30 days, or would be a problem to lose for an afternoon, design it as software.
Where it fits
Power Automate is usually one piece of a larger estate. On AmTab's project, Power Automate keeps the website store, the CRM and the ERP holding the same records, so orders reach Business Central without anyone re-keying them. TechFabric implements Dynamics 365 Business Central and CRM and the automation and AI workflows around them.
Frequently asked questions
Can a flow that runs on a trial licence be moved to production unchanged?
Only if every connector it uses is covered by the licences of the people who will run it. A trial hides the gap, so the check has to happen before anyone approves the proof of concept. Put the connector list next to the licence table and count who needs Premium, or whether one Process licence covers the flow.
Should invoice intake run on Premium licences or one Process licence?
Usually one Process licence at $150 per bot per month, because Premium is $15 for every user the flow touches, so past ten users the Process licence costs less. A Process licence can only be assigned to a flow inside a solution, so build it in one from the start.
How should a flow that loops over thousands of rows a day be designed?
It should be designed against the official daily request allocation, not the higher transition limits Microsoft applies today. Switching on concurrency in Apply to each helps it finish sooner, but it doesn't raise the allocation. If the flow stays throttled for 14 days it's switched off, so a busy flow that outgrows its licence ends up stopped, not just slow.
Why would a seasonal flow stop working?
Microsoft may turn off a flow whose trigger hasn't fired for 90 days, so a year-end or quarterly flow can be off when you need it. The exception is a flow whose owner holds a Premium or Process licence. That makes the owner's licence part of the design for any flow that runs rarely, and a second owner keeps it from stopping if the first account is disabled.