What it does

Agent Builder (the "Copilot Studio agent builder") is the lightweight, in-Copilot maker experience for spinning up a declarative agent without leaving Microsoft 365 Copilot. You describe what you want, add knowledge and a few actions, and publish.

Key facts

• Produces declarative agents — same runtime as agents built in full Copilot Studio.
• Accessed from within the Microsoft 365 Copilot app; aimed at business makers, not developers.
• Knowledge sources: SharePoint content and Copilot connectors. You can test the agent before you use, share or publish it.
• Skills can be added by supplying one or describing it in natural language. That's in preview and limited to organisations enrolled in the Microsoft Frontier Program.
• Available from microsoft365.com/chat, office.com/chat and the Teams desktop and web clients, on both the Work and Web options. Not on mobile.
• Agents built here don't consume the tenant's Dataverse storage entitlement.
• Needs outbound access to *.api.powerplatform.com on top of the standard Microsoft 365 URLs, for authoring, configuration, publishing and sharing.
• Publishing scope is you, specific people, or the whole org (org-wide needs admin approval).
• Access, and what you can add to an agent, depends on the licences assigned in the tenant. Check the licensing pages rather than assuming Copilot alone covers every capability.

When to use / skip

Use for quick, single-purpose agents a business user can own — a policy Q&A bot, a team assistant over a SharePoint site. Skip when you need custom actions, complex logic, ALM, or environment management; graduate to full Copilot Studio instead.

Configuration decisions

• Publish scope: self, named users, or org-wide.
• Which SharePoint content to ground on.
• Whether the instructions are tight enough to keep the agent on-topic.

Gotchas

• Governance surprises people: users can build agents themselves, so admins need a policy before it sprawls.
• Feature parity with full Copilot Studio is deliberately limited — you'll hit the ceiling on anything non-trivial.
• Org-wide publishing sits in an approval queue; it isn't instant.
• Known limits: agents built here can't be used in Teams group or 1:1 chats, customer-managed keys aren't supported, and auto-sharing SharePoint files works only for specific security groups, not everyone. For anyone else you grant file permissions by hand or the agent returns nothing.
• If an admin turns off web search in Copilot, web content is blocked as a knowledge source, but the Web content toggle in the Knowledge pane stays switched on. The policy wins; the UI is just misleading.

Consultant notes

• Good for citizen makers, but agree tenant-level controls first or you'll be untangling shadow agents later.
• It's the on-ramp to Copilot Studio — set expectations that "real" agents may need to move there.
• No connector cost beyond existing Copilot licensing for basic SharePoint grounding, but custom connectors change that.
• Check the Teams group chat limit against the use case early. "Put it in our project channel chat" is a common ask and it won't work.
• Admins can switch Agent Builder off per organisation, so confirm it's actually enabled before running a workshop.

---

Review if Agent Builder's knowledge sources, skills preview or publish scopes change.