How can I publish a CoPilot from Studio while having it reference my connector for the agent instead of asking users for their own?

Question

How can I publish a CoPilot from Studio while having it reference my connector for the agent instead of asking users for their own?

Jeremy Duffy 5

I have CoPilot that is working and has a connector to our ServiceNow instance via an Oauth connection. Only a few weeks ago, CoPilot used to warn "publishing this will use YOUR credentials for the connection; are you ok with that?" which is the behavior that I wanted so I said "yes".

However, that option seems to have disappeared and anyone on my team who tries to use it is asked for their own ServiceNow connection - something they won't have. For the purposes of this tool, it's sufficient that I have that access (read-only) so I need the CoPilot to use mine instead.

Users should be able to talk to my agent via CoPilot or Teams and get responses that include data from ServiceNow.

Note that I already found a promising control in settings > connection settings > connection parameters which SEEMS to do what I need, but doesn't actually work.

User's image

Prasad-MSFT 10,481 Reputation points Microsoft External Staff Moderator

2026-01-06T12:20:44.62+00:00

Thanks for raising your issue. We will check this at our end and will update you accordingly.
Prasad-MSFT 10,481 Reputation points Microsoft External Staff Moderator

2026-01-07T12:43:42.64+00:00
Now Copilot defaults to using each user’s credentials. To make Copilot always use your ServiceNow OAuth connection:

Go to Copilot Studio → Settings → Resources → Connection references

Make sure the ServiceNow reference is bound to your connection

Go to Settings → Security → Run-only users

Add your users (or Everyone)

For ServiceNow, select Use this connection

Choose your OAuth connection

Republish the Copilot
Jeremy Duffy 5 Reputation points

2026-01-07T14:53:01.2033333+00:00

I do not see that setting

However, I checked the connection parameters sharing option again and it there are some additional options that I haven't seen before so I thought an update might have been made. I tested it again, but have somehow reached a "usage limit".
Prasad-MSFT 10,481 Reputation points Microsoft External Staff Moderator

2026-01-12T11:10:07.5733333+00:00

Are you still getting that error? Jeremy

I was analysing and it seems like Connection parameter sharing still will NOT allow OAuth identity sharing. You can no longer force a Copilot Studio agent to use the maker’s OAuth credentials for all users for most SaaS connectors (including ServiceNow). What you’re seeing is by design, following recent security changes.
Jeremy Duffy 5 Reputation points

2026-01-12T14:44:55.8766667+00:00

The usage limit issue went away, but I'm back to the original issue. So what connection types CAN be shared? Do I have to use my personal credentials instead? Because that seems like a bigger security risk. Or is there no type of credential that can be shared which makes me wonder why the setting is there at all. And how are we supposed to write agents that have connections to other tools that service users who obviously wouldn't have connections to our other internal systems. If that's "by design", it seems designed to fail.

Answer recommended by moderator

0 additional answers

Your answer

Prasad-MSFT 10,481 Reputation points Microsoft External Staff Moderator

2026-01-06T12:20:44.62+00:00

Thanks for raising your issue. We will check this at our end and will update you accordingly.
Prasad-MSFT 10,481 Reputation points Microsoft External Staff Moderator

2026-01-07T12:43:42.64+00:00

Now Copilot defaults to using each user’s credentials. To make Copilot always use your ServiceNow OAuth connection:

Go to Copilot Studio → Settings → Resources → Connection references

Make sure the ServiceNow reference is bound to your connection

Go to Settings → Security → Run-only users

Add your users (or Everyone)

For ServiceNow, select Use this connection

Choose your OAuth connection

Republish the Copilot
Jeremy Duffy 5 Reputation points

2026-01-07T14:53:01.2033333+00:00

I do not see that setting

However, I checked the connection parameters sharing option again and it there are some additional options that I haven't seen before so I thought an update might have been made. I tested it again, but have somehow reached a "usage limit".
Prasad-MSFT 10,481 Reputation points Microsoft External Staff Moderator

2026-01-12T11:10:07.5733333+00:00

Are you still getting that error? Jeremy

I was analysing and it seems like Connection parameter sharing still will NOT allow OAuth identity sharing. You can no longer force a Copilot Studio agent to use the maker’s OAuth credentials for all users for most SaaS connectors (including ServiceNow). What you’re seeing is by design, following recent security changes.
Jeremy Duffy 5 Reputation points

2026-01-12T14:44:55.8766667+00:00

The usage limit issue went away, but I'm back to the original issue. So what connection types CAN be shared? Do I have to use my personal credentials instead? Because that seems like a bigger security risk. Or is there no type of credential that can be shared which makes me wonder why the setting is there at all. And how are we supposed to write agents that have connections to other tools that service users who obviously wouldn't have connections to our other internal systems. If that's "by design", it seems designed to fail.

Answer 1

Jeremy Duffy 5

The Microsoft tech above is WRONG. The answer I was looking for which WORKED was to adjust my tool in the "Additional Details" section it lists "credentials to use" and has the option of "maker-provided credentials"

I made this change and it worked. I found out from a coworker who had dealt with this and found the answer before. Pretty disappointed that not only was the official MS answer was not helpful, but was wrong.

0 comments

Share via

How can I publish a CoPilot from Studio while having it reference my connector for the agent instead of asking users for their own?

0 additional answers

Your answer