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!
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.
To use these Office 365 APIs, it is necessary to use an Active Directory account that is authenticated on the specified Office 365 tenant and to specify the application ID.
Thanks to the consent process, your data is secured. Kickle and/or CTOUCH employees CANNOT, in any way, access your data.
Note: CTOUCH For Teams Go & Kickle Go are both the same product
Executing the consent:
1. Go to: CTOUCH Consent For Teams Go
2. Fill in all required details and press [NEXT]
3. Scope of the consent is shown and press [NEXT] to confirm
4. Sign in with the Microsoft Tenant Administrator account:
5. Accept the shown consent.
6. Consent is done!
Note: If below message pops up, you do not have the administrator rights to accept the consent. Please check the rights from the account you are using and/or login in with the admin account.