The first agent most teams build in Microsoft 365 is a simple one: answer questions from a handbook. The mistake that follows is common. They either overbuild it in Copilot Studio, or they push a no-code agent past what it can do.
Microsoft now publishes an official decision guide, and a Microsoft Learn page dated October 2026 says the choice should depend on "the required capabilities and operating model, not audience size alone." This post turns that guide into rules you can apply today. It builds on our earlier piece about repeating work in Microsoft 365 Copilot, which covers the scheduling side.
TL;DR: Agent Builder vs Copilot Studio
| Question | Agent Builder | Copilot Studio |
|---|---|---|
| Where it lives | Inside Microsoft 365 Copilot (Copilot chat in microsoft365.com, office.com and Teams) | Standalone application |
| Authoring | Natural-language configuration, no code project | Managed authoring with workflows and tools |
| Knowledge | Supported Microsoft 365 sources, Copilot connectors, web | Knowledge, connectors and tools of the selected experience |
| External actions | Not supported | Supported through tools and connectors |
| Audience | Users in your organisation, via sharing or org catalog | Internal or external users, via channels |
| Lifecycle | Configure, test, share, submit | Environments, ALM, deployment, analytics |
| Governance | Microsoft 365 agent controls | Power Platform controls plus Microsoft 365 controls |
| Best for | Onboarding or project-information agent | IT request workflow with approvals, customer support with escalation |
What can Agent Builder do?
Microsoft's Agent Builder overview, updated November 2026, describes it as "an easy way to build declarative agents for Microsoft 365" for quick and straightforward projects. Its examples are an agent that gives writing or presentation coaching to organisational standards, and a team onboarding agent that answers questions about a new team.
You can specify dedicated knowledge sources, including SharePoint content and information provided by Copilot connectors, and test the agent before you use, share or publish it. You can build from microsoft365.com/chat, office.com/chat and the Teams desktop and web client. It is not available on mobile versions of those apps.
One change since our earlier coverage: Agent Builder can now add skills. A skill is a reusable packaged task: a directory with a required SKILL.md file plus optional resources and scripts. Microsoft's add-skills article allows up to eight skills per agent, each a compressed .zip of up to 50 MB, with skill instructions under 20,000 characters. The comparison page marks custom skills as in preview, so treat them as early.
The prompt for a quick start is plain English. Microsoft's example asks Agent Builder to create an agent that helps a team write release notes, with a reusable skill that groups changes into Features, Fixes and Other and formats a Markdown changelog.
A rounded figure wearing a belt of abstract tools, one in green, showing an Agent Builder agent configured with instructions, knowledge and skills
What are the limits of Agent Builder?
Microsoft lists known limitations, and they decide most cases:
- No external actions. Agent Builder "doesn't support authoring actions that integrate external services."
- Not in Teams group or 1:1 chats. You can't use agents built in Agent Builder there.
- SharePoint auto-sharing is narrow. It works only when sharing with specific security groups, not everyone in the organisation. You may have to update file permissions yourself.
- Customer Managed Keys are not supported.
- Web policy wins. If an admin disables web content through the Allow web search in Copilot policy, Copilot blocks web content, even though the toggle in the Knowledge pane stays visible.
Sharing has its own rules. Microsoft's sharing article gives two roles: Can edit (owner) and Can chat. A group can only be a chat user, so owners must be individuals. There is an Org-wide sharing for chat access toggle, and publishing to your org catalog needs admin approval. The article also says sharing does not allow deployment across other channels. To publish an agent across multiple channels, you need Copilot Studio.
Access to the agent is separate from access to its sources. Sharing an agent does not grant access to its SharePoint content, and uploaded files become embedded knowledge that anyone with agent access can receive answers from, subject to sensitivity labels. Review uploads before you share.
What does Copilot Studio add?
Microsoft's comparison table is the honest summary. Copilot Studio adds external actions through tools and connectors, internal or external audiences through channels, and environment, application lifecycle and analytics features. Governance moves to Power Platform environment and connector controls.
Microsoft's copy-agent article lists what you gain: versioning, staged deployments and rollback; usage monitoring and analytics; governance such as role-based access and data policies; advanced customisation with conditional logic and external APIs; separate development, test and production environments; and audit trails. For a first build in Studio, see what Copilot Studio is and how to build your first agent. For worked examples, see our IT helpdesk agent and HR onboarding agent guides.
One caution from Microsoft's page: Copilot Studio capabilities, channels and billing vary by the selected harness, so do not assume a feature is available in every Studio agent.
The three-question test
Microsoft's decision guide has three questions. Ask them in this order.
- Do users need an external channel, such as a customer-facing website? If yes, evaluate Copilot Studio, and confirm the experience supports your channel and authentication.
- Do you need external-service actions, workflow logic, or separate development, test and production environments? If yes, evaluate Copilot Studio.
- Can instructions plus supported knowledge and capabilities in Microsoft 365 Copilot meet the need? If yes, start with Agent Builder.
Microsoft adds a point many teams miss: Agent Builder supports organisational distribution through sharing and org-catalog submission, so "needing users across several departments doesn't by itself require Copilot Studio."
| Scenario | Pick | Why |
|---|---|---|
| Team handbook Q and A on SharePoint | Agent Builder | Knowledge only, internal audience |
| Brand-voice writing coach | Agent Builder | Instructions and examples |
| Meeting-notes formatter with a reusable skill | Agent Builder (skills in preview) | Packaged steps, no external system |
| Raise a ServiceNow ticket from chat | Copilot Studio | External action |
| Customer-facing website assistant | Copilot Studio | External channel |
| Approval flow with audit trail | Copilot Studio | Workflow and governance |
| Hourly mailbox scan | Copilot Studio | Scheduled or triggered work |
A clock pointing to a green mark above a waiting package, illustrating scheduled agent work that Agent Builder cannot run and Copilot Studio can
What does Copy to Copilot Studio carry over?
You do not have to start again when you outgrow Agent Builder. In the More options menu choose Copy to Copilot Studio. Microsoft's article lists what moves:
| Copied | Not copied, and what to do |
|---|---|
| Name, description, instructions | Copilot connectors: set up connectors after copying |
| Suggested prompts, icon | Scoped Copilot connectors: not currently supported in Copilot Studio |
| SharePoint files, folders and sites as knowledge | Embedded files: upload again |
| Websites as knowledge | Teams chats and meetings: add the Power Platform connector for Teams |
| Emails: add the Power Platform connector for Outlook | |
| Create documents, charts and code: add code interpreter in settings | |
| Create images from prompts: not currently supported in Copilot Studio |
Four facts stop surprises:
- It is a snapshot, not a sync. Copilot Studio creates a snapshot, and later updates to the original do not affect the copy. Each copy operation creates a new agent.
- The original stays. It remains available in Microsoft 365 Copilot, so decide later whether to delete it and tell users where to go.
- Licences. Copying requires a Copilot Studio licence or a Microsoft 365 Copilot licence, and trial availability depends on admin settings. Users also need the Dataverse entitlement enabled.
- Environments. You pick a Power Platform environment, which needs Dataverse, a supported data location and the right security roles. Admins manage Agent Builder in the Microsoft 365 admin center and Copilot Studio in the Power Platform admin center.
What does each option cost?
The short version: Agent Builder agents do not consume the tenant's Dataverse storage entitlement, according to Microsoft. Beyond that, cost follows capabilities.
Microsoft's prerequisites table shows the pattern. Without usage-based billing, Copilot Chat users can use agents with custom instructions, web search, code interpreter and image generation, but not custom knowledge from SharePoint, Copilot connectors, embedded files or Dataverse. Turning on pay-as-you-go billing, consumed as Copilot Credits, unlocks those. Email, people, Teams messages and Teams meetings as knowledge need a Microsoft 365 Copilot licence. Agent access also depends on the licence of whoever uses it, so an agent you share may error for a user without the right licence.
For Copilot Studio, billing varies by harness and is measured in Copilot Credits. Our pricing and licensing guide explains the credit model and our Copilot Studio first-agent guide shows how it bills in practice. Before you commit, confirm maker access and end-user access separately, as Microsoft advises.
A rule of thumb for admins
Start in Agent Builder when the agent only needs instructions and approved knowledge. Microsoft notes that creating agents is a core Copilot capability when agents are enabled, so you cannot disable Agent Builder creation separately. You can control access, org-wide sharing and catalog approval under the Agents settings in the Microsoft 365 admin center. Pair that with a permissions review, because an agent respects the end user's access. Our Copilot readiness checklist covers the work.
If you would like a guided build of an agent and an automation with an instructor, our Microsoft Copilot and Copilot Studio workshop runs live on December 20 and 21, 2026.
Related reading
- Repeat work in Microsoft 365 Copilot: Agent Builder, Studio and the limits
- What is Microsoft Copilot Studio? Build your first agent
- Build an IT helpdesk agent in Copilot Studio
- Build an HR onboarding agent in Copilot Studio
- Loops, workflows and autonomous agents in Copilot Studio
- Microsoft 365 Copilot pricing and licensing
- Researcher and Analyst agents
- Official: Choose between Agent Builder and Copilot Studio, Copy an agent to Copilot Studio, Agent Builder overview
Details reflect Microsoft Learn pages updated in October and November 2026. Agent Builder custom skills are marked as preview and Copilot Studio capabilities vary by harness, so confirm the current state in your own tenant before you build.
