Skip to main content
Announcements
Talend Data Catalog 8.0 End of Support: December 31, 2024 Get Details

How-to: Qlik Application Automation connectors to Office 365 require Admin Consent

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
MarkGeurtsen
Support
Support

How-to: Qlik Application Automation connectors to Office 365 require Admin Consent

Last Update:

Jun 20, 2024 8:16:08 AM

Updated By:

MarkGeurtsen

Created date:

Oct 14, 2021 9:49:48 AM

In Qlik Application Automation when trying to connect a connector of the Office 365 suite, some users will experience the following message during the authentication flow:

MarkGeurtsen_0-1634219199976.png

This error can show up for the Microsoft Teams, Microsoft Onedrive, Microsoft Sharepoint and Microsoft Excel connectors and depends on your Office 365 tenant. This article explains different methods on how to allow users to make a connector from Qlik Application Automation.

When an Azure admin navigates to the Consent and Permissions page inside Enterprise Applications, the following will be visible:

MarkGeurtsen_0-1718871338743.png

Admin Consent Request Workflow

If the option Do not allow user consent is selected, the only way to get the Microsoft connectors in Qlik Application Automation working is by enabling the Admin Consent Request workflow. To do this, the admin needs to navigate to Admin consent settings and enable the request box and assign reviewers for each request justification:

MarkGeurtsen_1-1718871557271.png

When a user now creates a connection, they will be asked to provide a justification. This request will be sent to the Azure Administrators of the tenant:

MarkGeurtsen_0-1718884968978.png

When this request is submitted, the reviewers of the request should now see the request:

MarkGeurtsen_1-1718885091184.png

The reviewer can review the request which takes the reviewer to the consent screen with the option to allow access for the organization. This will install an enterprise application in the Azure tenant of the user.

MarkGeurtsen_2-1718885187673.png

 

Classifying low impact permissions

An alternative option is if the Azure tenant selected the option Allow User Consent from verified publishers for selected permissions. 

MarkGeurtsen_3-1718885350258.png

 

When this option is chosen, an Azure administrator of the tenant can head to the Permission Classifications page:

MarkGeurtsen_4-1718885382262.png

 

 

The following scopes will have to be classified as low impact for the different connectors:

Microsoft Teams Microsoft Sharepoint Microsoft Onedrive Microsoft Excel Microsoft Outlook

User.Read

User.Read

User.Read

User.Read

User.Read

offline_access

offline_access offline_access offline_access offline_access
profile Files.Read.All Files.ReadWrite.All Files.ReadWrite.All Mail.Send
openid Files.ReadWrite.All      
email Sites.Read.All      
Team.ReadBasic.All Sites.Manage.All      
ChannelMessage.Send Sites.ReadWrite.All      
Channel.ReadBasic.All        


Microsoft Teams/Sharepoint ( with admin consent )

This connector will always require admin consent and these scopes cannot be classified as being low impact.

Labels (1)
Version history
Last update:
‎2024-06-20 08:16 AM
Updated by: