3.5. Reflection Checkpoint
Key Takeaways
- Three agent types serve different purposes: task agents (triggered, multi-step), autonomous agents (self-initiated, continuous), and prompt-and-response agents (stateless, single interaction). Selecting the wrong type creates fundamental user experience mismatches.
- Topics in Copilot Studio use generative orchestration by default — they're not rigid chatbot scripts. Fallback topic design directly impacts user experience and agent resolution rates.
- Topics and generative orchestration handle the conversation; agent flows are deterministic automation the agent calls as a tool, and Power Automate cloud flows run standalone, independent of any agent. They are related but not interchangeable.
- NLP, CLU, and generative AI orchestration serve different complexity levels. Regulated scenarios often need CLU's determinism; general knowledge scenarios benefit from generative flexibility. Hybrid approaches combine both.
- MCP extends agents with tool access; Computer Use handles UI automation for API-less scenarios. Both add latency and require careful error handling.
- Data processing pipelines (clean, chunk, enrich, index, serve) determine grounding quality. Poor chunking and stale indexes are the most common causes of agent quality issues.
Connecting Forward
Phase 4 applies agent design to specific Microsoft business platforms: Dynamics 365 (Customer Experience, Service, Finance, Supply Chain) and Power Platform. You'll design Copilot customizations within D365 apps, orchestrate prebuilt agents, and integrate AI into Power Apps canvas applications — all building on the Copilot Studio foundations from this phase.
Self-Check Questions
- A company needs an agent that automatically detects when a VIP customer submits a support ticket and fast-tracks it to a senior agent. Is this a task agent, autonomous agent, or prompt-and-response agent? What triggers it?
- An agent built with generative orchestration sometimes routes billing questions to the wrong topic. The billing topic has 5 trigger phrases and a one-line description. What's the most likely cause, and would switching to CLU fix it?
- A legacy HR system has a web interface but no API. The company wants their Copilot Studio agent to look up employee records in this system. Design the solution using available extensibility options.