Microsoft Outlook Mail
Microsoft Outlook Mail is the email service accessed through the Microsoft Graph API, which exposes user and shared mailboxes for reading, sending, replying to, and forwarding email. Nexla uses the Graph mail endpoints to fetch messages, folders, and attachments as a data source, and to send, draft, reply to, and forward messages as a destination.

Power end-to-end data operations for your Microsoft Outlook Mail API with Nexla. Our bi-directional Microsoft Outlook Mail connector is purpose-built for Microsoft Outlook Mail, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Microsoft Outlook Mail or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Microsoft Outlook Mail workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Nexla connects to Microsoft Outlook Mail through the Microsoft Graph API in one of two ways:
- OAuth 2.0 sign-in: you sign in with your Microsoft account, and Nexla reads or sends mail as that user through a Nexla-managed application.
- App-only (Microsoft Entra client credentials): Nexla authenticates as an application (service principal) registered in your own Microsoft Entra tenant, with no user sign-in. Use this method to reach shared mailboxes or other mailboxes that the application has been granted access to.
OAuth 2.0 sign-in
With this method, you do not need to register your own app or supply a client ID or client secret. Authorization is completed entirely from within Nexla using your Microsoft account.
Before creating a credential, confirm the following:
-
You have a Microsoft account with an Outlook mailbox that Nexla should read from or send mail on behalf of.
-
You are able to sign in to that account during credential creation to complete the OAuth consent step.
-
You are prepared to grant the delegated Microsoft Graph mail permissions that Nexla requests. These are the standard user-consent scopes for mailbox access —
User.Read(basic profile),Mail.ReadandMail.ReadWrite(read and manage mail), andMail.Send(send mail) — along withoffline_access, which allows Nexla to obtain a refresh token so the connection does not need to be re-authorized on every run.
Access is scoped to the mailbox of the account you authorize, and Nexla acts only with the permissions you consent to during authorization. For reference on the mail API and its permissions, see the Microsoft Graph mail API overview and the Microsoft Graph permissions reference.
App-only (Microsoft Entra client credentials)
Before creating a credential, confirm the following:
-
An application is registered in your Microsoft Entra tenant, and you have its Directory (tenant) ID and Application (client) ID from the app registration's Overview page, plus a client secret value created under Certificates & secrets.
-
The application has been granted Microsoft Graph application permissions, with admin consent.
Mail.Readis required to read mail.Mail.ReadWriteandMail.Sendare needed only for the destination endpoints that change or send mail. -
You know the address of at least one mailbox that the application can read. Nexla uses it to test the credential.
Application permissions apply to every mailbox in the tenant unless an Exchange administrator limits the application to specific mailboxes. To restrict access to, for example, a set of shared mailboxes, see Role Based Access Control for Applications in Exchange Online. For details on the token flow, see the Microsoft identity platform client credentials flow.
Authenticate
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Select the authentication method that matches your setup, and complete the corresponding steps.
Microsoft Outlook Mail Authentication Methods
- OAuth 2.0 sign-in
- App-only (Microsoft Entra client credentials)
Sign in with your Microsoft account. Nexla reads and sends mail as that user. The Mail.Send permission allows Nexla to send mail from the authorized mailbox; grant it only if you intend to use Microsoft Outlook Mail as a destination.
- Keep Sign in with OAuth selected as the authentication method (it is the default).
- Follow the prompts to authorize Nexla to access your Microsoft Outlook mailbox. You will be redirected to the Microsoft sign-in page to sign in with your Microsoft account and consent to the requested mail permissions.
- Nexla automatically handles the token exchange and refresh once authorization is complete, so the credential does not need to be re-authorized on each run.
Authenticate as an application (service principal) in your Microsoft Entra tenant, with no user sign-in. Use this method to read shared mailboxes or any mailbox the application has been granted access to.
- Select App-only (Microsoft Entra client credentials) as the authentication method.
- Enter your Microsoft Entra Directory (tenant) ID in the Directory (tenant) ID field.
- Enter the application's Application (client) ID in the Application (client) ID field.
- Enter a client secret value of the application in the Client Secret field. This value is treated as a secret.
- Enter the address of one mailbox that the application can read, for example
support@contoso.com, in the Test Mailbox field. Nexla reads that mailbox's Inbox folder to test the credential.
- Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Microsoft Outlook Mail connector tile, then select the credential that will be used to connect to your mailbox, and click Next; or, create a new Microsoft Outlook Mail credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Microsoft Graph mail endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Every endpoint template has a required Mailbox parameter that selects whose mailbox to use. Keep the default, me, to use the mailbox of the account that signed in with OAuth 2.0. With an App-only credential, enter users/ followed by the mailbox address, for example users/support@contoso.com. This also reaches shared mailboxes. To read several mailboxes, create one data source per mailbox.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
Microsoft Outlook Mail data sources can also be manually configured to ingest data from any valid Microsoft Graph mail endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Microsoft Outlook Mail data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Use as a destination
Click the + icon on the Nexset that will be sent to the Microsoft Outlook Mail destination, and select the Send to Destination option from the menu. Select the Microsoft Outlook Mail connector from the list of available destination connectors, then select the credential that will be used to connect to your mailbox, and click Next; or, create a new Microsoft Outlook Mail credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Microsoft Graph mail endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
As with data sources, every endpoint template has a required Mailbox parameter. Keep the default, me, to act on the mailbox of the account that signed in with OAuth 2.0, or enter users/ followed by the mailbox address, for example users/support@contoso.com, with an App-only credential.
Manual configuration
Microsoft Outlook Mail destinations can also be manually configured to send data to any valid Microsoft Graph mail endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The Microsoft Graph mail endpoints expect JSON in the request body. Ensure your Nexset records are mapped to the message structure required by the target endpoint before activating the destination.
Save & activate
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Microsoft Outlook Mail endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Microsoft Outlook Mail endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.