Agent Builder is for small helpers that answer questions. When your helper needs to do things, like fill in a form or run on its own, you move it to the bigger workshop.
Agent Builder makes agents that answer from instructions and knowledge. Copilot Studio is the next step up. It adds actions, workflows, triggers that run without anyone asking, and more knowledge. Moving brings more cost and more responsibility, so I only move when one of a few clear signs appears.
Move from Agent Builder (declarative, no external actions, capped knowledge) to Copilot Studio when you need actions/connectors, agent flows, autonomous triggers, larger or structured knowledge, or channels outside Microsoft 365. Expect Copilot Credit metering per feature (e.g. 5 per agent action, 13 per 100 flow actions) and a named owner for ALM and environment governance.
Two tools, one path
Microsoft positions Agent Builder for "quick and straightforward projects". Its documentation says Agent Builder "doesn't support authoring actions that integrate external services", and that to add low-code actions, connectors or workflows you should copy the agent to Copilot Studio. So the two tools are steps on one path, and Microsoft gives you a way to move from one to the other.
I find it helpful to keep Agent Builder as the default and treat moving as a decision with reasons.
Four signs it's time
- The agent needs to do something. If it should create a ticket, update a list or send an approval, that's an action, and actions need Copilot Studio.
- It needs to run without being asked. Copilot Studio supports agents triggered by events, such as a new order arriving. Microsoft's billing page has exactly that example: an order processing agent triggered by each new order.
- It needs more knowledge than Agent Builder allows. Agent Builder caps sources per agent, for example 100 SharePoint files and four websites. Copilot Studio's knowledge limits are different; for example, its knowledge sources summary lists up to 25 SharePoint URLs in generative mode.
- It needs to be used outside Microsoft 365, such as on a public website. Microsoft's billing examples include a customer support agent on a website.
If none of these apply, I'd stay in Agent Builder. It's simpler to own.
What changes when you move
The first change is cost. Copilot Studio meters each feature in Copilot Credits. Microsoft's rates include 2 credits for a generative answer, 10 for tenant graph grounding, 5 for an agent action and 13 for every 100 agent flow actions. Employee-facing use by a person with a Microsoft Copilot licence, under their own identity, isn't charged. Flows started by other triggers are charged at the standard rate, so an autonomous agent costs money even if every employee is licensed.
The second change is ownership. A Copilot Studio agent lives in a Power Platform environment and may use connectors to other systems. Someone needs to own it: who can change it, how changes are tested, and what happens when a connector breaks.
The third change is limits and enforcement. In a tenant on prepaid capacity, Microsoft says custom agents are disabled when consumption reaches 125% of the prepaid capacity, and admins can set monthly limits for individual agents in the Power Platform admin center.
A worked example
This scenario is illustrative. An IT team built an Agent Builder agent that answers questions about laptop requests from the IT policy. It works well. Now they want it to raise the request in the service desk tool when someone asks for a laptop.
| Question | Answer |
|---|---|
| Does it need to do something? | Yes, raise a ticket |
| Does it need to run unprompted? | No |
| Too much knowledge? | No |
| Used outside Microsoft 365? | No |
One sign is enough. They copy it to Copilot Studio, add the ticketing action, set a monthly credit limit, and name an owner. For licensed staff using it under their own identity, there's no charge. For anyone else, each ticket raised costs credits for the action, plus the answer and any grounding.
What I'm still checking
I haven't tested what carries across when an Agent Builder agent is copied to Copilot Studio, such as embedded files and sharing settings. I'd check that on a test agent before moving a popular one.
Sources
- Microsoft Learn, Agent Builder overview, accessed 11 October 2026.
- Microsoft Learn, Add knowledge sources to an agent in Agent Builder, accessed 11 October 2026.
- Microsoft Learn, Knowledge sources summary, Copilot Studio, accessed 11 October 2026.
- Microsoft Learn, Billing rates and management, Copilot Studio, accessed 11 October 2026.