Copilot Studio vs Agent Builder: Which One to Use, and What Each Can Actually Ship

Use Agent Builder if the agent is for you or a small team and answers questions from content you already have. Use Copilot Studio if the agent is for a department, the whole company, or customers, or if it needs to do anything beyond answering. That is Microsoft's own decision rule, and it holds up. Audience decides the tool, not features.

There is a second difference nobody puts in a comparison table, and it is expensive to discover late: an agent built in Agent Builder can never be listed in the Microsoft Commercial Marketplace. Neither can a declarative agent built in Copilot Studio. If selling to other companies is the plan, only two build paths get you there, and one of them is not on this page.

The short comparison

Microsoft publishes its own feature comparison between the two. Here is what it says, condensed, with the licensing and distribution reality added.

What is Agent Builder in Microsoft 365 Copilot?

Agent Builder is the no-code authoring experience built into the Microsoft 365 Copilot app. You describe what you want in plain language, point it at some content, and you have an agent. Microsoft frames these agents as reusable templates that package repeatable prompts and content connections to retrieve insights from Microsoft Graph.

The examples Microsoft gives are deliberately modest: a project FAQ bot answering common questions from project documentation, a product documentation assistant that helps employees find information in internal manuals or wikis, an onboarding agent that answers new team members' questions from an internal knowledge base. Notice what those have in common. They all retrieve and explain. None of them do anything.

Two governance principles are worth knowing because they answer the security question before it gets asked. The first is no new privileges: agents respect existing Microsoft 365 permissions, so if a user cannot open a SharePoint site, a Teams channel or an Outlook mailbox, the agent will not surface content from it for them. The second is that standard audit logs, activity reports and DLP and retention policies apply, because the agents live inside Microsoft 365 rather than beside it.

What is Copilot Studio?

Copilot Studio is a separate product on the Power Platform, aimed at makers and developers rather than information workers. Microsoft describes agents built there as "more customizable and feature-rich" than agents created with Agent Builder, which is accurate but undersells the gap. The real difference is that Copilot Studio agents can take actions.

Microsoft's own examples show the shift: a customer support agent that creates support tickets and escalates issues to a human, an IT help desk triage agent that routes employee requests to the right team, a sales assistant that retrieves CRM data, makes notes and starts an approval workflow. Every one of those writes to a system somewhere.

That capability comes with real operational weight. Copilot Studio brings application lifecycle management across development, test and production environments, connector governance so admins control which systems agents can reach, environment-level DLP and role-based access, and telemetry. It also brings a second admin surface: Copilot Studio is managed from the Power Platform admin center, not the Microsoft 365 admin center. If your Microsoft 365 admins and your Power Platform admins are different people, you have just added a stakeholder. Deciding early which systems an agent may call, and with what permissions, is the part teams underestimate, and it is the same problem that enforcing tool and data access for AI agents exists to solve at runtime rather than at design time.

Do you need a license for Agent Builder or Copilot Studio?

Both are included with a Microsoft 365 Copilot add-on license for authenticated users, which lists at $30 per user per month. Without that license you have two options, and one of them is free.

The free web-grounded tier is more useful than it sounds for evaluation. You can prove the authoring experience works for your people before anybody signs a purchase order. What it cannot do is touch a single document you own, which is usually the whole point, so treat it as a demo rather than a deployment. The credit meter is where Copilot Studio budgets go wrong, and the rates vary by what the agent does rather than by headcount. Our breakdown of Copilot Studio pricing covers the full rate card, and how Copilot Credits meter explains why two teams of the same size get very different invoices.

Which one should you choose?

Work down this list and stop at the first row that matches your situation.

If you start in Agent Builder and outgrow it, you are not stuck. Microsoft supports copying an agent from Microsoft 365 Copilot into Copilot Studio, preserving its core configuration and instructions so the work is not lost. That makes Agent Builder a reasonable first step even when you suspect you will need more later, which is a genuinely useful property and one of the better arguments for starting simple.

Can you sell an agent built in Copilot Studio or Agent Builder?

This is where the two tools stop looking similar. Microsoft publishes a distribution matrix per build path, and it is unforgiving.

So the honest answer to "can I sell what I build here" is: only if you build a multitenant custom agent in Copilot Studio, or you leave both no-code tools behind and use the Microsoft 365 Agents Toolkit. Anything you make in Agent Builder is a tenant-internal asset by design, permanently. That is fine if it was always meant to be, and painful if you spent a quarter assuming otherwise.

Even the paths that do reach the marketplace end at an admin. Microsoft is explicit that an agent is not visible to users until an admin approves the request, and that publishing to an organization's app catalog requires admin approval. The full picture of how agents move from a maker's screen to a user's Copilot, and the four different Microsoft catalogs people call an agent store, is covered in our guide to the Microsoft Agent Store.

Is Agent Builder the same as Copilot Studio lite?

Effectively, yes, and Microsoft's own documentation URLs still carry the "copilot studio lite" naming for the Agent Builder publishing flow. It is the same lineage: a simplified authoring surface that produces declarative agents using the Microsoft 365 Copilot orchestrator, foundation models and services, without exposing the Power Platform underneath. The lite framing is fair as long as you read it as "fewer capabilities" rather than "cheaper version of the same thing," because the two tools produce agents with genuinely different ceilings.

Where each one falls short

Agent Builder's limit is not the authoring experience, which is good. It is that a retrieval agent solves a narrow problem. Most of the work people hope to automate involves reading something, deciding something, and writing the result somewhere else. Agent Builder does the first third.

Copilot Studio's limit is the opposite. It can do the whole job, but you take on credit forecasting, a second admin center, environment strategy, connector governance and a build cycle measured in weeks. For a single well-defined outcome, that overhead frequently costs more than the outcome is worth, especially for a team under a hundred people without a Power Platform practice.

Both share a harder constraint: they reason over what Microsoft Graph and your connectors can reach. Work with a specialist data model, document extraction with structured output, or a vertical workflow with its own rules, usually wants a purpose-built product rather than a general agent pointed at a SharePoint library. That is the gap ready-made agents fill. You can browse agents by category and see the integrations and permissions each needs before committing, or read how the licensing routes fit together in AI agents for Microsoft 365.

The one-line answer

Agent Builder for a small team's questions, Copilot Studio for a department's work, the Agents Toolkit or a multitenant Copilot Studio agent if you plan to sell it, and a ready-made agent if you needed it last week. Everything else in the comparison follows from that.