Microsoft Teams Configuration for FlexO (for Online Meeting)

Microsoft Teams Configuration for FlexO (for Online Meeting)

Prerequisites

1. Administrator account to Azure: https://portal.azure.com/
2. Administrator account to FlexO

Architecture & Concept

FlexO leverages the OAuth protocol to get access to users’ account in order to create, modify, and  delete teams meeting events in their accounts.

OAuth is an open standard protocol that provides a way for a third party applications to access  data without storing users’ password locally, instead only an encrypted bearer token is provided with a limited lifetime. This means FlexO is not storing any users' password relative to their Office 365 account.
OAuth process implemented on Microsoft Identify Platform
OAuth Access Token has a lifetime of 1 hour, that can be refreshed using its  corresponding Refresh Token. FlexO will manage the refresh process automatically.
This is required in order to synchronize calendars between FlexO and the users thin-or-heavy  client (e.g., OWA/Outlook) without the need of installing a plugin or add-on on the client side. 

Azure Configuration

Application Configuration

The first step in the Office 365 configuration for FlexO is to register FlexO in the Azure Console so  that it can be recognized as a trusted 3rd party. This is a required step so that FlexO can prompt authorization request to Office 365 to the users.

Using an administrator account:
  1. Login to the Azure Console at https://portal.azure.com/
  2. On the main dashboard page, navigate to Azure Active Directory then App registrations



  3. Click New registration button, enter an Application name, and a Redirect URI (provided by oomnis for SaaS version, or you own server URL for on-premise installation)



    Under Authentication , add the FlexO  Redirect URIs  according to your plateform domain (in doubt, please refer to your oomnis FlexO representative)



    then select ID tokens  as shown below:



  4. Navigate to Certificates & secrets and click New client secret to generate a new secret


    Warning: Keep a note of the secret Value as it will be needed for the next steps.
    When creating the secret, you should create a secret with a long life span (2 years for example).
    With an expired secret, the connector will stop connecting and you will need to create a new secret and update the configuration.

  5. Navigate to API permissions, click Add a permission, and select Microsoft Graph:



  6. Click on Delegated permissions screen, then select the following permissions:
    1. under OnlineMeetings: select OnlineMeetings.ReadWrite
  7. Once the permissions have been selected, click Grant admin consent for […], then validate Yes



  8. Last step is optional. Navigate to Branding to customize the application by adding the application logo and information URL.

After creating the application, remember to note the Directory (tenant) ID and Application (client) ID as this will be needed later during FlexO configuration.
You will be able to find them in the App Registration Overview.



Remember to note the client secret value before closing the window as it will no longer be visible afterwards. It is required for the FlexO configuration. If
you haven’t noted the client secret , you can generate a new one and update the  FlexO configuration.


Flexo Configuration

Using the Tenant ID , the Application ID and the Application Secret Key previously obtained, you can now configure the connection in FlexO.
Please confirm the Redirection URL and Lifecyle URL with your FlexO representative. Save the configuration, but it is not required to Enable the integration




    • Related Articles

    • Office 365 Configuration for FlexO Integration (Graph)

      Prerequisites 1. Administrator account to Azure: https://portal.azure.com/ 2. Administrator account to Office 365: https://outlook.office365.com/ecp/ 3. Administrator account to FlexO 4. Access to Powershell console as an administrator 5. Public DNS ...

    • Microsoft 365 Configuration for flexEZ

      Prerequisites 1. Administrator account to Azure: https://portal.azure.com/ 2. Administrator account to Office 365: https://outlook.office365.com/ecp/ 3. Administrator account to flexEZ 4. Access to Powershell console as an administrator 5. Public DNS ...

    • Office 365 Configuration for FlexO Integration (EWS)

      Prerequisites 1. Administrator account to Azure: https://portal.azure.com/ 2. Administrator account to Office 365: https://outlook.office365.com/ecp/ 3. Administrator account to FlexO 4. Access to Powershell console as an administrator 5. Internet ...

    • Teams plugin Configuration for flexEZ

      Prerequisites 1. Administrator account to Microsoft Office365: https://admin.microsoft.com Microsoft 365 Configuration (as an administrator) Teams Configuration Connect to the Microsoft O365 administration console via https://admin.microsoft.com On ...

    • Exchange Configuration for FlexO Integration

      Prerequisites 1.  Administrator account to Exchange Control Panel (ECP):  https://[Exchange-Server-url]/ecp/ 2.  Access to Exchange management shell console as an  Exchange administrator 3.  Administrator account to FlexO Exchange Configuration ...