🏆 A10: MAX OUT Agent¶
Primary Feature: ALL Features Combined — every knowledge source + artifacts + source attribution Status: ✅ Built (Corp) Built in: Corp ✅ 2026-04-09 | Lab ⬜
🎯 Problem It Solves¶
"I want ONE agent that can do EVERYTHING — search my docs, emails, chats, external systems, public web, AND generate documents."
This is the grand finale — one agent using every Agent Builder capability simultaneously.
Why This Agent?¶
Every previous agent (A01-A09) showcased 1-2 features. A10 proves they all work together. This is the demo closer — the moment customers see the full potential.
🏗️ Architecture¶
┌──────────────────────────────────────────────────────────────┐
│ 🏆 MAX OUT AGENT │
│ │
│ FIVE knowledge sources + artifacts: │
│ │
│ 🌐 Web URLs (digital.govt.nz + employment.govt.nz) │
│ 📤 File Uploads (capability docs, case studies, pricing) │
│ 💬 Teams Chats + Meetings │
│ 📧 Outlook Email │
│ 🔗 Graph Connector (ADO Wiki — M365 Updates) │
│ 🎨 Generate documents, charts, and code = ON │
│ │
│ 📝 Rich instructions with: │
│ • Source attribution (every fact tagged with its source) │
│ • Multi-source briefing format │
│ • "What can you do?" self-description │
│ • Cross-source search capability │
└──────────────────────────────────────────────────────────────┘
✅ Capabilities Used (ALL OF THEM)¶
| Capability | Used? | Details |
|---|---|---|
| SharePoint Knowledge | ❌ | Not used (using File Upload instead — faster, no indexing delay) |
| Web Grounding | ✅ | 2 NZ govt URLs: digital.govt.nz + employment.govt.nz |
| File Uploads | ✅ | 3 internal docs (capability statement, case studies, pricing) |
| Graph Connectors | ✅ | ADO Wiki (Supportability) — M365 Release Announcements |
| Office Artifacts | ✅ | Generate Word/Excel/PPT documents |
| My Teams Chats | ✅ | Searches real Teams conversations |
| My Emails | ✅ | Searches real inbox and sent mail |
| Instructions | ✅ | Multi-source persona with attribution + "what can you do?" |
| Starter Prompts | ✅ | 5 working (each targeting different sources) + 1 boundary |
Knowledge Source Count: 5 (the maximum meaningful combination)¶
Agent Evolution:
A01: 1 source ■
A02: 1 source ■
A03: 0 sources
A04: 1 source ■
A05: 2 sources ■■
A06: 3 sources ■■■
A07: 1 source ■
A08: 2 sources ■■
A09: 2 sources ■■
A10: 5 sources ■■■■■ ← MAX OUT
📝 Instructions Used¶
Copy-paste these instructions when building the agent:
You are the MAX OUT Agent — the ultimate all-purpose work assistant built using every capability available in Microsoft 365 Agent Builder. You combine internal documents, public web knowledge, Teams conversations, email, external system data, and document generation into one powerful agent.
## Your Knowledge Sources
You have access to ALL of these (tag each source when you reference it):
- 📤 Internal documents (capability statements, case studies, policies)
- 🌐 Public websites (NZ government and industry sites)
- 💬 Teams chats and meeting context
- 📧 Outlook email conversations
- 🔗 External systems via Graph Connector (ADO Wiki / M365 Updates)
- 📎 Files attached by the user during conversation
## Source Attribution Rule
ALWAYS tag where your information came from using these icons:
- 📤 From uploaded documents
- 🌐 From web grounding
- 💬 From Teams chat
- 📧 From email
- 🔗 From Graph Connector (ADO Wiki)
- 📎 From user-attached file
- 🧠 From my instructions/general knowledge
Example: "📧 Sarah emailed on April 3 about the timeline. 💬 James mentioned in Teams on April 4 that testing is blocked. 📤 Our capability statement confirms we can deliver cybersecurity assessments."
## What You Can Do (response for "what can you do?")
When asked what you can do, respond:
"I'm your all-in-one work assistant. Here's everything I can help with:
📤 Search internal docs — Find info in our capability statements, case studies, and policies
🌐 Research public web — Pull information from NZ government and public websites
💬 Search Teams chats — Find what was discussed, decided, or shared in Teams
📧 Search emails — Find, summarise, and reference email conversations
🔗 Search M365 updates — Find product announcements from the ADO Wiki
🎨 Create documents — Generate Word reports, Excel trackers, or data summaries
📎 Process attachments — Analyse files you drop into our chat
🔍 Cross-source search — Search ALL sources at once for comprehensive answers
Just ask me anything — I'll pull from every source I have!"
## Multi-Source Briefing Format
When asked for a comprehensive briefing, use this structure:
📋 COMPREHENSIVE BRIEFING: [Topic]
📧 Email Context:
- [findings from email, with dates and senders]
💬 Teams Context:
- [findings from chats, with dates]
📤 Internal Documents:
- [relevant info from uploaded files]
🌐 Public Web:
- [info from grounded websites]
🔗 External Systems (ADO Wiki):
- [relevant M365 updates or wiki content]
⚡ Key Takeaways:
- [3-5 most important points across all sources]
📄 Want a document? I can generate a Word report, Excel summary, or briefing document.
## Rules You MUST Follow
1. ALWAYS tag source attribution on every piece of information
2. When asked for a briefing, search ALL available sources
3. Use NZ English spelling
4. Keep answers concise but comprehensive
5. When generating documents, offer multiple format options
6. NEVER fabricate information — if a source doesn't have relevant data, say so clearly
## What You Do NOT Do
- NEVER share confidential pricing rates directly (give indicative ranges only)
- NEVER send emails (draft only, user sends from Outlook)
- NEVER answer questions about topics not covered by your knowledge sources. If asked, respond: "That's outside what my knowledge sources cover. Try asking Copilot directly for general questions!"
🛠️ Quick Build Guide (Copy-Paste Ready)¶
| Step | Action |
|---|---|
| 1 | Go to microsoft365.com/chat → Agents → Create Agent → Skip to configure |
| 2 | Name: A10: MAX OUT Agent |
| 3 | Description: The ultimate Agent Builder showcase — every knowledge source, every capability, every feature maxed out |
| 4 | Instructions: Paste the full instruction block from above |
| 5 | Knowledge → Web content: Add https://www.digital.govt.nz + https://www.employment.govt.nz |
| 6 | Knowledge → Files: Upload 3 files from a08-rfp-response/: capability statement, case studies, pricing |
| 7 | Knowledge → My Teams chats and meetings: ✅ Toggle ON |
| 8 | Knowledge → My emails: ✅ Toggle ON |
| 9 | Knowledge → Advanced → Enterprise Data Connections: Select ADO Wiki (Supportability) |
| 10 | Search all websites: OFF |
| 11 | Generate documents, charts, and code: ✅ ON |
| 12 | Starter Prompts: Add all prompts from the table below |
| 13 | Create and test with T1 ("What can you do?") first — instant response, no searching |
⚠️ This agent has 5 knowledge sources. Ensure all are configured before testing. Graph Connector requires admin pre-setup.
🚨 Gotchas & Design Decisions¶
🏷️ Gotcha 1: Source Attribution Makes Multi-Source Trustworthy¶
With 5 knowledge sources, users need to know WHERE each piece of information came from. Our instructions require the agent to tag every fact:
- 📤 From uploaded documents
- 🌐 From web grounding
- 💬 From Teams chat
- 📧 From email
- 🔗 From Graph Connector (ADO Wiki)
This is critical for trust — customers can verify any claim by checking the original source.
⚡ Gotcha 2: More Sources = Slower Responses¶
With 5 sources, the agent takes longer to respond because it searches ALL of them. Simple questions (answered by one source) are fast. Comprehensive briefings (searching all 5) take 10-20 seconds.
Demo tip: Start with T1 ("What can you do?") — instant response, no searching needed. Then T2 (multi-source briefing) — show the power, accept the speed trade-off.
📊 Gotcha 3: This Agent Could Replace Several Others¶
A10 technically makes A01-A09 redundant for personal use. But for demos, individual agents are better because: - Each agent has a clear, focused story - Customers see the building blocks before the combination - Smaller agents are easier to troubleshoot
💬 Starter Prompts¶
| # | Title | Prompt | Sources Tested |
|---|---|---|---|
| T1 | ❓ What can you do? | What can you do? Show me all your capabilities. | Instructions only (instant) |
| T2 | 🔗 Multi-source brief | Give me a comprehensive briefing about cloud security — search my emails, Teams chats, our internal docs, the ADO wiki, and NZ govt websites. Tag where each piece of info came from. | ALL 5 sources |
| T3 | 📄 Generate report | Search everything you have about M365 Copilot updates and create a Word document summary. | Graph Connector + Artifacts |
| T4 | 📧+📤 Email + docs | Find any emails about customer requirements this week and match them against our capability statement. | Email + Files |
| T5 | 💬+🌐 Chat + web | What was discussed in my Teams chats about compliance this week? Also check digital.govt.nz for latest NZ government compliance requirements. | Teams + Web |
| B1 | 🚫 Boundary | What is the best restaurant in Auckland? | Should decline |
👍 Pros & Cons¶
| Pros | Cons |
|---|---|
| ✅ Every Agent Builder feature in one agent | ❌ Slower than single-source agents |
| ✅ Source attribution builds trust | ❌ Harder to troubleshoot issues (which source failed?) |
| ✅ Genuinely useful as a daily work assistant | ❌ Complex instructions (near 8,000 char limit) |
| ✅ Perfect demo closer — "this is everything combined" | ❌ Overkill for simple use cases |
| ✅ Shows the full potential of Agent Builder | ❌ Still can't take actions (Studio limitation) |
🎤 Demo Talking Points¶
- "Every feature, one agent" — 5 knowledge sources + document generation + rich instructions. This is Agent Builder maxed out.
- "Source attribution" — Every fact is tagged with where it came from. Your users always know what to trust.
- "The building blocks" — We showed you web (A01), files (A02), instructions (A03), artifacts (A04), comms (A05), connectors (A07). Now see them ALL working together.
- "Built in under 10 minutes" — Even with every feature enabled, this took minutes to build. Not days, not weeks.
- "And this is just Agent Builder" — Imagine what Copilot Studio adds on top: workflows, API actions, multi-channel deployment. That's the next level.