The name changed, the idea stayed
Microsoft first called its in-app agent maker “Copilot Studio lite” and “Copilot Studio agent builder”. The old documentation URL now redirects to Agent Builder in Microsoft 365 Copilot. It builds declarative agents: an agent defined by instructions, knowledge and a few capabilities, running on Microsoft 365 Copilot’s own orchestration and models.
You build in microsoft365.com/chat, office.com/chat, or the Teams desktop and web clients. You describe the agent in plain language or fill in the configuration, add knowledge and test it next to the editor.
What it can and cannot do
| Agent Builder | Copilot Studio | |
|---|---|---|
| Where you build | Inside Microsoft 365 Copilot and Teams | copilotstudio.microsoft.com |
| Knowledge | SharePoint, Copilot connectors, websites, uploaded files | Also Dataverse, many more connectors, custom data |
| Actions on outside systems | No | Yes: connectors, MCP servers, flows |
| Skills | Can be added | Yes |
| Where it’s managed | Microsoft 365 admin center | Power Platform admin center |
| Storage | Doesn’t use Dataverse storage | Dataverse |
| Publishing | Inside Microsoft 365 Copilot | Also websites, mobile apps, other channels |
A few limits Microsoft lists for Agent Builder:
- No support for customer-managed keys.
- Agents can’t be used in Teams group chats or 1:1 chats.
- Auto-sharing SharePoint files with the agent’s users only works with security groups.
- Admins can’t switch off creation separately while agents are enabled.
Who can use what
Access to Agent Builder depends on your licenses and tenant settings. Under usage-based billing, agents grounded only in public data or instructions are free to use. Grounding in SharePoint, connectors or Dataverse needs either pay-as-you-go or a Microsoft 365 Copilot license, and email, people and Teams knowledge need the Microsoft 365 Copilot license. For the price of that license see How much does Microsoft 365 Copilot cost?.
The common mistake: building the wrong thing in the wrong place
Teams often start in Agent Builder because it is right there, then hit the wall when the agent needs to create a ticket, look up an order or call an API. Agent Builder has no actions that integrate external services. The route is Copy to Copilot Studio, but it is a copy, not a move:
- The original stays where it is and later edits don’t sync, so you now have two agents.
- Copilot connectors must be configured again after copying; scoped connectors and image generation are not supported.
- Embedded files must be re-uploaded; Teams and email knowledge come back only through connectors.
- The person copying needs a Copilot Studio or Microsoft 365 Copilot license and the Dataverse entitlement.
The practical rule: if you already know the agent must act in another system, start in Copilot Studio. If it only answers questions over a set of documents, Agent Builder is enough. More on the step up is in What is the difference between Microsoft Copilot and Copilot Studio?.
What this means for a team
Agent Builder makes it easy for every employee to make a personal helper over a SharePoint folder. That is also the risk: ten people make ten agents over overlapping documents, each with its own instructions, and none of them knows what the others were told. Corrections stay inside one agent.
Where Bombos fits
Agent Builder agents know what one person put in them. Bombos is a plugin that gives Copilot and the other AI tools your team uses (Claude, ChatGPT, Codex, Cursor, your own agents) one shared memory: team knowledge, learned rules and what already sits in mail, documents and repos, traceable, in the cloud or on your own server. One person can try it first with their own agents.
Related questions
Is Agent Builder the same as Copilot Studio?
No. Agent Builder lives inside Microsoft 365 Copilot and is managed in the Microsoft 365 admin center. Copilot Studio is a separate studio managed in the Power Platform admin center, with connectors, workflows, environments and analytics.
Does Agent Builder work on mobile?
No. Microsoft lists microsoft365.com/chat, office.com/chat and the Teams desktop and web clients as the places to build. Creating agents on mobile is not supported.
What gets lost when I copy an agent to Copilot Studio?
Name, description, instructions, suggested prompts, icon, SharePoint and website knowledge are copied. Copilot connectors must be set up again, embedded files re-uploaded, Teams and email knowledge added via connectors, and scoped connectors and image generation are not supported. Later changes to the original don't sync.
Can an admin turn off Agent Builder but keep agents?
Not separately. Microsoft notes that admins can't disable agent creation in Agent Builder on its own while agents are enabled for users.
