Fabrikam wants to deploy their Copilot Studio IT support agent to be available to employees both inside Microsoft Teams and on the company's external customer support portal website. Which deployment approach should the team use?
Select an answer to reveal the explanation.
Short Explanation and Infographic
One agent, many channels — Copilot Studio lets you publish the same agent to Teams, web, mobile, and more simultaneously from the Channels tab. Answer: B.
Full explanation below image
Full Explanation
Copilot Studio supports multi-channel publication from a single agent. The Channels section of the agent configuration allows deployment to Teams, web chat (embeddable via a script snippet), mobile apps, Slack, Facebook, and more — all from the same underlying agent.
Option B is correct. The team publishes once and selects both the Microsoft Teams channel and the custom website channel (which generates a JavaScript embed snippet). The same agent logic, topics, and knowledge sources serve users on both channels. Content can be channel-aware if needed (e.g., showing adaptive cards only on Teams where they render natively).
Option A is incorrect. Maintaining two separate agents for different channels doubles the maintenance burden and creates consistency risks. Copilot Studio is designed to deploy one agent to multiple channels.
Option C is incorrect. Embedding a Teams app in an iframe is technically complex and has significant limitations — Teams apps are not designed to be iframed, and cross-origin policies would block the embed in most scenarios. This approach is unsupported.
Option D is incorrect. While Azure Bot Service underlies some Copilot Studio channel integrations, the developer does not need to manually configure Azure Bot Service routing. Copilot Studio handles the channel connections automatically from its Channels UI.