|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "Seamless SSO with Custom Connectors (Yes It's Possible!)" |
| 4 | +date: 2025-12-05 |
| 5 | +categories: [copilot-studio, authentication] |
| 6 | +tags: [manual-auth, sso, authentication, best-practices] |
| 7 | +description: Avoiding the dreaded connection manager dialog for slick authenticated access to custom APIs and MCP servers. |
| 8 | +author: daveburman-msft |
| 9 | +image: |
| 10 | + path: /assets/posts/obo-for-custom-connectors/header.png |
| 11 | + alt: "A typical user reaction to being asked for credentials" |
| 12 | + no_bg: true |
| 13 | +--- |
| 14 | + |
| 15 | +Agents are great at bringing together information from multiple sources to provide intelligent insights to users. The tools available within Microsoft Copilot Studio provide a vast array of options for interacting with external sources. Often those external sources need to be able to authenticate the user, and so agents need to be able to act on behalf of the user. Ideally all of this needs to happen without the user needing to enter credentials, to provide a seamless conversation experience. |
| 16 | + |
| 17 | +If you've tried to incorporate a Microsoft Entra ID OAuth secured custom API or MCP server into an agent, you may have been disappointed to find users being prompted for credentials during the chat. Single Sign-On can be achieved in this scenario, and today we've released [new guidance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-custom-connector-on-behalf-of) which details everything required to ensure this works perfect. |
| 18 | + |
| 19 | +## Challenges ## |
| 20 | + |
| 21 | +When it comes to implementing tools which need to authenticate on behalf of a user, generally a couple of complaints crop up: |
| 22 | +- **Consent Popup** which asks users for their permission to act on their behalf |
| 23 | +- **Connection & Authentication** if the agent cannot create a connection and authenticate on behalf of the user, the agent prompts the user to do it manually |
| 24 | + |
| 25 | +## Consent ## |
| 26 | + |
| 27 | +I'll cover consent briefly as is often perceived as a connectivity issue. It's not; the two are separate. |
| 28 | + |
| 29 | +This is the consent card. |
| 30 | + |
| 31 | +{: .shadow w="638" h="611"} |
| 32 | + |
| 33 | +Tools using credentials on behalf of the user will prompt for the user's consent the first time they run. A bit like when you take your car for a service and the mechanic wants to borrow your keys and drive your car on your behalf; you'd probably want him to ask first. This is **not** a symptom of misconfigured authentication, this is expected, and for now at least, unavoidable. However, this only involves a single click of the "Allow" button, and then it's a distant memory. |
| 34 | + |
| 35 | +## Connection & Authentication ## |
| 36 | + |
| 37 | +The route to correctly configuring SSO is somewhat fraught with peril, and a wrong move at any point is likely to manifest as the _mildly_ frustrating message below: |
| 38 | + |
| 39 | +{: .shadow w="409" h="168"} |
| 40 | + |
| 41 | +If you're trying to configure SSO to a resource secured with a Microsoft Entra ID using OAuth and you see this, it's really just telling you something's configured incorrectly. Unfortunately there are no clues from the agent, it's a matter of systematically working through our [**new guidance**](https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-custom-connector-on-behalf-of) to understand what's wrong. |
| 42 | + |
| 43 | +At a high level, the process looks like this: |
| 44 | +- (If you're implementing a custom API/MCP server) Create an app registration to represent the server, with appropriate scope(s) exposed |
| 45 | +- Create an app registration representing the Custom Connector, including creating a client secret, adding and consenting for the correct permissions, and adding the **Azure API Connections service as an authorized client** |
| 46 | +- Configure the OAuth settings within your Custom Connector |
| 47 | +- Share access to the Custom Connector with users (who need to exist in the environment, see [this recent post from James](https://microsoft.github.io/mcscatblog/posts/unlocking-seamless-access-how-to-ensure-users-can-create-connections-for-copilot-studio-agents/) for more info) |
| 48 | + |
| 49 | +Note, as a maker, some of the crucial steps around connection creation happen in the background while you're adding and configuring the tool. This means you can experience confusing behaviour where SSO works perfectly for the maker, but when a second user comes along and invokes the tool through chat, SSO fails for them. This is common if the step regarding Azure API Connections is missed. |
| 50 | + |
| 51 | +## MCP Tools ## |
| 52 | + |
| 53 | +MCP tools use Custom Connectors under the hood, so all of the above applies equally in MCP scenarios. One point of caution though; if you add an MCP tool using the [MCP Onboarding Wizard](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent#option-1-use-the-mcp-onboarding-wizard-recommended), it will create a Custom Connector in the background, so you'll need to go through the initial auth process within the wizard first, and then go back and alter the Custom Connector's security information. |
| 54 | + |
| 55 | +## The Result ## |
| 56 | + |
| 57 | +With correct configuration, users are prompted for consent when the tool is invoked, and after consent is provided, a connection is created and authenticated in the background. The tool executes and returns a response, all without a single mention of the phrase "connection manager". Wonderful! |
| 58 | + |
| 59 | +Special thanks Adi for delegating permissions to OBO write a blog post on SSO for Custom Connectors, as promised in [this post](https://microsoft.github.io/mcscatblog/posts/you-dont-need-manual-auth/). |
0 commit comments