Hi!
I've noticed multiple times that the access given to my Copilot bot seems to expire/stop working without any indications, and without removing teammates from the shared list.
Question: is there a way to prevent it? Or at least do you know when exactly such scenario occurs?
CONTEXT
An example scenario:
1. I assign read permissions.
2. User can freely interact with the bot.
3. Then the permissions suddenly stop working.
4. I have to remove permissions and readd again to fix it.
I believe this happens most often on republishing of the agent, but I may be wrong. I DO NOT change any permissions on my own, unless they stop working.
I share access via:
Channels -> Teams and Microsoft 365 Copilot ->Availability options -> Share to my teammates and shared users
So one of the things that are happening over many scenarios, is caching issues. It's a headache all over.
Some suggestions
1. (individuals) can try to clear their cache and try
2. Make sure you are using versioning in the agent. Like in D365/Power Platform, it will help to force a refresh because it will force the system overall to see the agent as new, where-as many times when its just the agent and not the meta-data about the agent it will not.
3. Unfortunately as mentioned Caching is a huge problem in different scenarios and effects users both in permissions or logging into the agent or infinite looping etc. If you really cannot get this fixed for a user, then go and remove the Agent from whatever Channel has the issue. Give it a few minutes at least before you put it back. When its teams also look at clearing the Teams cache locally for users after having them log out of teams, clear the teams cache and log back in.
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?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.