Power Automate settles into a company without anyone deciding on it. It comes with the Microsoft 365 license, so one day a flow files attachments in SharePoint, another sends an approval in Teams. The day the conversation turns to AI agents, someone asks: isn't that already AI automation?
The honest answer is no, and that's no criticism. Power Automate runs a path someone drew. Since Microsoft added AI steps to flows, that path can read a free-text email. But the diagram still decides what happens next. An agent chooses its path based on what it just read.
That difference decides what the license you already pay for can do, and when an agent becomes the better choice.
The short answer, for the busy
Power Automate is Microsoft's automation tool: a trigger, then fixed steps. Microsoft 365 business plans already let you build automated, scheduled and button-triggered flows with standard connectors (Outlook, SharePoint, Teams, approvals), up to 6,000 actions a day per user. Premium connectors such as Salesforce or SQL Server, and custom connectors, require the Power Automate Premium license, listed on Microsoft's Canadian page at CAD $20.40 per user per month, paid yearly. An AI step that reads an email or a document is paid in credits, and from November 1, 2026, licenses bought or renewed no longer include AI Builder credits: you need Copilot Credits instead. Power Automate is enough when the path is known in advance, even if an AI step reads free text. An AI agent becomes the better choice when the next step depends on what was just read.
What your Microsoft 365 license already includes
Microsoft 365 business plans, Business Basic, Standard and Premium among them, include Power Automate rights. They cover automated, scheduled and button-triggered flows, standard connectors and 6,000 actions a day. They exclude premium connectors (except in Dataverse for Teams environments), custom connectors, the gateway to servers you run on-site, and any AI Builder capacity, the Power Platform's AI component.
The standard connector list is more generous than people assume: besides Outlook, SharePoint, Teams, Excel and Forms, it includes approvals, Planner, Gmail and Docusign. For many small businesses, that's enough.
Beyond that, you pay per license. On Microsoft's Canadian page, Power Automate Premium costs CAD $20.40 per user per month, paid yearly. Power Automate Process, a license attached to a flow or a machine rather than a person, costs CAD $203.50 a month, also paid yearly.
Copilot, the assistant you chat with, is a different product, compared with its rivals in our piece on Copilot, ChatGPT and Claude.
Where Power Automate is the right tool
Power Automate's home ground is work you can sketch on a napkin: when this happens, do that, then tell this person. A leave request that goes out for approval and lands back in a calendar. A supplier invoice filed in the right SharePoint folder. A form response that adds a row to a list and pings the team in Teams. A reminder sent every Monday morning.
These flows share one trait: the data always arrives in the same shape, and what happens next involves no interpretation. Here, Power Automate has every advantage: the flow runs inside your Microsoft tenant, under accounts your admin already manages, at no extra cost while the connectors are standard, and someone who has never written a line of code can build one in an afternoon.
If your need looks like this, don't buy anything else. An AI agent would do the same job at a higher price.
First wall: premium connectors
The first obstacle has nothing to do with intelligence. As soon as a flow has to talk to software missing from the standard list, it becomes a premium flow. In Microsoft's catalogue, Salesforce, SQL Server, Mailchimp and even Dataverse, the Power Platform's own database, are premium connectors. Software with no connector at all needs a custom connector, which Microsoft 365 licenses don't include and which assumes the software has an API.
The billing rule follows the identity the flow runs under. An automated or scheduled flow runs as its owner: if it uses a premium connector, only the owner needs a Premium license. A flow started by hand runs as whoever presses the button: every user then needs the license, unless you assign a Process license to the flow itself.
Run the numbers for a premium flow started by hand by 15 employees: 15 Premium licenses at CAD $306 a month, or one Process license at CAD $203.50. It adds up flow by flow, and that's often where the "already included" project stops being included.
Reading free text: the AI step in a flow
For years, a flow could move an email but not understand it. Not anymore: the Run a prompt action sends text to a language model with your instructions and returns the answer, which you can route to a human approval.
By default, the model is GPT-4.1 mini, billed at the basic rate: 0.1 Copilot Credit per 1,000 tokens, and Microsoft prices a credit at US $0.01 on pay-as-you-go. Take 1,000 emails a month at roughly 2,000 tokens each, instructions included: 2 million tokens, 200 credits, about US $2. The AI itself costs next to nothing.
What costs is access. Microsoft 365 licenses include no AI Builder capacity; the Premium license came with 5,000 AI Builder credits a month, but Microsoft is ending that: from November 1, 2026, licenses bought or renewed no longer receive them, and AI steps draw on Copilot Credits. You then need a 25,000-credit pack at CAD $271.40 a month, or pay-as-you-go through an Azure subscription. With neither, the AI step is blocked.
One more thing to settle before you build: Microsoft's documentation contradicts itself. One Microsoft Learn page says an AI Builder action doesn't make a flow premium; another, on AI Builder licensing, says it does. Get a written answer from your reseller.
The real line: who picks the next step
With an AI step, a flow reads. It still doesn't decide. The model fills in a field ("category: invoice"), then the diagram takes over again and follows the branch set up for that value. As long as the possible outputs are known in advance, that works very well: five categories, five branches, a human approval on the doubtful cases.
The flow hits its limit when the next step depends on the content in a way nobody planned. A customer wants to change the delivery address on an order that may already have shipped: someone has to check shipping, then decide what to answer. A request arrives incomplete: someone has to spot what's missing and ask for it. Every exception becomes a new branch, then a branch inside the branch. We've described what becomes of a 40-node no-code flow, and Power Automate doesn't escape it.
An agent works the other way around. You give it a goal, tools and rules, and it chooses which tool to call, in what order, and when to stop and ask a human. The anatomy of an email triage agent shows that loop in practice.
Microsoft sees the same line. Its generative actions let the AI choose actions and their order from a stated intent, but they're in preview, so not recommended for production, and limited to nine Microsoft connectors. For full agents, Microsoft points to Copilot Studio and its credits, which we covered in our piece on Copilot Studio or a custom agent.
The flow that belongs to someone who leaves
One licensing detail causes more trouble than the rest: a flow belongs to a person. When its owner leaves the company, Microsoft downgrades the flow, notifies the co-owners and turns it off after 14 days if nobody acts. The same happens when the owner of a premium flow loses their Premium license.
There's a fix: put flows in a solution so the owner can be changed, or assign them a Process license. Someone still has to know those flows exist, built one at a time by different employees under their own accounts, and read Microsoft's notice before day 14.
Flow, flow with AI, or agent: the grid
A flow alone when the trigger, the fields and the next step are fixed, and everything happens inside Microsoft 365. It's already paid for.
A flow with an AI step when the input is free text but the output fits a list known in advance: classify, extract fields, summarize for someone who approves. Budget for Copilot Credits, a named owner and human review of edge cases.
An agent when the next step depends on what was just read, when the work crosses software outside Microsoft or without a connector, when someone has to write to the customer to get what's missing, or when you want to choose the model and control what data it receives.
You don't have to pick one. The Power Automate flow keeps the approvals and the filing; the agent takes the part of the process that needs judgment.
Where to start
List the flows already running, with their owners. Then take the process that costs you the most hours and ask it this article's question: at each step, who decides the next one?
If the answer is "always the same rule," Power Automate will do the job, and you don't need us. If it's "it depends," write to us with the process, the software involved and the volume. With us, an agent is a fixed monthly subscription with no upfront development cost, quoted after a first call.
Prices, product names and licensing rules were read on Microsoft's official pages on September 24, 2026; Microsoft changes them often. Check your situation with your reseller before buying.
Written byXavier Peich