Declarative vs custom engine agent: which one needs extra hosting, which one can act on its own
Verdict: Declarative agents use Copilot's own orchestrator and model, so no extra hosting - but they only respond to a user-started conversation. Custom engine agents need separate hosting (e.g. Azure) but support proactive messaging, triggering workflows without a user starting one.
| Criterion | Declarative agent | Custom engine agent |
|---|---|---|
| Hosting | None needed - uses Copilot's own orchestrator and foundation model | Needs its own orchestrator/model hosting - typically outside Microsoft 365 on cloud services such as Azure, at extra cost (Copilot Studio can host some cases in Microsoft 365) |
| How it starts | User-initiated conversation only | Supports proactive messaging - can trigger a workflow without a user starting the interaction |
| Typical fit | A simple, quick in-app answer bot (e.g. onboarding Q&A grounded in SharePoint content, inside Teams/Outlook) | An automated workflow that must act as soon as a trigger condition is met |
Rules
- Declarative agents use Copilot's own orchestrator and foundation model, so no additional hosting is required.
- A declarative agent runs inside Microsoft 365 apps such as Teams and Outlook and can be grounded in SharePoint content - it fits a simple, quick in-app answer bot.
- A custom engine agent supports proactive messaging, letting developers define workflows and trigger agent behaviour without a user starting the interaction - the defining reason to build one instead of a declarative agent.
Traps
- Agent Builder only produces declarative agents, so a scenario needing proactive triggering (no user prompt) cannot be met by anything Agent Builder makes.
- Agents built from SharePoint are declarative and share the same user-initiated limitation - they cannot start a workflow on their own either.