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

Thank you for sharing your inputs, CoralieSimonaire​ ! Hope you are well too 😊

I agree with you that this seems related to client-side caching. The multiple sign out and sign ins are the biggest hindrances for adoption at this point.

To add on - The agent was visible in Copilot on the browser. But the SharePoint connection consent card didn't display. I had to get some users to refresh the browser for the connection prompt to be displayed. Now, I'm also seeing a behavior that the agent retrieves from Knowledge source 1 (and not Knowledge source 2).

Previously for the testing and pilot of this agent, I was publishing the agent directly in Copilot Studio through Microsoft 365 and Teams channels. These issues didn't come up then (occasionally apps needed a restart but that was all - there was never any inconsistency in establishing connection or in the responses).

👉 I've just been suggested (through Q&A forum in Microsoft Learn) to wait up to 48 hours since publishing for the agent to appear in Copilot. So I'm going to give that a try and check if these caching related issues go away. I'll post updates on this thread.