You've rolled out Microsoft 365 Copilot, and now your organization has entered the AI revolution.
Mission accomplished! ... or is it?
Out of the box, Microsoft 365 Copilot only has access to the underlying LLM's baseline knowledge and some content in your Microsoft 365 tenant.
But most companies have valuable data outside Microsoft 365—manuals, standard operating procedures, policies, inventory systems, ERPs, CRMs, sales data, and more! How can you connect Copilot to these resources? Custom agents are the answer.
But, how do you choose between your agent options? SharePoint Agents, formerly Agent Builder, Copilot Studio, or Declarative Agents with the Microsoft 365 Agents Toolkit (ATK) for VS Code?
You know how! 👉 You’ll attend this session and leave armed knowing the differences between these options and which one makes the most sense for your organization!
📚 CHAPTERS
-------------------------------------------
00:00 : Introduction
12:17 : Why do you need an agent?
14:13 : Copilot adoption & market context
19:17 : Core concepts: prompts, RAG, knowledge types
24:09 : Knowledge vs. actions & foundational knowledge
26:27 : Copilot architecture & orchestrators
29:54 : Copilot's round-trip flow to the LLM
34:39 : The semantic index (Microsoft's moat)
40:08 : Four agent creation options overview
44:10 : SharePoint agents demo
50:17 : Agent Builder demo
53:40 : Copilot Studio demo
59:15 : Declarative agents & M365 Agents Toolkit demo
1:10:10 : Hidden surprises & orchestrator differences
1:16:12 : How to choose: decision factors
1:25:22 : Q&A session
