Good morning
I had a chatbot working properly until yesterday, now each time I'm trying to open it we have this message "Permissions needed. Ask your IT admin to add Global EHS&S Learning Team to this team/chat/meeting."
Is there any actions or things that I need to check?
thanks for the help
go to Microsoft Team App Desktop -> Power Virtual Agents -> chatbot -> Managment -> channel -> Microsoft Team -> Edit detail .
I hope this screen can help u find it .
I don't have the "manage > Channel" where do I find this? thanks
thanks you.
now i found it can fixed by this
tick allow users to add this bot
Hi, for our case, we newly just share the bot with different AAD group, other than the one we originally used before.
Then strangely it worked for us. It's not related to teams admin center setting...at least for us. You might wanna try as well.. Thanks!
Than I have no idea.
My advice is to ask the IT admin...because of the message; '"Machtigingen nodig. Vraag uw IT-beheerder om het xxxxxx toe te voegen aan dit team/chat/vergadering.
it not working for me. when try follow
any solution for share link install bot
Microsoft support solution was working for us !
you are facing this issue because required Teams permissions are not in place, and it required to turn on those permissions. Kindly ask your Teams admin to turn on the below permissions, please refer the screenshot below for more information
1
2
It worked for us good luck all
@Svend79 , great thanks for your detailed information. We also published the bot by hyperlink only.
We'll try assign the setup policy direct to the users and see if it will work...
@YuHash have now tried it with the group policy assignment and it works.
btw. we publish the bot only by hyperlink, it is not found in the store, because we have not yet created an app for it...
Hi @YuHash,
we created a PVA bot and published it for testing to members of an AAD security group. Then when the permission error occurred and they could no longer open the bot, we created a setup policy and assigned it direct to the users. Since then it works again.
We have not yet assigned the group to the policy. Apparently that is the difference. I'll test using the group assignment and get back to you....
WarrenBelz
146,771
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,091
Most Valuable Professional