Jul 12 2020 05:42 PM
Hi All,
We currently have our Global policy set to Allow all Microsoft Apps, block all 3rd party and custom apps. Our assumption was that setting Allow all apps for Microsoft apps, "Teams apps published by Microsoft or its partners can be installed by your users" means that when the Publisher is Microsoft, Microsoft Corp. or Microsoft Corporation, the app would be available to all users to consume.
The issue is, we've recently (2 days ago) enabled the "Incoming Webhook", and it's not available for users to use. Other apps such as Bing News, Azure Boards, Power BI, and Wikipedia Search are available.
Any ideas why it wouldn't be showing up?
Cheers
Rob
Jul 12 2020 10:47 PM
So when users go to Apps within Teams, and search for Incoming Webhook, do they not see the option as below?
Jul 12 2020 10:57 PM
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
Jul 12 2020 11:08 PM
Solution
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.
Jul 12 2020 11:59 PM
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
Jul 13 2020 01:16 AM
Ah yes, it can just be a case of waiting. Things don't always happen quickly in Teams. You definitely should not have had to enable it as a third-party app though.
Jul 13 2020 04:43 PM
Aug 12 2020 10:20 PM
Jul 12 2020 11:08 PM
Solution
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.