Copilot Agents · 6 min read

Copilot Agent Builder vs Copilot Studio: which do you need?

James Wilkinson

By James Wilkinson 5 August 2026 Updated 30 October 2026

The plain-English difference between the agent builder in Copilot Chat and Copilot Studio, and the one question that decides between them.

TL;DR
  • The agent builder in Copilot Chat creates declarative agents in plain English. It answers questions from your content and does not take actions.
  • Copilot Studio is a separately licensed build environment that adds connectors, workflows and actions, so agents can do the next step, not just describe it.
  • The deciding question is one sentence: does the agent only need to answer, or does it need to act?

The agent builder in Copilot Chat creates declarative agents: plain-English instructions plus knowledge sources, good for answering questions from your own content, and part of Copilot Chat, so most Microsoft 365 organisations already have it. Copilot Studio is a separately licensed build environment that adds connectors, workflows and actions, so an agent can raise a ticket, update a record or trigger a Power Automate flow. The deciding question is one sentence: does the agent only need to answer, or does it need to act?

If you are still on “what is an agent at all”, start with the plain-English definition and come back. This article is the fork after that.

What the agent builder is

The agent builder lives inside Copilot Chat. You describe the agent in plain English, point it at knowledge sources such as a SharePoint site and it writes the instructions for you. The result is a declarative agent, which means instructions plus knowledge and no code.

Declarative agents answer questions and draft text, grounded in the content you chose. They cite the document an answer came from. They do not take actions: nothing is filed, sent, updated or triggered. That constraint is a feature for a first agent, because an agent that can only answer is easy to test, easy to trust and quick to fix.

A first declarative agent takes about 15 minutes, which is why it sits in the third stage of the Agent Journey, Agents you talk to, and why it is a good first thing to try after the handover at the end of a Firmwide install.

What Copilot Studio adds

Copilot Studio is the full build environment. Three additions matter.

Connectors. Routes into other systems: Microsoft 365, Dynamics and third-party systems that have a connector or an API. This is how an agent reads from or writes to something beyond its documents.

Workflows. The agent can hand work to Power Automate flows and pick up the result, so a conversation can end with something happening rather than something being described.

Actions. An action is a step the agent carries out rather than just describes: raising the IT ticket, starting the holiday approval, filing the signed contract and updating the client record. Each action runs with agreed review points, so a person still approves anything that matters.

Studio agents need maker-level skills, which sit between everyday user and developer. Most firms hand the work to a build partner through Copilot Studio agents built in a Firmwide install, which is what a Firmwide install includes, and the handover then shows the team how to use and look after the result.

The decision in one question

Does the agent only need to answer, or does it need to act?

Only answer: agent builder. Policy and handbook questions, which-template-is-current questions, tone-of-voice drafting, summaries for a team. If the output is words a person uses, a declarative agent does the job with less to license, less to govern and less to maintain.

Act: Copilot Studio. Intake that raises a ticket, onboarding that starts a flow, filing that updates a record. If the output is a change in a system, you need Studio’s connectors and actions, and you need the testing and ownership that come with them.

There is a third case that looks like an agent decision but is not: a rule-based process that should run silently with no conversation at all. That is Power Automate territory, and the line between the two is drawn in Copilot Studio vs Power Automate.

Where each sits on the journey

On the Agent Journey, the agent builder carries stage three, Agents you talk to: using an agent, building your first one and running team agents that answer questions. Copilot Studio carries stages four and five: agents that run, and the team of agents a business runs across departments. You do not choose one tool for life. Most journeys start in the builder and cross into Studio when the first agent needs to do something, not just say something.

Licensing follows the same line. The agent builder comes with Copilot Chat. Copilot Studio is licensed separately, and the licence question is settled during mapping, before anything is built, alongside the published prices.

Choosing for a real job

The honest test is to name the job first. “An agent for client questions” is not a job. “An agent that answers staff questions about our onboarding process, from the process site, and raises a ticket when the answer is not there” is a job, and its last clause tells you it is a Copilot Studio build. The AI agents for accountancy firms page shows what named jobs look like for one sector, and a free Copilot Readiness Check tells you where Copilot can and cannot see your data, the two jobs to automate first and a rough install price.

Related reading

More on Copilot Agents

Copilot Agents Are Copilot agents secure? Where your data goes The long answer on Copilot agent security: where answers come from, what stays inside the Microsoft 365 service boundary and what your admins control. Copilot Agents What is a Copilot agent? A plain-English definition A plain-English definition of Microsoft Copilot agents: what they are made of, the jobs they do well, where they run and how firms go from one agent to a team. Copilot Agents How to launch your first AI agent You don't need an IT department to launch your first AI agent safely. You need one well-chosen job, tidy sources, a one-page scope, a few simple checks and your Microsoft 365 admin, in that order. Capability map The Agent Journey Five stages from the Copilot licences your firm already has to a team of agents, with a Firmwide install building the skills stage and the agent stages. Automation Strategy Copilot Studio vs Power Automate: when each is the right answer A practical guide to choosing between Copilot Studio agents and Power Automate flows for Microsoft 365 work, with examples for UK professional services firms. The install Firmwide A fixed-price install, typically six to eight weeks: Copilot made safe and useful in your Microsoft 365, an agent and a skills pack for every department, handed over with training. Then Run keeps it working. Industry AI agents for accountancy firms Six accountancy agents for the admin every practice shares: WIP and billing, client checks, meeting notes, records chasing, onboarding and VAT review. Each one waits for one of your team to approve. Next step Pricing Fixed prices: the Readiness Check, the install priced by department, Run and the add-ons. Next step Book a Copilot Readiness Check Free, 30 minutes, online: where Copilot can and cannot see your data, the two jobs to automate first and a rough install price.

Common questions

Questions about Copilot agent builder vs Copilot Studio

Can we start in the agent builder and move to Copilot Studio later?
Yes, and most journeys work exactly that way. Teams prove the job and the knowledge sources with a declarative agent first, then rebuild in Copilot Studio when the agent needs connectors, workflows or actions. The thinking transfers directly. The instructions and knowledge choices made for the first version become the specification for the Studio build.
Is the agent builder enough for a team agent?
Often, yes. An agent that answers questions for a whole team needs proper instructions, agreed knowledge sources, a named owner and testing, but it does not need Copilot Studio unless it must take actions. Plenty of trusted team agents are declarative agents that never leave the agent builder.
What skills does Copilot Studio need?
Maker-level skills, which sit between everyday user and developer. Careful writing, clear process thinking and comfort with connectors and testing. Most firms hand the build to a partner and are shown how to use and look after the result at the handover. It does not require a software developer for most business agents.
Do we need both?
Many organisations end up using both, because they solve different stages of the same journey. The agent builder covers personal and team agents that answer questions. Copilot Studio covers the smaller number of agents that act, such as raising tickets or starting approval flows. Neither replaces the other.