Getting Started
Basic Concepts
Advanced Concepts
How-to Guides
Building integration flows
Data transformation
Integration patterns
Developing Components
Tenant Management
CRM components
ERP components
E-Commerce components
Marketing-related components
Finance-related components
Office components
Protocol components
Service components
Database components
Utility components
Component Descriptor
Covered in this article

Outlook component


An integration component for the Office 365 Outlook REST API


This component uses OAuth 2.0 authentication, so when deploying it to your team you need to supply OAuth App Client ID and Client Secret. You can register your app to get a client ID and secret via, for that you would need to sign in with either your Microsoft account (, or your work or school account (Office 365).

Client ID and Secret need to be configured in the environment variables MSAPP_CLIENT_ID and MSAPP_CLIENT_SECRET. When specifying callback URI please use your callback URL in a form


for public cloud default tenant use https://your-tenant.address/callback/oauth2

Apart from the OAuth 2.0 button you would need to specify the AD tenant ID if you not sure about that use common.

Before using this component certain Microsoft Graph scopes need to be defined for your application. This can be done via

The list of scopes required by the component is: “ calendars.readwrite mail.send”.

Known issues and limitations

Current implementation uses AD V2.0 OAuth2

Second version of AD protocol has some advantages, see here for more information.

OData output for lastModifiedDateTime has a precision issue

Apparently the lastModifiedDateTime returned by MS Graph has no milliseconds in it is obvious that filter query accept and treat millisecond values correctly there is a workaround for that issue implemented in the code, however you need to keep an eye on it.


Apache-2.0 © GmbH