One Time Easy Authentication & Permissions

(0) Share

Report

Posted on by YJ-02010636-0

Is there a way in Copilot Studio to let users authenticate all required connectors once in Teams/M365 Copilot UI (where the agent is deployed in), instead of being prompted again and again when each flow or action is hit?

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Prasad-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Unified, one-time authentication for all connectors is not currently available in Copilot Studio. Each connector requires separate authentication when first used.

Was this reply helpful? Yes No
WH-23060312-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Prasad-MSFT, just to clarify, I get that connectors must be authenticated separately, but this is assuming that they need to be authenticated in the first place. My question is, do they need to be authenticated?

For context, I have a Copilot Studio agent that uses a SharePoint Knowledge Source. I want to publish this agent in Teams. When the user invokes the SharePoint Knowledge Source connector for the first time, they are asked to approve the connection. This prompt disrupts the user experience, especially when it appears multiple times across different Knowledge Sources.

Is there any way to bypass this prompt?

Was this reply helpful? Yes No
Suggested answer

chiaraalina 2,425 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @YJ-02010636-0

You can use Maker‑Provided Credentials, but only in very specific and controlled scenarios. Don't use it for personalized data retrieval requiring user‑specific,
row‑level security scenarios where each user must only see their own data permissions etc.

Example: Internal FAQ bot (read‑only SharePoint knowledge)

When using maker‑provided credentials:

The agent executes all connector actions using the maker’s or a dedicated service account’s identity

End users are never prompted to authenticate or create connections

Every user sees and acts through the same security context

From a backend perspective, there is no user differentiation at all

Was this reply helpful? Yes No