Building Agents: Create, Test & Publish
Step-by-step: create a Copilot Chat agent in 15 minutes, build a SharePoint agent, then test and refine it before sharing with your team.
Two ways to build agents
Think of it like making a sandwich.
Copilot Chat agent = you describe what you want and the kitchen builds it. You say “I want a club sandwich with extra pickles” — Copilot Studio takes your description and creates the agent. You can also use a recipe (template) as a starting point.
SharePoint agent = you pick ingredients from what’s already in the fridge. You point the agent at a SharePoint site and say “answer questions about what’s in here.” It’s scoped to that content.
Both are no-code — you don’t write a single line of programming. If Kai at Brew & Byte can order a sandwich, they can build an agent.
Creating a Copilot Chat agent
This is a two-tab process in Copilot Studio’s lite experience:
Tab 1: Describe (the quick way)
- Open Copilot Chat → click Create agent
- You’ll see the Describe tab — type what you want in plain English:
- “Create an agent that helps new employees find answers about company policies, using our HR SharePoint site”
- Copilot Studio generates a draft agent based on your description
- Review the draft → tweak if needed → click Create
Tab 2: Configure (the detailed way)
If you need more control, switch to the Configure tab:
| Setting | What You Configure |
|---|---|
| Icon & name | Visual identity for the agent |
| Description | What the agent does (shown to users) |
| Instructions | Detailed behaviour rules (tone, scope, limitations) |
| Knowledge sources | SharePoint sites, web URLs, Copilot connectors |
| Capabilities | Code interpreter, image generator (optional) |
| Starter prompts | Suggested questions users see when they open the agent |
Real-world: Brew & Byte builds an onboarding agent
Kai (Brew & Byte’s owner) needs a way for new hires to find company policies without asking 10 different people.
Step 1: Opens Copilot Chat → “Create agent” Step 2 (Describe): Types: “An assistant that answers new employee questions about Brew & Byte policies. Friendly tone. References our HR SharePoint site.” Step 3 (Configure): Adds the HR SharePoint site as a knowledge source. Adds starter prompts: “How do I claim expenses?”, “What’s the dress code?”, “How do I book holiday?” Step 4: Clicks Create → shares with the team
Total time: 15 minutes. Zero coding. New hires now have a 24/7 policy assistant.
Templates — start from a recipe
Instead of describing from scratch, you can start from a template. Microsoft provides templates like:
- Prompt Coach (writing better prompts)
- Writing Coach (improving written content)
- Meeting Facilitator
- Project Helper
Templates come with preconfigured instructions and settings. You customise from there.
Creating a SharePoint agent
SharePoint agents are created directly from within a SharePoint site:
- Navigate to the SharePoint site where you want the agent
- Open the agent panel (from the site home, a library, or a specific file)
- Configure three tabs:
| Tab | What You Set |
|---|---|
| Overview | Agent name, description, icon |
| Sources | Entire site, specific library, or selected files |
| Behaviour | Custom instructions, welcome message |
- Click Create → the agent is saved as a .agent file on the site
SharePoint vs Copilot Chat agents — key differences
| Feature | Copilot Chat Agent | SharePoint Agent |
|---|---|---|
| Created in | Copilot Studio (lite) | SharePoint site |
| Knowledge scope | SharePoint + web + connectors | That specific SharePoint site |
| Extra capabilities | Code interpreter, image generator | Not available |
| Where users access it | Copilot Chat | On the SharePoint site |
| Saved as | Cloud service | .agent file on the site |
Exam tip: SharePoint agents are simpler and more focused — they’re designed for site-specific content. Copilot Chat agents are more flexible — they can combine multiple knowledge sources.
Testing and editing agents
Before sharing an agent, always test it. Here’s the testing checklist:
- Ask varied questions — don’t just test the happy path
- Check tone and style — does it match your instructions?
- Test edge cases — what happens with unexpected questions?
- Verify accuracy — are the answers factually correct?
- Check permissions — does the agent respect who can see what?
- Get user feedback — share with 2-3 colleagues before wide rollout
Editing after creation
Agents aren’t set-and-forget. You can edit them anytime:
- Copilot Chat agents: Open Copilot Studio → find the agent → edit instructions, sources, or capabilities
- SharePoint agents: Open the .agent file on the site → edit Overview, Sources, or Behaviour → click Update
Key concept: When you update an agent, changes take effect immediately for everyone using it. This is why testing is so important — a bad update affects all users instantly.
🎬 Video walkthrough
Flashcards
Knowledge Check
Northwave's marketing team wants to create an agent that answers questions about their brand guidelines. The guidelines are stored in a SharePoint document library AND on the company's public website. Which approach should they use?
Zoe at Brew & Byte created a SharePoint agent for the design team's project site. A week later, the team uploaded 50 new files to the library. Does Zoe need to update the agent?
Next up: Agent Lifecycle — the governance side: who can access agents, how approvals work, and how to monitor agents in production.