Agent Flow revalidating connection to SharePoint Online after deploying Microsoft Team

(1) Share

Report

Posted on by CD-25010348-0

I have an agent flow that pulls records from SharePoint Online. I’ve already configured and authenticated the connection between the agent and SharePoint Online in Copilot Studio. However, after publishing the agent to Microsoft Teams, users are prompted to revalidate the connection the first time they interact with the agent. This leads to a poor user experience. Is there a way to prevent this and ensure the agent uses the connection that was already established in Copilot Studio?

Please see the attached for more details.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

Calling actions from Copilot Studio

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Michael E. Gernaey 53,963 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CD-25010348-0

I responded to you on your other thread about the error itself.

However, to be unfortunately clear in the documentation that this is as expected. Now there are ways to get around it, but those require much different approaches and would in almost all cases not really benefit the end user as activities would be performed by a standard account and therefor tracking and history stink.

Since each is a different platform, consent does not follow across for Agent, and requires you to re-consent again :-(. So the primary way to stop this is to make everything happen as the Maker, but then... everything is done as the Maker not the person.

Unfortunately, you are stuck with, as many complain too about this, what it is. The answer sucks, but its a Microsoft thing, not a community bad answer thing :-(

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No
CD-25010348-0 14 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you @Michael,

Do you mean this is the expected behaviour? Users having to reconnect and reauthenticate Agent Flow even after this has already been done in Copilot Studio by the Maker?

Imagine having 50 Agent Flows, which is very possible. just imagine what users would be facing on their first interaction with the Agent deployed to Microsoft Teams Channel. I suppose Microsoft can do better.

Was this reply helpful? Yes No
Michael E. Gernaey 53,963 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CD-25010348-0

When you build and create flows, by default those flows will run as the person who triggers them (the actions, which aka need a connection), versus the maker.

What I was saying is, yes it is the OOB functionality, unless you specifically want every Connection to specific be the maker, which you can do but then any data written etc will be done as the Maker, not as the user using it.

it's one or the other, but the requirement to click (ok) is required yes.

Was this reply helpful? Yes No
CD-25010348-0 14 on at

Like
a
(0)

Report
Copy link

Link copied!

That you @Michael for your response,

Please How do I make it run on the maker's account? the flow is not meant to write any data, it only spools data in a read only mode.

If I create an Instant Flow in Power Automate for Power Apps, at the click of the button, the flow will run on the maker's account but not on each user's account, I suppose that's how the Agent Flow should have worked.

Was this reply helpful? Yes No