It's 8:40 on Monday morning and the head of administration already has 23 unread emails, three purchase requests waiting for her sign-off and an expense spreadsheet someone needs to check before month-end. She's been asked to "see how to automate this with Copilot." She opens the chat, asks for a summary of her inbox, and it works. Then she asks it to approve only the purchases under a certain amount, and that's where she gets stuck.
You can automate tasks with Copilot, but not everything that sounds like automation belongs in the chat. Microsoft has three tools that overlap quite a bit: Copilot in the Microsoft 365 apps, Power Automate, and Copilot Studio agents. Picking the wrong one gets expensive. Sometimes you pay for a license you didn't need, and sometimes you build a complicated flow for something Copilot could have handled in two minutes. This article sorts out what each one does, with concrete cases, and how to decide.
Assisting is not automating
Copilot is an assistant. It works when you ask: summarize a thread, draft a reply, write up meeting notes, analyze a spreadsheet. You decide when, you review the result, and you decide what to do with it.
Power Automate works the other way around. A flow fires on its own when something happens (an email arrives, an item is created in SharePoint, it's Monday at 9:00) and runs the steps you defined, every time, the same way. According to Microsoft Learn, cloud flows can be automated (triggered by an event), instant (started with a button) or scheduled.
A Copilot Studio agent sits in between. It talks like Copilot, but you can give it fixed instructions, its own knowledge sources and actions, including calling a flow.
Put simply: if the task needs human judgment every time, it's a Copilot job. If it repeats the same way and someone does it "because it has to be done," it's a Power Automate job.
Five common tasks and which tool to use
| Task | Tool | Why |
|---|---|---|
| Summarize a long email thread before replying | Copilot in Outlook | It's a one-off and someone has to read the result |
| Write up the notes from a Teams meeting | Copilot in Teams | It needs review before it goes out |
| Route every purchase request for approval and log the answer | Power Automate | It repeats, follows rules and needs a trail |
| Save attachments from certain emails to a SharePoint folder | Power Automate | It's mechanical and needs no judgment |
| Answer internal questions about HR or purchasing policies | Copilot Studio agent | It combines conversation with company-specific knowledge |
Approvals cause the most confusion. Copilot can help you decide whether to approve a purchase, because it summarizes the request and reminds you of the budget. But the full loop (sending the request to the right person, waiting for the answer, logging it and notifying the requester) is a flow's job. Power Automate has an action that starts an approval and waits for the response, and Microsoft publishes a walkthrough exercise for building one.
Copilot can also help build the flow
Power Automate has its own Copilot, and few teams use it. You describe what you need and it suggests the trigger and actions for the flow. Then you adjust it by chatting: "add a notification email at the end," "replace the email with a Teams message."
Microsoft's documentation gives a few tips that hold up well in practice:
- Phrase the request as "when X happens, do Y."
- Name the app you want to use: Outlook, Teams, Forms, SharePoint.
- Check the connections before creating the flow, and test it after you save it.
One caveat: Microsoft says the feature is optimized for English and has limited support for other languages. For teams working in Spanish, writing the description in English often gets better results; you then edit the text users will see by hand.
There's also a newer option: the Workflows agent in Microsoft 365 Copilot. According to Microsoft Support, you describe an automation in natural language and it builds it with Outlook, Teams, SharePoint, Planner and Approvals, including scheduled runs. It still has real limits. It's only available to organizations in the Frontier program and only in English, workflows can't be shared, and non-Microsoft connectors aren't supported. Fine for experimenting. We wouldn't put a critical process on it yet.
When a Copilot Studio agent makes sense
An agent is worth it when the task is conversational but repetitive, and the answer depends on your company's own information. Think of an internal help desk agent that answers using the procedures published in SharePoint and, when someone asks for a new laptop, kicks off the request flow.
That last piece is called an agent flow: a Power Automate flow designed to be called by the agent when needed. The agent understands what the person is asking for, and the flow carries out the steps with fixed rules.
Copilot Studio is billed differently from everything else. Usage is measured in Copilot Credits, bought as prepaid packs or pay-as-you-go through an Azure subscription, according to the licensing documentation. If the user has a Microsoft 365 Copilot license, using agents in Copilot Chat, Teams or SharePoint to answer questions or search organizational data doesn't use up credits. Agent flows the agent calls on that user's behalf don't either, but flows triggered some other way do. Check this before rolling an agent out company-wide.
What your Microsoft 365 already includes
Before buying licenses, look at what you already have. According to the Power Automate licensing FAQ, Microsoft 365 licenses let you build automated, scheduled and button flows with standard connectors such as Outlook, Teams, SharePoint, OneDrive, Forms or Planner. Premium connectors (SQL Server, Dynamics 365, Azure and others), custom connectors and desktop automation require Power Automate Premium or a Process license.
In practice, a good share of office flows (approvals, notifications, filing documents, reminders) can be built without spending more. The trouble starts when the flow needs to read from or write to the ERP or a database. That's when you want to run the numbers first, not after.
For larger projects, we wrote about when Power Platform automation is worth it.
How to decide with your team
One exercise that works: ask each area to list the five repetitive tasks that eat up most of their time, and ask three questions about each one.
- Does someone need to read and adjust the result every time? If so, start with Copilot.
- Does it always run the same way, with clear rules and an identifiable trigger? Then it's a Power Automate flow.
- Do people keep asking the same thing, with the answer sitting in internal documents? That's where an agent fits.
Many tasks mix all three. A purchase request might come in through an agent, move along with an approval flow and end with Copilot helping the manager review the context. Forcing everything into a single tool is exactly how you end up with flows nobody can maintain, or chats nobody checks. If you want to see how this compares with traditional rule-based automation, we cover it in AI vs traditional automation.
Frequently asked questions
Can I automate tasks with Copilot without Power Automate?
For one-off tasks, yes. Summarizing a thread or drafting a reply happens right in Copilot. For tasks that need to run by themselves, when an event happens or on a schedule, you need a flow, either in Power Automate or with the Workflows agent, which is still in the Frontier program.
Do I need to pay for Power Automate separately?
Not for flows using standard connectors like Outlook, Teams or SharePoint, which come with Microsoft 365 licenses. You do for premium connectors, custom connectors or desktop automation.
Do Copilot Studio agents cost extra?
It depends on usage. They're measured in Copilot Credits. For users with a Microsoft 365 Copilot license, several agent interactions in Copilot Chat, Teams and SharePoint don't consume credits, but other actions do.
Start with what you already pay for
Before buying anything new, it's worth checking what your Microsoft 365 license already allows. At Disrupsoft we assess which scenarios gain the most from Copilot, activate and configure it within your Microsoft 365, train teams using their own work and support adoption over time. If you want to sort out what to automate with Copilot and what to leave to a flow, take a look at our Copilot and Microsoft 365 service and let's talk.
