Forum Discussion
Help with App Permission Policies
That's odd. If you have the App setup as below in Managed Apps..
And your Microsoft apps are set as below in your Global Permission policy..
Then you should't have any problems. Maybe try creating a separate permission policy and assign a test user to it, and see if that sorts it. If not, then I would suggest opening a ticket with Microsoft.
So when users go to Apps within Teams, and search for Incoming Webhook, do they not see the option as below?
Hi PeterRising
That's correct, just having it allowed, and all "Microsoft apps", and the app isn't available.
I've since added it as an allowed 3rd party app, however that's not what i was expecting to have to do.
Cheers
Rob
That's odd. If you have the App setup as below in Managed Apps..
And your Microsoft apps are set as below in your Global Permission policy..
Then you should't have any problems. Maybe try creating a separate permission policy and assign a test user to it, and see if that sorts it. If not, then I would suggest opening a ticket with Microsoft.
I'd allowed the "Incoming webhook" app, and our Global policy was as it is below (this is also how my own Tenant is configured, and it's working as expected)
To make the webhooks app available, i had to set it to this
The user who requested it mentioned he had to quit the Teams app before webhooks was visible, which reminded me of a similar problem when we were testing an actual 3rd party app, we had to quit Teams to make it show up.
We have a couple more Microsoft published apps that I'll be allowing in the next couple days, and have lined up some end users to test for me. Hopefully its as easy as waiting the 24 hours, and quitting teams to clear out any cached settings client side. I'll also set up a test permission policy and add some of our test users into it as an extra check.
Cheers
R
