Copilot Studio or Microsoft 365 Copilot: Which to Choose?

The question comes up at almost every first meeting: "People talk about Copilot, people talk about Copilot Studio. Is it the same thing?" No. They share a name, they both come from Microsoft, but they do different jobs and they are not paid for in the same way. Here is what you need to decide with your eyes open: when one is enough, when you need the other, and when the two work together.

Microsoft 365 Copilot: an assistant for each person

Microsoft 365 Copilot is the assistant built into Word, Outlook, Teams, Excel and PowerPoint. It summarises a forty-message email thread, drafts a first version of a letter, finds the file whose name you forgot, and produces the recap of a Teams meeting with decisions and action items. It only sees what the signed-in person is allowed to see, nothing more: a folder that is closed to you is closed to your Copilot too.

On the licensing side, it is an add-on per user, in the region of 30 euros per user per month, on top of an existing Microsoft 365 licence (Business Standard, Business Premium, E3 or E5). Prices move and there are offers aimed at smaller businesses: check the current Microsoft price list before you run your numbers. Worth knowing: the free version, Copilot Chat, is available with your work account. It answers from the web and from files you hand it, but it is not wired into your mail, your meetings and your documents the way the paid version is.

Copilot Studio: custom agents connected to your processes

Copilot Studio is a workshop. In it you build agents: specialised assistants that answer from sources you choose (a SharePoint library, a Dataverse table, an internal site) and that can take action, for example run a Power Automate flow or create a request. An agent is published in Teams, on a website, or inside Microsoft 365 Copilot itself.

The billing logic is different: no licence per user, but usage measured in Copilot Credits (formerly "messages"), bought as monthly packs or paid as you go. A pack costs in the region of a few hundred euros a month for typical small-business use; Microsoft's published prices are the reference. In practice, an agent used by 150 employees often costs less than 150 Copilot licences, because you pay for what is actually used.

In both cases your data stays in your Microsoft 365 tenant and is not used to train public models. For a Copilot Studio agent, whether access rights are respected depends on one setting: Microsoft authentication. Switched on, the agent shows each person only what they are allowed to see. Without it, a SharePoint library cannot be used as a knowledge source at all: the agent answers everyone the same way, from public websites or files uploaded to it. It is the first thing we check.

When Microsoft 365 Copilot is enough

If your goal is to save time for people who write, read and sit in many meetings, Microsoft 365 Copilot is enough. A sales director preparing ten proposals a week, an executive assistant sorting two hundred emails a day, a manager walking out of meetings with actions to capture: they gain right away, with no project.

The sensible move: equip five to ten people for three months, ask them to note what they actually use it for, then decide who else really needs it. An unused licence is a cost nobody sees.

When you need Copilot Studio

Copilot Studio becomes necessary when the same question comes from many people, or when the answer has to come from your own data and rules. Three typical situations:

• Repeated questions. Leave, expenses, quality procedures, product warranties: an agent answers from your up-to-date documents, day and night, and hands over to a human when it does not know.
• A process that has to run. "Where is my order?", "create a service request for me": the agent reads your database and triggers the flow, it does not just write text.
• People without a Copilot licence. An agent published in Teams can be used by all your employees, and even by customers on your website, with no individual licence.

It is also the right tool when you want tight control over what the AI is allowed to say: a Copilot Studio agent only answers from the sources you gave it. For a first project, our article on your first AI agent with Copilot Studio walks through choosing the scope.

When the two work together

The most effective setup in a 100-person company often looks like this: around twenty Microsoft 365 Copilot licences for the people who produce a lot of written work, plus two or three Copilot Studio agents open to everyone in Teams. The agents can even appear inside Copilot for those who have it: one entry point, several specialists behind it. A user who already has Microsoft 365 Copilot uses those agents in Teams with no extra credits counted, to be confirmed against Microsoft's current terms.

How we work: a short scoping workshop to lay out the use cases and the real licensing bill, then, if an agent is justified, a fixed-price build, price set at scoping, with tests on your real questions before go-live. The steps are on our method page.