User permission error

[Chris_Williams]

Hi,

I've deployed a PVA-Teams chatbot & when the user Adds the bot & it loads - - it comes back with a permissions error. 

As a temporary alternative, I've setup & deployed a chatbot from Web-PVA and this doesn't present any user error.

I would be grateful for any advice as to how I can tackle this permissions issue.

Thanks

[renatoromao]

HI @Chris_Williams ,

We already talk about it in this community, let me some minutes to send here.

[renatoromao]

We have a delay to talk with chatbot after publish (whole solution here): Solved: User can't talk to bot - Power Platform Community (microsoft.com)

[Chris_Williams]

A delay of months?  My chatbot has been published for a long time.  Users still can't talk to it.

[renatoromao · Accepted solution]

Hi @Chris_Williams ,

Sorry for your bad experience!

I recommend you to create a ticket to support, they can investigate better: https://powervirtualagents.microsoft.com/en-us/support

[renatoromao]

Did you see this link that I sent?

I fixed now because is not opening to the correct topic: Solved: User can't talk to bot - Power Platform Community (microsoft.com)

@Chris_Williams 

[Jcook]

Hello @Chris_Williams 

Is the bot setup to be used by whole organization in the security tab ?

It might be only accessible from same team the bot is built in:

https://docs.microsoft.com/en-us/power-virtual-agents/teams/configuration-security-teams

[Chris_Williams]

Thanks RenatoRomao & Jcook.

I'm only trying to use it in the group it is created within / linked to.  Other teams in my organisation have been able to deploy their bot without any trouble.  I created the bot months ago & have disabled, disconnected, republished, re-connected to the team many times over the months.  It's certainly not a time delay issue.

I was able to upload a web-PVA created chatbot, and as I say other teams within the organisation can use chatbots, so I don't believe it's an Teams Admin setting.  It appears to be only my account (I am an owner of the team).

I will submit a ticket to Microsoft.

Thanks for looking, Chris.