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?

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. The correct approach is to publish the agent to both the Microsoft Teams channel and the custom website (web chat) channel from within the same Copilot Studio agent configuration. 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, such as showing adaptive cards only on Teams where they render natively. The approach of deploying two separate agents — one configured for Teams and one for the website — is incorrect because it doubles the maintenance burden and creates consistency risks; Copilot Studio is designed to deploy one agent to multiple channels. The approach of publishing the agent to Teams only and then embedding the Teams app inside an iframe on the website is incorrect because Teams apps are not designed to be iframed, and cross-origin policies would block the embed in most scenarios, making this approach unsupported. The approach of using Azure Bot Service as an intermediary to route messages between Teams and the website is incorrect because, 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.