Forum Discussion

JoostKoopmans1's avatar
JoostKoopmans1
Iron Contributor
Dec 08, 2017

Error access Outlook Tasks from Flow

We have no issues connecting Flow to Outlook, however when we want to connect to Outlook Tasks we get the following error:   OutlookTasksConnector-PowerApps and Flow needs permission to access re...
Microsoft Flow
Alexandru Tofan's avatar
Alexandru Tofan
Former Employee
Jan 23, 2018

Hi - it turns out this is a consent issue. 

Please work with the tenant admin to check if the “Users can consent to apps accessing company data on their behalf” option in AAD is set to YES.

This option can be found under Azure Active Directory >> Users and groups >> User settings >> Enterprise applications

  • JoostKoopmans1's avatar
    JoostKoopmans1
    Iron Contributor
    Jan 23, 2018

    Hi Alexandru Tofan,

     

    This setting is indeed turned off in our tenant because we do not want our users to give consent to 3rd party apps. However it is strange this setting is only needed for Outlook Tasks, right?

    I cannot test it, but if correct it seems like a design flaw or bug to me...

    • Alexandru Tofan's avatar
      Alexandru Tofan
      Former Employee
      Jan 25, 2018

      Hi JoostKoopmans1,

       

      The Outlook Tasks connector uses a 3rd party app and requires consent. The name of the application is OutlookTasksConnector-PowerApps and Flow and the application ID is 99da6bf4-4525-4bfa-b39f-b6a35789c240. Make sure permission is granted to this app in AAD before attempting to use the connector. It is not mandatory to turn ON the “Users can consent to apps accessing company data on their behalf” option if permission has been granted to the app.

      • Timothy Anderson's avatar
        Timothy Anderson
        Brass Contributor
        Jul 03, 2018

        I'm having trouble locating the app in AAD and our users are getting the error.

         

        Any help figuring out how to search for it?

    • Alexandru Tofan's avatar
      Alexandru Tofan
      Former Employee
      Jan 23, 2018

      I've reported the issue to the appropriate team and I am waiting for an answer as there were several other people who experienced the same behaviour. I do not know why the Outlook Tasks connector behaves differently from Outlook.com connector but I am hoping to find out soon. I will keep this thread updated.

Resources