Announcements
I want to integrate my Copilot Studio agent into a web application using the Agents SDK. The official documentation provides a method called “Connect to Copilot Studio with Agents SDK User Sign-in”, which requires end-user authentication. However, in my use case, I need the agent to be accessible to end-users without requiring sign-in.
I’m aware that the “Default Web Chat Embed Code” method can achieve this, but it does not allow customization of the chat UI, which is a requirement for my application.
Has anyone implemented a similar scenario? If yes, please share your approach or suggestions.
You’re not missing anything, this is mostly a current platform limitation rather than a config issue.
What’s supported today
For web scenarios you basically have three options (as you already spotted in the docs):
Default Web Chat Embed (No Authentication)
Allows anonymous / no sign-in
Very limited UI customization (you’re essentially using the built-in web chat)
Agents SDK with user sign-in
Requires user authentication – there’s no “anonymous” mode here today
Legacy DirectLine
Considered “legacy” and should be used only where Agents SDK doesn’t yet fit your scenario
Key point
That’s why your scenario (custom UI + no user sign-in) can’t be achieved purely with the “Connect to Copilot Studio with Agents SDK User sign-in” option.
Available Options:
If anonymous access is a hard requirement
Right now, the Agents SDK in Copilot Studio cannot be used without user sign-in. The SDK is built to work only with authenticated users because it needs Azure AD identity to run actions securely. That is why the documentation only shows the “Connect to Copilot Studio with Agents SDK User Sign-in” method.
If you want users to access the agent without signing in, Microsoft currently provides only two workable options:
1. Use the default Web Chat Embed (Anonymous Access) This method supports fully anonymous usage and works out-of-the-box, but the UI cannot be deeply customized. You can only do basic styling through the container or CSS. If you only need a simple embed, this is the only supported front-end option.
2. Build a Custom UI + Call the Agent Through Your Backend (Service/Server Identity) If you need a fully custom chat UI but still want the user to remain anonymous, you must call the agent from your backend instead of the browser. Here is how it works:
This pattern is commonly used when teams need custom chat interfaces while keeping users anonymous. It keeps your credentials secure and still allows you to fully control the front-end experience.
At the moment, Microsoft does not offer a direct “anonymous SDK” authentication method.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 827
Vish WR 294
Haque 249
