2.2.4. When to Build, Extend, or Use Prebuilt Agents
One of the highest-value architectural decisions is knowing when to build custom agents versus extending existing capabilities versus using prebuilt agents out of the box. The exam tests this frequently because it directly impacts cost, time-to-value, and maintainability.
Prebuilt Agents — Microsoft provides prebuilt agents that are ready to deploy with configuration:
- Account Reconciliation Agent (D365 Finance) — matches transactions, flags discrepancies and suggests corrections
- Quality Evaluation Agent (D365 Customer Service) — evaluates the quality of customer-service cases and conversations
- Customer Intent Agent (D365 Contact Center) — detects what the customer wants so the conversation can be routed or self-served
- Procurement Agent (D365 Supply Chain Management) — handles supplier communications such as vendor email classification and purchase order follow-up, and can assess how supplier changes affect orders
- Employee Self-Service Agent (Microsoft 365) — answers employees' common HR and IT questions without contacting a person
Use prebuilt agents when the business process aligns with the agent's designed purpose. The agent handles the AI logic; you configure the business rules, data sources, and integration points.
Extend Microsoft Copilot — When users need AI capabilities within their existing Microsoft 365 workflow (Teams, Outlook, Word), extend Copilot rather than building a standalone agent:
- Declarative agents — Custom agents published to Microsoft Copilot with specific instructions and knowledge
- API plugins — Connect Copilot to external APIs for real-time data
- Copilot connectors — Synced connectors index external data into Microsoft Graph so Copilot can search it alongside Microsoft 365 content; federated connectors fetch data live through MCP without indexing it
Microsoft Copilot extensions reach people who work in Microsoft 365, so they fit internal staff. External customers are not Microsoft 365 Copilot users in your tenant; serve them with a standalone Copilot Studio agent on a customer-facing channel.
Build Custom Agents — Build from scratch only when:
- No prebuilt agent covers the use case
- Extension points don't provide enough control
- The solution requires custom models, specialized orchestration, or unique conversational flows
- Regulatory or compliance requirements mandate custom implementations
Decision Matrix:
| Factor | Use Prebuilt | Extend Copilot | Build Custom |
|---|---|---|---|
| Time to value | Days to weeks | Weeks | Months |
| Maintenance burden | Microsoft maintains core logic | Shared responsibility | Fully your responsibility |
| Customization depth | Configuration only | Moderate (plugins, connectors) | Unlimited |
| Cost | Included in license or low incremental | Moderate | Highest |
| Risk | Lowest | Low | Highest |
| When | Process matches prebuilt purpose | Users work in M365 | Unique requirements |
Exam Trap: The exam frequently presents scenarios where a prebuilt agent or Copilot extension would suffice, but a distractor recommends building a custom agent in Microsoft Foundry. The correct answer almost always favors the simplest solution that meets requirements. Building custom is a last resort, not a default.
Reflection Question: A sales team wants an AI assistant that pulls CRM data, suggests next actions, and summarizes meeting notes — all within Microsoft Teams. Should you build a custom agent, extend Microsoft Copilot, or configure a prebuilt agent?