3.2.1. Copilot Studio and Custom Agents
💡 First Principle: Copilot Studio lets you teach AI about YOUR organization without writing code—like training a new employee on company policies, except the "employee" can serve thousands simultaneously. It's the platform layer between out-of-box Copilot and custom development. Use it when standard Copilot doesn't know enough about your specific workflows, but you don't need to build from scratch.
When to use Copilot Studio:
| Scenario | Why Copilot Studio |
|---|---|
| HR chatbot | Ground on HR policies, connect to HR systems |
| IT helpdesk | Ground on IT documentation, create tickets |
| Customer FAQ | Ground on product knowledge base |
| Process assistant | Guide users through multi-step workflows |
Copilot Studio capabilities:
- Custom agents: Build AI assistants for specific workflows
- Knowledge grounding: Connect agents to SharePoint, websites, or documents
- Actions: Connect agents to external systems and APIs
- Natural language authoring: Define agent behavior conversationally
- Channels: Deploy to Teams, websites, or other platforms
⚠️ Exam Trap: When a question describes a custom agent scenario (HR bot, IT helpdesk, customer FAQ), the answer is usually Copilot Studio—not Foundry. Foundry is for building AI products and training custom models, not business chatbots.
Reflection Question: A company wants a chatbot that can answer questions about their employee benefits and help employees submit benefits-related requests. Would you recommend M365 Copilot, Copilot Studio, or Foundry?
