Is Power Automate included with Microsoft 365?

Partly. Microsoft 365 licenses include limited Power Automate rights: you can create and run cloud flows that use standard connectors, such as Outlook, SharePoint and Teams, within a daily action limit per user. Premium connectors, custom connectors and desktop flows (RPA) need a standalone license such as Power Automate Premium or Power Automate Process.

Do I need a Power Automate license to build agent flows in Copilot Studio?

No. Microsoft states that agent flows are billed through Copilot Studio based on usage, so they consume Copilot Studio capacity instead of requiring a Power Automate license. They can use premium connectors, but they can't currently call desktop flows, and they can't be shared or given co-owners the way cloud flows can.

Can a Copilot Studio agent run a Power Automate flow?

Yes. You add the flow to the agent as a tool. The flow must be in a solution, start with the When an agent calls the flow trigger, and finish with the Respond to the agent action so it can pass results back. The agent then decides when to call it during a conversation or task.

Will Copilot Studio replace Power Automate?

Not on current evidence. Microsoft documents them as complementary: Copilot Studio for agents and AI-driven automation, Power Automate for general automation, including desktop flows that agent flows can't call today. Many solutions use an agent for the conversation and a Power Automate flow for the dependable back-end steps.

Which should a beginner learn first?

Learn Power Automate basics first. Triggers, actions, conditions, connectors and solutions are the same concepts you will use when you give an agent tools in Copilot Studio. Once you can build and troubleshoot a reliable cloud flow, adding an agent on top is a much smaller step.

Copilot Studio vs Power Automate: Picking the Right Tool

Use Power Automate when the job is a fixed process: something happens, a set of steps runs in order, and the same input gives the same result every time. Use Copilot Studio when a person needs to ask, explain or decide something in plain language, or when a step needs judgment. Most real solutions use both: an agent handles the conversation and a flow does the work.

At a glance (as of October 2026)

Question	Power Automate	Copilot Studio
Built for	Rule-based processes	Conversations and AI-driven tasks
Starts with	An event, a button or a schedule	A question, an event or a goal
Desktop automation	Desktop flows (RPA)	Computer use tool
Paid for with	User or bot licenses	Copilot Credits

The real question: conversation or process?

Teams often ask which tool is better. A more useful question is whether the work needs a conversation or a process.

A process has a known shape. A form is submitted, a manager approves, a row is written to a list, an email goes out. Power Automate cloud flows are designed for exactly this, and Microsoft describes three kinds: automated flows triggered by an event, instant flows started with a button, and scheduled flows that run on a timetable.

A conversation is open ended. An employee asks how many vacation days carry over, a customer describes a problem in their own words, or a manager wants a summary of open tickets. Copilot Studio agents are built for this. Microsoft defines an agent as an AI assistant that follows your instructions, draws on the knowledge sources you connect, and uses tools to take action, reasoning through a request to decide the next step.

A quick test: if you can draw the whole job as a flowchart with no "it depends" boxes, start with Power Automate. If the first step is understanding what someone wants, start with Copilot Studio.

What each tool is today

Both products changed a lot over the past year, so check the current definitions before you plan.

Power Automate

According to Microsoft Learn, Power Automate offers three types of flows:

Cloud flows run automatically, instantly or on a schedule, using connectors to Microsoft 365 and many other services.
Desktop flows automate web and desktop apps through robotic process automation (RPA), which is how you reach older systems that have no API.
Generative actions (preview) let you describe the intent of a step and have AI choose the actions.

You can also describe a flow to Copilot in the Power Automate designer and let it draft the steps. That helps beginners, but the result is still a deterministic automation.

Copilot Studio

The Copilot Studio overview now lists three building blocks:

Agents that hold conversations and complete tasks in Teams, Microsoft Copilot, websites and other channels.
Workflows, a newer automation format where each step can combine agents, tools and logic.
Agent flows, the established flow format in Copilot Studio, with an authoring experience similar to Power Automate.

Everything in Copilot Studio runs on a "harness", the runtime that decides when to call the model and which tools to use. Microsoft currently offers a GitHub Copilot harness for reasoning-heavy, multistep work, a Customer Conversation harness for customer service over chat and voice, and a standard harness for rule-based agents and agent flows. Despite the name, the GitHub Copilot harness is a Copilot Studio framework, not the GitHub Copilot coding service.

Where the line blurs: agent flows

Agent flows look like Power Automate flows, which is where most confusion starts. The agent flows FAQ spells out the practical differences:

Agent flows are billed through Copilot Studio based on usage. They don't need a Power Automate license, and they aren't included in Power Automate entitlements.
Agent flows can use premium connectors.
Agent flows can't call desktop flows at this time.
Unlike cloud flows, agent flows can't be copied, shared, given co-owners or given run-only permissions in Copilot Studio.

