AccessToBotDenied after publishing Bot to Teams and granting permissions

(1) Share

Report

Posted on by KM-12090803-0

Hi there,

I have created a bot in CoPilot Studio that uses Dataverse tables and Power Automate Flows. I have published the bot to teams via ZIP file and given permissions to some users.
The Dataverse access is also configured to use my (the CoPilot author's) authentication.
I can use the bot just fine in Teams, but everyone else gets errors like this:

It seems like some more permissions are needed, but which ones? The bot is visible to colleagues, but they always get this "AccessToBotDenied" error.

I hope someone can help me.

Best regards,
Karsten

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (4)

Answers (0)

Sort by

IF-05121233-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

I did this to solve my problem, but I didn't check which one solved it. First I went to channels, teams, edit agent details, Teams multi-user collaboration areas and checked the box to allow collaborators to interact with the bot and in about 30 minutes it was activated.

Was this reply helpful? Yes No
Suggested answer

Artur Stepniak 1,539 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,

I'd suggest you to check that you've assigned everything correctly here: https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-share-bots?tabs=web.

In case of any other questions, let me know. If the answer helped you, mark it, so that others can benefit from it.

Best regards,

Artur Stepniak

Was this reply helpful? Yes No
Suggested answer

thehetz 23 on at

Like
a
(0)

Report
Copy link

Link copied!

I have had issues similar to this in the past when publishing using a .zip file. Have you tried publishing through the Teams channel within Copilot studio? Also, since you are leveraging Dataverse in this solution, all of the users that you share the bot with may need to have a Power Platform Premium license assigned to them so they can access Dataverse. Then you could set the permission to connect as the user, rather than as the author. You may also try sharing the Dataverse connection with those users as well, from the Power Platform Admin portal.

Was this reply helpful? Yes No
Suggested answer

KM-12090803-0 4 on at

Like
a
(1)

Report
Copy link

Link copied!

The solution was to give every user of the Bot also the permission for the corresponding power automate flow. Sadly it does not seem possible, to use the CoPilot Authors permission.

Was this reply helpful? Yes No