Forum Discussion

RobD365's avatar
RobD365
Brass Contributor
Jul 13, 2020
Solved

Help with App Permission Policies

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

  • RobD365 

     

    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.

  • RobD365 

     

    So when users go to Apps within Teams, and search for Incoming Webhook, do they not see the option as below?

     

    • RobD365's avatar
      RobD365
      Brass Contributor

      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

      • RobD365 

         

        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.

Resources