Agents for Contoso
Build the two Copilot Studio agents the demo stars — an RFP responder and a KYC chase agent — on a platform where autonomous triggers and multi-agent orchestration are now GA.
- Design the two star agents around provenance and an autonomous trigger
- Distinguish the standard Copilot Studio harness from its newer preview experiences
- Keep agent definitions in the same repo discipline as everything else
Two agents will star in the demo, and both answer a specific finding. The RFP responder drafts DDQ answers grounded in Contoso’s own answer library, with provenance on every line — that is finding D3, weeks of re-answering, addressed. The KYC chase agent fires autonomously when a KYC item goes stale and advances the onboarding state — that is D4, the email-based chase and the refresh backlog, addressed. Neither is a chatbot; each is a worker with a job the client named.
This example uses the standard Copilot Studio harness. Autonomous agents and event triggers are generally available⊙ , so the KYC chase can fire on a stale item rather than waiting to be asked. A2A connections are GA in that experience; connecting agents in the newer GitHub Copilot harness experience is separately in preview.⊙ MCP supplies tools and resources with generative orchestration enabled; do not assume support for every feature of the MCP protocol.⊙ Computer use is GA for cases with no API⊙ , and the model list includes Claude Sonnet 5.⊙
The discipline point: the Copilot Studio VS Code extension, GA since January 2026⊙ , keeps these agent definitions in the same repo as the instruction stack and the data model. The demo agents are versioned artifacts, not clicks in a portal you cannot diff.
Provenance is the product
The RFP responder’s value is not that it drafts fast — anything drafts fast. It is that every drafted line carries a citation back to the answer-library source, so an SME reviewing the queue can trust or correct each claim in seconds. In a regulated firm, an answer you cannot trace is an answer you cannot send. Build the provenance first and the speed second; the reverse impresses no one who has to sign the DDQ.
In the field
Sketch the KYC chase agent’s trigger and its one autonomous action, and write down what it must never do without a human — advancing a stage is fine, sending a client-facing email may not be. That boundary is the difference between an autonomous agent and an unsupervised one.
- 05-agents/ — the RFP responder and KYC chase agent definitions