A product owner asks when to enable generative orchestration for a Copilot Studio agent versus relying primarily on classic topic trigger phrases. Which statement best guides the decision?
Select an answer to reveal the explanation.
Short Explanation
Think of generative orchestration as a smart receptionist that reads tool and topic descriptions and routes you to the right specialist. You still keep classic topics for locked-down, compliance-critical steps.
Full Explanation
Copilot Studio supports classic orchestration, where trigger phrases route to topics, and generative orchestration, where the model chooses topics, actions, or tools from metadata and descriptions. Many production agents mix both: generative routing for flexible intents and authored topics for precise multi-step processes. Generative orchestration lets the model select tools or topics from descriptions and user intent, helping multi-skill agents, while classic topics remain important for deterministic, compliance-critical paths. The claim that generative orchestration permanently deletes all topics and allows only Bing search answers is false; it does not delete topics or force search-only answers. The claim that classic topics cannot call Power Automate, so every agent must use generative orchestration for any action, is false; classic topics can invoke flows and actions. The claim that generative orchestration is required to publish an agent to Teams is false; Teams publishing does not require it. Exam tip: know flexibility vs determinism tradeoffs, and description quality matters for generative tool selection.