connect to continue

(0) Share

Report

Posted on by PN-15071445-0

I've designed a copilot agent to provide information on internal stuff like policies from our sharepoint site. On the first attempt, a connect to continue box pops up. every time a colleague clicks the allow button it pops up again. After about an hour, it works but the user experience is poor. After that, the box doesn't reappear to the user. Is there anyway to prevent this?

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Sayali-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello PN-15071445-0 ,

This sounds more like an authentication or consent propagation issue than a problem with the SharePoint knowledge source itself. The repeated "Connect to continue" prompt typically occurs when the user's authentication token or connection hasn't been fully established yet. Once the connection is successfully created and cached, the prompt usually stops appearing for that user. It's worth checking whether the agent's knowledge source or connector requires user authentication, whether all first-time users experience the same behavior, and whether Conditional Access or consent policies are affecting token issuance.
Unfortunately, if user authentication is required, there isn't a way to completely remove the initial consent experience, but the behavior improving after some time suggests a connection or token propagation delay rather than an issue with the agent configuration.

Was this reply helpful? Yes No
PN-15071445-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Hey Sayali,

Thanks for your reply :)

How can I check whether Conditional Access or consent policies are affecting token issuance? Would this be on Sharepoint? Currently, colleagues should have access to all the files the agent is sourcing information.

Was this reply helpful? Yes No
PN-15071445-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

And, yes all users are experiencing this issue. After circa 11 clicks of the allow button the agent connects

Was this reply helpful? Yes No