Choose the right Copilot Studio integration path for your agent
Diesen Beitrag auf Deutsch lesen
A decision guide compares Teams, hosted and self-hosted WebChat, custom UIs, mobile SDKs, Direct Line, and server-side connectors.
TL;DR
Copilot Studio integration depends on audience, authentication, and control needs. Teams requires no API, hosted WebChat is no-code but cannot provide SSO, the M365 Agents SDK supports Entra ID SSO and streaming for employee scenarios, while Direct Line supports customer and non-Entra scenarios.
Original by Adi Leibowitz, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Match the agent experience to its audience, using Teams for internal users, M365 Agents SDK WebChat for employee SSO, and Direct Line for customer or non-Entra access.
- Admins/CoE: Record the authentication mode and integration pattern before deployment, because hosted WebChat has no SSO and the native mobile SDK currently requires No Authentication.
- Security/Compliance: Use a server-side layer when sanitization, compliance enforcement, or response transformation is required, while recognizing that Direct Line interception adds routing complexity and latency.
Frequently asked questions
Which Copilot Studio integration provides Entra ID SSO for employee-facing WebChat?
The M365 Agents SDK client provides seamless Entra ID SSO for employee-facing WebChat when the agent uses Authenticate with Microsoft.
Why does Microsoft-hosted Copilot Studio WebChat not provide seamless SSO?
The hosted WebChat embed uses manual authentication with a copied validation code, so users cannot receive seamless SSO through that embed.
What authentication limitation affects the Copilot Studio native mobile SDK?
The native mobile SDK currently requires No Authentication, while its Entra ID configuration fields are not functional yet.