Step 3. Office 365 Consent For Teams Go

WARNING: The Office 365 consent may take up to 24 hours before active and should be executed by O365 Tenant Administrator!

General information:

Office 365 APIs, OAuth, Consent Flow

BRIX for Teams Go/Kickle uses OpenID authentication to get access to Office 365 resources. Authentication principles are detailed here: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols.

These permissions are OAuth standard permissions (based on Azure AD Application specifications). For Teams Go/Kickle needs to access your Microsoft Teams instance to read the contact list, retrieve the room agenda, etc., as a normal user would do (with the same "level" permissions as a normal user). The "consent" is an activation in your O365 tenant, to specify that "For Teams Go/Kickle is an application and will need to authenticate to to the office server with a user account". 

In addition, the For Teams Go/Kickle app will always need a user account to authenticate to the online server. So there are two security levels: application-level AND user-level. Without a user account, For Teams Go/Kickle cannot access the online server, even if you have approved the consent.

Note: To use these Office 365 APIs, it is necessary to use a O365 account which is authenticated on the specified Office 365 tenant, and to specify the application ID. CTOUCH and/or Kickle employees CANNOT access these APIs.