I've published a Copilot chatbot on Teams and have given access to a few members of my Teams to test it out. The bot worked as expected to most of my team members however certain team members are facing AccessToBotDenied error. How should I go from here?
Error:
Sorry, something unexpected happened. We’re looking into it. Error code: AccessToBotDenied. Conversation ID: xxxxxxx. Time (UTC): xxxxxxx.
In Copilot studio, I was able to follow the steps to create a copilot that is connected to a SharePoint site as a source.
https://www.youtube.com/watch?v=2-VYwC6Akiw
With my global admin account, in the SharePoint site, I can query the content of the site. However when I connect with another regular user account (read or write on the site), it gets the error 'AccessToBotDenied' after entering the code.
For all users to use a bot (copilot - power virtual agent), do we need to give them specific permissions, licences? How to give them access to Dataverse?
This is what I tried without success:
Power Platform Admin Center > Environments > click environment > click see all under Users > click user > Manage roles > check Bot Transcript Viewer, Dataverse Search Role, Dataverse Service Role
SOLUTION: Solved: Re: Error AccessToBotDenied Copilot - Power Platform Community (microsoft.com)
Hi @kailim , where did you give the access to Dataverse? Having the same issue I guess..
I found out the solution myself. For my case it was the problem with data access. Make sure the user who are using the bot has access to your Dataverse. After allowing access, they were able to use the bot without problem.
Were you able to get any resolution here? Bumped into the same error trying to demo an internal bot as well, but not much info on the error otherwise. In our case it's occurring on the Demo Website channel - works for myself as the author and some users, but not others get the error.
1) Publish Copilot
2) At admin.teams.microsoft.com > search user > policies > add app permission policy to user
3) At admin.teams.microsoft.com > search user > policies > add setup policy change to user
Note that the chatbot was working fine before, just all of a sudden gave out that error to a few users.
How did you share it with your team members? Can you describe the steps?