Using Connect action in Microsoft 365 Outlook package

Use the Connect action in the Microsoft 365 Outlook package to establish a connection with a Microsoft 365 Outlook server. This is the first action you must use to automate Microsoft 365 Outlook related tasks.

OAuth 2.0 is used to connect to the Microsoft 365 Outlook server. Ensure that you configure OAuth 2.0 properties in Microsoft Azure and then configure the OAuth connection in the Control Room.
  1. Configure OAuth 2.0 properties in the Microsoft Azure portal:
  2. Configure OAuth connection in Control Room.

    For more information, see Configure OAuth 2.0 connection in Control Room.

Settings

  • Click the Azure cloud drop-down and select one of the following:
    • Azure Global: for Microsoft 365 Commercial version (login.microsoftonline.com)
    • Azure US GCC High: for Microsoft 365 Government version (login.microsoftonline.us)
  • Click the OAuth2 Authentication mode drop-down and select one of the following authentication modes:
    • Client Credentials

      For more information, see Microsoft identity platform and the OAuth 2.0 client credentials flow

      Use the following fields to enter the information that is provided for your account on your Azure portal
      • Client ID: enter the Microsoft 365 client or insert it from the Credential Vault.
      • Tenant ID: enter the unique ID for your Microsoft 365 subscription or insert it from the Credential Vault.
      • Username: enter the username that you want to use for accessing the Microsoft 365 Outlook server.

        If you are accessing shared mailbox, ensure that you provide the email address of the user who has access to the shared mailbox

      • Client secret: enter your access token or insert it from the Credential Vault.
      For all the above fields, you can use one of the following tabs to insert a value:
      • Credential: to use a value in the Credential Vault that contains information about the Client ID/Client secret/ username/ password..
      • Variable: to use a user-defined variable that contains information about the Client ID/Client secret/ username/ password.
      • Insecure string: to enter a value.
    • Authorization Code with PKCE

      For more information, see Microsoft identity platform and OAuth 2.0 authorization code flow

      Use the following fields to enter the information that is provided for your Azure portal:
      • Client ID: enter the Microsoft 365 client or insert it from the Credential Vault.
      • Tenant ID: enter the unique ID for your Microsoft 365 subscription or insert it from the Credential Vault.
      • Redirect URL: enter the URL address.

        The bot must run in an attended mode by providing a log in form for the first time where you can enter your log in credentials.

      • Username: enter the email address of the mailbox you want to access within Microsoft 365 Outlook server.

        OAuth2 credentials configured in the Microsoft Azure portal must be used to access this mailbox. If you are accessing shared mailbox, ensure that you provide the email address of the user who has access to the shared mailbox

      Note: If you have selected the Authorization Code with PKCE option, a browser is displayed that implies the connection to the Microsoft 365 Outlook server was established successfully. Ensure that you close this browser to continue.
    • Control Room managed
      Use the following fields to update the information:
      • Connection: click the Pick button to select an existing connection.
        • Click the Provider type drop-down menu to select an available or custom provider.

          For information in creating a custom provider, see Configure OAuth 2.0 connection in Control Room.

        • Click the Connection name to select the corresponding connection for the selected provider.
        • Use the Token type field to select one of the following options:
          • Shared: for a global token.

            An access token of shared type is created when a connection is established to the Control Room. This access token is stored as a credential. When you run your automation, the access token is referenced in the automation using the enterprise application provider type set up in the Control Room.

          • User-specific: for a token that is specific to a user.
            If you select this option, ensure that you log in to your Microsoft 365 account to authenticate and generate a user-specific token. Perform the following steps to use this option:
            1. Log in to Control Room and navigate to My settings > OAuth connections in your profile.
            2. Under the OAuth connections tab, click Login to authenticate.
            3. Sign in to your Microsoft 365 account and select Continue.
            4. Verify the services you have access to and click Continue.

              If the connection is succeeded, it will display the status as Active under the OAuth connections > Connections table.

      • Click one of the following tabs in the Username field:
        • Credential: click the Pick button to select a value in the Credential Vault that contains information about the username.
        • Variable: to use a user-defined variable that contains information about the username.
        • Insecure string: to enter a value.

        If you are accessing shared mailbox, ensure that you provide the email address of the user who has access to the shared mailbox

  • In the Create Microsoft 365 Outlook session field, use one of the following tabs for creating a session:
    • Local session: to specify a session name that can be used only in the current bot.
    • Global session: to specify a session name that can be used across multiple botsbots, such as parent bots, child bots, and all other child bots of the parent bot.
      Recommendation: The parent and child bots should have the same package version.
    • Variable: to specify a session variable that can be used to share that session with other child bots.