Flows built in Power Automate stay in Power Automate unless you convert them to agent flows, which moves their billing to Copilot Studio capacity. Treat that as a deliberate decision, not a tidy-up.

A practical rule: if a flow exists mainly to serve one agent, an agent flow keeps everything in one place. If a flow serves many people, needs shared ownership or drives desktop automation, keep it in Power Automate.

Four examples and the right tool for each

1. Invoice approval routing

A PDF lands in a shared mailbox, the amount decides who approves it, and the approved file is filed in SharePoint. Every path is known in advance. Use a Power Automate cloud flow.

2. HR policy questions in Teams

Employees ask about leave, benefits and expenses in their own words, and the answers live in your handbook and policy pages. Use a Copilot Studio agent grounded on those documents, with a named human contact for anything it can't answer.

3. IT help desk intake

The agent asks what is wrong, suggests a knowledge article, and if the issue is real, logs a ticket with the right category and priority. Use both: the agent handles the conversation and calls a flow to create the ticket, so ticket creation stays predictable and auditable.

4. Data entry into an old desktop app

There is no API, so something has to click and type. Power Automate desktop flows do this with recorded, scripted steps. Copilot Studio also has a computer use tool that works from natural-language instructions on a Windows computer and adapts when screens change. Scripted RPA is more predictable; computer use is more flexible. For a high-volume, unchanging screen, scripted RPA is usually the safer start.

How the two work together

The strongest designs split the job: the agent understands and decides, and the flow executes.

An agent calls a flow. Add the flow to the agent as a tool. It must be a solution flow that starts with the When an agent calls the flow trigger and ends with the Respond to the agent action.
A flow calls an agent. In a Power Automate cloud flow, the Microsoft Copilot Studio connector's Execute Agent and wait action sends a message to a published agent and hands its response to later steps, as Microsoft documents.

This split keeps business rules where they belong. A common mistake is writing rules such as "approvals above a set amount go to finance" into an agent's instructions. Put that rule in a flow condition, where it is visible, testable and applied the same way every time. Let the agent collect the request and explain the outcome.

For a deeper look at what agents are and when a business needs one, see our guide to Microsoft Copilot Studio agents, and for a wider view across vendors, what AI agents can do for small businesses.

Licensing questions to settle before you build

Licensing is a common place for projects to stall, so check these points with your Microsoft partner or account team before you commit. Prices below are US list prices shown on Microsoft's pages as of October 2026; your actual price can differ.

What do your Microsoft 365 licenses already include? Microsoft 365 licenses carry limited Power Automate rights: cloud flows with standard connectors and a daily limit of 6,000 actions per user. Premium and custom connectors aren't included.
Do you need premium connectors or desktop flows? Power Automate pricing lists Power Automate Premium at $15.00 per user per month and Power Automate Process at $150.00 per bot per month, both paid yearly. Premium covers attended desktop flows; Process covers unattended ones.
How will you pay for Copilot Studio? Usage is measured in Copilot Credits. You can buy prepaid Copilot Credit packs, pay as you go through an Azure subscription, or use a one-year prepurchase plan. Purchased capacity is enforced monthly and unused credits don't carry over.
Do your users have Microsoft 365 Copilot? For Microsoft 365 Copilot licensed users, some agent usage in Copilot Chat, Teams and SharePoint (classic answers, generative answers and Microsoft Graph grounding) doesn't count against Copilot Studio capacity, according to the Copilot Studio licensing page.
Whose credentials will an autonomous agent use? In the standard harness, event triggers authenticate with the agent maker's credentials, so people using a published agent may reach data through that account. Decide this before you publish, not after.
Who watches consumption? Name an owner for capacity alerts in the Power Platform admin center from day one, so a busy agent doesn't stop mid-month.

Common mistakes to avoid

Building an agent for a process that has no conversation. If nobody needs to talk to it, a flow is simpler, cheaper to reason about and easier to support.
Building a giant flow to fake a conversation. Long chains of conditions trying to parse free text are what agents are for.
Skipping solutions. Put flows and agents in solutions from the start. Agent tools require it, and it makes moving from test to production far easier.
Ignoring ownership. Cloud flows can have co-owners; agent flows can't. Plan who maintains each piece when its builder changes roles.

How CertTulen Academy can help

If your team is new to both tools, start with Microsoft Power Platform Fundamentals (PL-900), which covers Power Automate alongside Power Apps and Power BI. If you already build flows and want to add agents, Create Agents in Microsoft Copilot Studio (PL-7008) is a one-day, hands-on course. CertTulen is a Microsoft Training Services Partner, and our MCT-led classes run live online with labs. For a private cohort built around your own processes, contact us for a batch that suits your time zone.