Microsoft Outlook Connector

Microsoft Outlook is a productivity suite for managing email and calendar.
This component allows reading, sending, and managing emails, as well as creating, updating, and managing calendar events and subscriptions.

API Documentation

This component was built using the Microsoft Graph API currently utilizing v1.0

Connections

OAuth 2.0 Authorization Code

Authenticates actions in all Microsoft's Graph API services.

To connect to Microsoft Outlook using OAuth 2.0, create an App Registration in Microsoft Entra (formerly Azure Active Directory).

Prerequisites

• Access to a Microsoft Entra admin center or Azure Portal
• Permissions to create App Registrations

Setup Steps

1. Navigate to Azure Active Directory tenant and create a new App Registration
2. When creating the application, select Supported account types:
   • Choose Accounts in any organizational directory (Any Azure AD directory - Multitenant) to allow users from other organizations to authenticate
3. Under Platforms, add the Web platform:
   • Add https://oauth2.flowbuilder.eu.lansweeper.com/callback for EU sites or https://oauth2.flowbuilder.us.lansweeper.com/callback for US sites as a Redirect URI
4. Navigate to Certificates & Secrets and create a new Client Secret:
   • Copy the Value of the client secret (this will only be shown once)
5. Navigate to the Overview page and copy the Application (client) ID

Configure the Connection

• Enter the Application (client) ID value into the Client ID field

• Enter the Client Secret value into the same named field

• The default scopes are pre-configured for common use cases:

  https://graph.microsoft.com/User.Read https://graph.microsoft.com/Calendars.ReadWrite https://graph.microsoft.com/Mail.ReadWrite https://graph.microsoft.com/Mail.Send offline_access
  

  • https://graph.microsoft.com/User.Read - Read basic user data
  • https://graph.microsoft.com/Calendars.ReadWrite - Manage Outlook calendar
  • https://graph.microsoft.com/Mail.ReadWrite - Manage email
  • https://graph.microsoft.com/Mail.Send - Send email
  • offline_access - Maintain OAuth connection and receive refresh tokens
  • Refer to Microsoft Graph permissions reference for additional scope information

• Additional Authorization Parameters (optional) - Query string parameters appended to the OAuth authorization URL:

  • Use prompt=consent to force Microsoft to display the consent screen, which is useful when the requested scopes have changed and users need to re-authorize
  • Use login_hint=user@example.com to pre-fill the user's email address on the sign-in page
  • Multiple parameters can be combined with & (e.g., prompt=consent&login_hint=user@example.com)

This connection uses OAuth 2.0, a common authentication mechanism for integrations.
Read about how OAuth 2.0 works here.

OAuth 2.0 Authorization Code (Deprecated)

Authenticate using OAuth 2.0 Authorization Code (Deprecated).

You will first need to create and configure a new "App Registration" within your Azure Active Directory tenant.
When creating the application you will be prompted to select the 'Supported account types'. Under this section, be sure to select 'Accounts in any organizational directory (Any Azure AD directory - Multitenant)'.

Prerequisites

• Access to an Azure Active Directory tenant
• Permissions to create App Registrations

Setup Steps

1. Create and configure a new App Registration within the Azure Active Directory tenant
2. When creating the application, select Supported account types:
   • Choose Accounts in any organizational directory (Any Azure AD directory - Multitenant) to allow access from other organizations
3. Under Platforms, add the Web platform:
   • Add the OAuth 2.0 callback URL — https://oauth2.flowbuilder.eu.lansweeper.com/callback for EU sites or https://oauth2.flowbuilder.us.lansweeper.com/callback for US sites — as a Redirect URI
4. Navigate to Certificates & Secrets and create a new Client Secret:
   • Copy the Value of the client secret (this will only be shown once)
5. Navigate to the Overview page and copy the Application (client) ID

Configure the Connection

• Enter the Application (client) ID value into the Client ID field
• Enter the Client Secret value into the same named field
• If Multitenant was not selected when creating the Azure application, replace the Authorize URL and Token URL with tenant-specific values
• The default scopes are pre-configured (any scopes not needed can be removed):
  • https://graph.microsoft.com/User.Read — reads basic user data
  • https://graph.microsoft.com/Calendars.ReadWrite — manages Outlook calendar
  • https://graph.microsoft.com/Mail.ReadWrite — manages email
  • https://graph.microsoft.com/Mail.Send — sends email
  • Ensure the offline_access scope is included in the app registration. It is essential to maintain the OAuth connection and receive refresh tokens. Without it, users will need to re-authenticate every hour.

After saving the integration, users can authenticate with OAuth 2.0 to access their Microsoft Outlook data.

App Verification and Admin Consent

Microsoft requires Azure AD app registrations used in multi-tenant deployments to complete a publisher verification process. This review confirms the app developer's identity, giving end users confidence that they are authorizing a legitimate, verified application.

Azure AD app registrations have two distinct verification concepts that affect how users experience the authentication flow.

Publisher Verification

Complete publisher verification before deploying to end users. Without it, the Microsoft consent screen displays "Unverified" next to the app name. This reduces user trust and may prevent users in organizations with strict Azure AD policies from being able to authorize the app at all.

To verify the publisher:

1. Ensure the organization has a Microsoft Partner Network (MPN) account
2. In the Microsoft Entra Admin Center, open the app registration
3. Under Branding & properties, click Add a verified publisher
4. Enter the MPN ID and confirm

