To build an agent in Microsoft 365 Copilot, define a focused task, add instructions and suitable knowledge sources, test the result, then choose who can use or edit it. Agent Builder creates declarative agents: assistants configured for a particular purpose. Microsoft positions it for straightforward, scenario-specific work; it points builders to Copilot Studio when they need external-service actions, low-code workflows, or deployment across multiple channels.
Start with one clear job and choose sources deliberately: sharing an agent does not automatically give its users access to every linked file.
1. Choose the right builder
Use Agent Builder for a focused assistant that works with instructions and selected knowledge sources. Microsoft lists the creation experience at microsoft365.com/chat, office.com/chat, and in the Microsoft Teams desktop and web apps; the listed experiences are not available in their mobile versions. Microsoft’s Agent Builder overview
| If your agent needs to… | Use Agent Builder | Consider Copilot Studio |
| Handle a straightforward, scenario-specific task | Microsoft describes Agent Builder as suited to quick, focused agents. | — |
| Take actions that integrate with external services or use low-code workflows | These are outside Agent Builder’s authoring scope. | Microsoft directs builders to Copilot Studio for these needs. |
| Deploy across multiple channels | Agent Builder is not the path Microsoft identifies for this deployment. | Microsoft points builders to Copilot Studio for multi-channel deployment. |
This is a decision guide for the capabilities at issue, not a complete feature comparison. Microsoft’s overview and sharing and management guidance describe the respective boundaries.
2. Define the agent’s job and instructions
Before configuring sources, write down who the agent is for, the task it should handle, and the kind of response it should produce. Keep its scope narrow enough that you can test whether an answer serves the task. Agent Builder supports describing an agent in natural language or configuring it manually.
Turn that outline into instructions for the agent. State what it should do with the knowledge you provide and where its task ends. Review the resulting instructions before moving on, rather than assuming a short description covers every boundary.
3. Add knowledge sources that fit
Choose sources the agent needs for its task, then check their per-agent limits. Microsoft lists public websites, SharePoint and OneDrive files, Teams chats and meetings, Outlook email, uploaded files, and Microsoft 365 Copilot connectors among the available knowledge sources. Some sources depend on licensing and tenant configuration; Dynamics 365 and Power Apps data also require administrator enablement. Microsoft’s knowledge-source guide
| Knowledge source | Limit per agent |
| Public websites | 4 URLs |
| SharePoint | 100 files and 1 list |
| OneDrive | 50 files |
| Teams | 5 chats and 5 meetings |
| Uploaded files | 20 files |
These are separate limits by source type, not one combined file allowance. If the task depends on more material than a source limit permits, narrow the knowledge set to what the agent needs rather than building around a larger collection.
The Cloud files interface shows where to browse work files. Agent Builder also has a “Choose other data sources” option above connector tiles such as Azure DevOps Work Items, Confluence, and GitHub.
4. Set web access with tenant policy in mind
Agent Builder includes a web-content setting, but an administrator’s Allow web search in Copilot policy takes precedence. If that policy blocks web content, the setting in the interface can remain visible even though the agent cannot use web content as a knowledge source. Microsoft’s Agent Builder overview
5. Test the agent before sharing
Try representative questions for the task you defined. Check whether the responses follow the instructions and use the sources you intended, then adjust the instructions or source set where needed. Microsoft recommends testing an agent before using, sharing, or publishing it.
6. Share it with the right access
Agents start private. When you share one, choose between Can chat, which allows interaction, and Can edit, which gives owner-level editing, sharing, and management rights. Publishing to the organization catalog is a separate route and requires administrator review and approval. Microsoft’s sharing and management guide
Check the access implications of each knowledge source before sharing. SharePoint and OneDrive permissions and sensitivity labels continue to apply, so giving someone access to the agent does not by itself give them access to every linked file. Uploaded files behave differently: people who can use the agent can receive responses grounded in those files, subject to the files’ sensitivity-label permissions. Microsoft’s sharing guidance and knowledge-source guidance explain these distinctions.