Intermittent Post-Deployment Issues with Copilot Agent Using SharePoint Knowledge Sources

Hi Sohnash, 

I hope you're doing well ? 

Yes, I've already seen similar behavior when deploying Copilot Studio agents published to Teams and Microsoft 365 Copilot.

What makes me think this is related to propagation or client-side caching is the fact that the agent becomes visible after signing out and back in, and that some of the issues disappear after users reconnect to Teams or Copilot.

Microsoft documents several scenarios where an approved or published agent does not appear immediately because of client-side caching and recommends signing out and signing back in.

It documents a known issue where Teams may temporarily continue using a previously published version of an agent after it has been published or republished.

However, I haven't found any source that specifically describes the SharePoint consent card not being displayed or a specific malfunction affecting a Dataverse-indexed SharePoint knowledge source.

For those aspects, I would focus on validating the authentication configuration, user/admin consent, SharePoint permissions, and any propagation delays affecting the environment.