Agent Library
Microsoft Copilot agents for the Tax department — why they matter, how to build them, and 8 ready-to-use templates with full system prompts.
From chat to agent: why it matters
Using Microsoft 365 Copilot as a general chat tool is useful — but the real productivity gain comes from agents: specialised assistants that know your domain, remember your preferences, and are connected to your data. Here's the difference in practice.
Persistent specialisation
💬 Regular Chat
Blank slate every conversation. No memory of your preferred formats, your entity structure, or past analyses.
🤖 Agent
The system prompt is always loaded. The agent knows Canon's OU codes, your VAT regimes, your preferred output format, and your escalation thresholds before you type a single word.
Connected to real data
💬 Regular Chat
You paste data in. If you forget to include it, you get a hallucinated answer.
🤖 Agent
Studio agents can call SharePoint, Power Automate flows, your data lake REST APIs, or Oracle via a connector. Non-Studio agents can be given a curated SharePoint knowledge base. Answers are grounded.
Consistent voice & guardrails
💬 Regular Chat
Output style varies with every prompt. Nothing stops the model from going off-topic or giving an answer with no caveats.
🤖 Agent
The system prompt defines tone, scope, required disclaimers, escalation rules, and what topics to decline. Every response is shaped by those rules.
Re-usable without prompt engineering
💬 Regular Chat
Team members who don't know how to prompt well get poor results. Knowledge lives in one person's head.
🤖 Agent
One expert builds the agent. Everyone else uses it as a simple Q&A tool. Prompt knowledge is encoded in the agent and shared across the team.
Auditable and improvable
💬 Regular Chat
No log of what was asked or answered. You can't measure quality over time.
🤖 Agent
Studio agents have conversation analytics. Non-Studio agents can be versioned in SharePoint. You can see what users ask, identify gaps, and iterate the system prompt systematically.
Integrated into workflows
💬 Regular Chat
Standalone tool. Copy-paste to get results into your systems.
🤖 Agent
Studio agents can trigger Power Automate flows, write back to SharePoint lists, send Teams notifications, and integrate with Oracle via custom connectors.
Which type of agent should I build?
→ Use Copilot Studio if you need:
- • Live API calls or ERP connector actions
- • Write-back to systems (create records, trigger flows)
- • Conversation analytics for compliance
- • Hard-coded dialog branches
- • Multi-channel deployment (Teams + SharePoint + portal)
→ Use Non-Studio (Declarative) if you need:
- • Fast setup (<1 hour, no IT required)
- • Answers grounded in existing M365 content
- • A proof of concept before full Studio investment
- • Read-only research or policy lookup
- • No additional licensing cost