Separate a knowledge assistant from a broader agent with tools, workflows, and publishing channels.
Conversation & research · Documented · Documentation checked 2026-10-04
Microsoft 365 Copilot Agent Builder and the separate Copilot Studio product.
Tenant policy and licensing determine Agent Builder access; Studio publishing, connectors, and metered usage have their own requirements.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Separate a knowledge assistant from a broader agent with tools, workflows, and publishing channels.
Agent Builder in Microsoft 365 supports a bounded knowledge-agent experience. Copilot Studio is a separate product for richer orchestration, tools, channels, and administration. Neither is the same as an ordinary prompt. Grounding, action tools, publishing, and billing require distinct decisions.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Identify whether a knowledge-only agent meets the task or whether Studio is needed.
- Select a permitted knowledge source and define the audience and answer boundary.
- Build and test in the documented product with synthetic questions, including missing answers.
- Review authentication, connected actions, policy, and licensing before publishing to a channel.
Worked example
A workshop FAQ agent can answer from an approved agenda without booking sessions. If later connected to registration, that action needs an authenticated flow and human review of participant details. Begin with retrieval-only behavior.
Answer questions only from the approved workshop agenda and FAQ. Give the supporting reference. If the answer is absent or contradictory, say you cannot establish it and route the question to the organizer. Do not register people, send messages, or edit the agenda.
Inspect and verify the result
Test known answers, absent answers, contradictory sources, and unauthorized requests. Inspect the actual source permissions and deployment identity. Review tool calls separately from conversational replies.
Limits and troubleshooting
Agent Builder’s supported knowledge and publishing scope differs from Studio. Connector and metered-agent access may require additional licensing. If a task needs actions outside the product boundary, identify a separate approved workflow rather than promising it inside the chat.
Data, permissions, and actions
Knowledge access and action permissions are different. Restrict connectors, recipients, and operations in enforceable controls. Publishing expands the audience; verify source rights, authentication, retention, and a process for withdrawing an incorrect agent.
Related reading
Personal Copilot, Copilot Chat, and work context
Identify the Copilot edition and the information it is entitled to use.
From Researcher report to a reviewed Page
Build a cited briefing and a persistent draft Page using the correct Copilot identity.
From a reference collection to a FAQ agent
Use a bounded source collection to design a retrieval-only workshop FAQ agent.
Permissions and meaningful approvals
Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Agent Builder versus Copilot Studio · Microsoft
Copilot Chat FAQ · Microsoft