Once verified, the consent screen displays the organization name with a verified badge instead of "Unverified."

Admin Consent

Apps requesting application permissions (permissions that act without a signed-in user) or high-privilege delegated permissions require admin consent before any user in a Microsoft 365 tenant can authenticate. Without admin consent, users see a "Need admin approval" error.

A tenant administrator can grant consent using either method:

Method 1 — Admin Consent URL:

Navigate to the following URL, replacing {tenant} with the Directory tenant ID and {client_id} with the Application client ID:

https://login.microsoftonline.com/{tenant}/adminconsent?client_id={client_id}

Method 2 — Microsoft Entra Admin Center:

1. Navigate to Microsoft Entra Admin Center → Enterprise applications
2. Select the app registration
3. Under Permissions, click Grant admin consent for [organization name]

This connection uses OAuth 2.0, a common authentication mechanism for integrations.
Read about how OAuth 2.0 works here.

OAuth 2.0 Client Credentials

Authenticates actions in all Microsoft's Graph API services.

To connect to Microsoft Outlook using OAuth 2.0 Client Credentials flow, create an App Registration with application permissions in Microsoft Entra.

The Client Credentials flow is used for server-to-server authentication without user interaction, requiring application-level permissions and admin consent.

Prerequisites

• Access to Microsoft Entra admin center
• Permissions to create App Registrations and grant admin consent
• Tenant ID for the organization

Setup Steps

1. Navigate to Microsoft Entra Identity > Applications > App registrations and select New registration:
   • Set Supported Account types to Accounts in any organizational directory (Any Azure AD directory - Multitenant) to allow access from other organizations
   • Set the Redirect URI dropdown to Web platform and add https://oauth2.flowbuilder.eu.lansweeper.com/callback for EU sites or https://oauth2.flowbuilder.us.lansweeper.com/callback for US sites as a Redirect URI
   • Select Register to complete
2. From the App menu, navigate to Certificates & Secrets and add a new Client Secret:
   • Copy the Value for the Client Secret (this will only be shown once)
3. Navigate to the Overview page and copy the Application (client) ID
4. Navigate to API Permissions and configure application permissions:
   • Select Add Permission > Microsoft Graph > Application permissions
   • Add all permissions required for the use case (e.g., Mail.ReadWrite, Calendars.ReadWrite, User.Read.All)
   • Refer to Microsoft Graph permissions reference for available permissions
5. After applying all relevant permissions, select Grant Admin Consent to authorize the application permissions

Configure the Connection

• Enter the Tenant ID for the organization being accessed
• Enter the Application (client) ID value into the Client ID field
• Enter the Client Secret value into the same named field
• Enter the User ID of the user whose data will be accessed (required for user-specific endpoints)
• The default scope https://graph.microsoft.com/.default is pre-configured for the connection

This connection uses OAuth 2.0, a common authentication mechanism for integrations.
Read about how OAuth 2.0 works here.

Triggers

Calendar Event Webhook

Receive calendar event notifications from Outlook. Automatically creates and manages a webhook subscription for calendar events when the instance is deployed, and removes the subscription when the instance is deleted. Supports scheduled renewal to keep the subscription active.

Mail Message Webhook

Receive mail message notifications from Outlook. Automatically creates and manages a webhook subscription for mail messages when the instance is deployed, and removes the subscription when the instance is deleted. Supports scheduled renewal to keep the subscription active.

New and Updated Messages

Checks for new and updated mail messages in Microsoft Outlook on a configured schedule.

Webhook

Receive and validate webhook requests from Outlook for manually configured webhook subscriptions.

Actions

Cancel Event

Cancels an event.

Create Calendar

Creates a new calendar.

Create Event

Creates an event on a calendar.

Create Event Subscription

Creates an event subscription for Microsoft Outlook.

Create Mail Folder

Creates a new mail folder.

Create Mail Folder Subscription

Creates a mail folder subscription for Microsoft Outlook.

Delete All Instance Subscriptions

Deletes all subscriptions pointed at this instance.

Delete Calendar

Deletes an existing calendar.

Delete Event

Deletes an event.

Delete Mail Folder

Deletes the specified mail folder.

Delete Message

Deletes a message by ID.

Delete Subscription

Deletes an existing subscription for Microsoft Outlook.

Get Calendar Event

Gets information about a specific calendar event.

Get Current User

Gets the information and metadata of the user that is currently logged in.

Get Mail Message

Fetches and parses a raw message by ID.

Get Schedule Availability

Gets the free/busy availability information for a collection of users.

List Calendars

Lists all calendars for the user.

List Events

Lists all events for the user.

List Mail Folders

Gets the mail folder collection directly under the root folder of the signed-in user, or under the specified parent folder.

List Mail Messages

Lists mail messages in a user's mailbox.

List Subscriptions

Lists all subscriptions for Microsoft Outlook.

List Supported Languages

Lists supported languages for the current user.

List Supported Timezones

Lists supported timezones for the current user.

Raw Request

Sends a raw HTTP request to Microsoft Outlook.

Send Message

Sends a new message.

Update Calendar

Updates an existing calendar.

Update Event

Updates an existing event.

Update Event Subscription Expiration

Updates the expiration of an existing event subscription for Microsoft Outlook.