Integration Service for Automation Suite User Guide

DELIVERY:

RELEASE: 2.2510

Last updated Nov 11, 2025

Microsoft Outlook 365 authentication

Overview

In Integration Service, when you create a connection to one of our Microsoft Graph-based connectors, you can choose between the following authentication options:

OAuth 2.0 Client credentials – uses a service account and, optionally, connects to your shared mailbox.
Bring your own OAuth 2.0 app – connects to a private application you create, and, optionally, to your shared mailbox.

In case you encounter any errors during the sign-in process, it is recommended to contact your Microsoft Outlook 365 administrator. For more information, refer to the Office 365 Outlook connector documentation.

Admin consent

Note: This section applies only to the Bring your own OAuth 2.0 app authentication options.

Many organizations require the consent of an administrator before you create a connection to an external application. The admin consent workflow requires an admin to approve the app registration to specific users or groups before a connection is established. For more details, check Overview of admin consent workflow and User and admin consent in Microsoft Entra ID in the Microsoft documentation.

Note: Integration Service impersonates the user that creates the connection. The credentials of the user offer access to all of the same resources that they have in the given application. If you share the connection, every change made to Microsoft SharePoint or OneDrive with that connection is made on behalf of that user.

OAuth 2.0 Client credentials

Scopes

The minimal scopes required for creating a connection are the following: Mail.Read, User.Read.All or User.Read.

Adding the Microsoft Outlook 365 connection

To create a connection to your Microsoft Outlook 365 instance, perform the following steps:

Select Integration Service from the left rail.
From the Connectors list, select Microsoft Outlook 365, or use the search bar to find the connector.
Select Connect to Microsoft Outlook 365.
You are now redirected to the connection page.
Enter the required credentials.
Note:
- You must provide a Client ID and Client secret, the Tenant ID, and the Scopes you may need to interact with different activities. For more details check the documentation for activities to learn what scopes they require.
- If you are using a multi-tenant application, keep the default value for the Tenant ID (common).
- If you are using a single-tenant application, retrieve the Tenant ID from Azure. For more details, check How to find your Microsoft Entra tenant ID.
Select Connect.

Bring your own OAuth 2.0 app

Overview

To learn how to create an application, go to the official Microsoft documentation and follow the described steps: Register an application with the Microsoft identity platform.

Note: This is an advanced functionality and requires admin privileges in the target application. Work with your IT administrator to set up your application successfully.

Requirements

When creating your own application to use with Integration Service, you must consider the following requirements:

You must configure the application as a Multitenant or Single tenant application.
You must configure a Web application.
You must configure a Web Redirect URI. The Redirect URI (or callback URL) for your OAuth 2.0 application is provided in the authentication screen when creating a connection: https://{yourDomain}/provisioning_/callback.
You must set up delegated permissions. For more information, refer to Permissions in the Microsoft official documentation.
Generate a client secret for your application.

Important: The advantage of using your private OAuth application is that you can customize permissions depending on your actual needs. To learn which scopes are required for each activity in the Microsoft 365 package, refer to Working with scopes and check out the activities documentation.

The connector uses Microsoft Graph API. Refer to the Microsoft Graph permissions reference page for details on all permissions.

After you create your application, use the Client ID and Client Secret to create a connection with the Microsoft connectors.

Scopes

Minimal scopes required for creating a connection: openid, offline_access, Mail.Read.
Minimal list of scopes required for Outlook triggers:
- For shared mailbox triggers: openid, offline_access, Mail.Read, Mail.Read.Shared.
- For events on calendars: Calendars.Read.
- For events on shared calendars: Calendars.Read.Shared.

Adding the Microsoft Outlook 365 connection

To create a connection to your Microsoft Outlook 365 instance, perform the following steps:

Select Integration Service from the left rail.
From the Connectors list, select Microsoft Outlook 365, or use the search bar to find the connector.
Select Connect to Microsoft Outlook 365.
You are now redirected to the connection page.
Select the Bring your own OAuth 2.0 app authentication type.
Fill in the required fields: Client ID and Client secret, and, optionally, the Scope, required to interact with different activities, Tenant ID, Environment, and Shared mailbox.
Note:
- For more details check the documentation for activities to learn what scopes they require.
- If you use a multi-tenant application, keep the default value for the Tenant ID (common).
- If you use a single tenant application, retrieve the Tenant ID from Azure. For more details, check How to find your Microsoft Entra tenant ID.

Refresh tokens for OAuth applications

Refresh tokens for OAuth applications can be invalidated or revoked at any time by Microsoft. This can happen for different reasons, such as timeouts and revocations. For details, see Microsoft's official documentation.

Warning: Token invalidation results in failed connections and automations are unable to run without fixing connections.

Make sure to follow best practices from Microsoft when creating your OAuth applications. For full details on how to create a Microsoft OAuth app, see the Microsoft documentation.

This issue affects not only the OneDrive & SharePoint connector, but all Microsoft Graph-based connectors, such as Outlook or Teams.

On this page