---
title: "Outlook Mail Input"
slug: "outlook-mail"
description: "Information about the Outlook Mail Input module."
updated: 2026-08-28T07:30:20Z
published: 2026-08-28T07:30:20Z
canonical: "kb.lasernetgroup.com/outlook-mail"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Outlook Mail Input

**Applies to:** Lasernet Core 11

The Outlook Mail module integrates directly with Office 365 to retrieve emails. It uses the Microsoft Graph API to access Exchange Online data.

To set up the module, follow this process:

1. [Configure the module’s authentication](/v1/docs/outlook-mail#configure-authentication).
2. [Provide values for the module’s other properties](/v1/docs/outlook-mail#other-module-properties).

## Configure Authentication

> [!NOTE]
> Note
> 
> Lasernet Core 11.2 and later do not support user authentication.

Refer to the information for the version of Lasernet Core that you are using.

**Lasernet Core 11.0 and 11.1**

### Select Authentication Type

Select which type of authentication the module will use:

- **User:** The module authenticates as a user.
- **Application:** The module authenticates as an application registered in Entra ID.

![The Setup tab of an Outlook Mail input module.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/outlook%20mail%20input.png)

#### Authenticate as a User

Set **Authentication** to **User**, then click **Obtain Authorization** to access the account for your organization and to autofill the **Display name** and **E-mail** fields.

The Outlook Mail module will obtain authorization to:

- Maintain access to data to which you have granted access.
- Configure individual permission to send mail on behalf of yourself.
- Configure API permission to send mail on behalf of others.
- Sign you in and read your profile.

The **Remove Authorization** button deletes the obtained authorization.

> [!NOTE]
> Note
> 
> **Obtain Authorization** and **Remove Authorization** are available only when you select **User** authentication.

**User Authentication Properties**

| **Display name** | Display name for the account (click **Obtain Authorization** to autofill this field). |
| --- | --- |
| **E-mail** | E-mail address for the account (click **Obtain Authorization** to autofill this field). |
| **Shared Mailbox** | To use a shared mailbox, insert a UserID, UserPrincipalName or an email address. |

#### Authenticate as an Application

Application authentication for Outlook Mail communication requires that:

- Lasernet Core is registered as an app by an Entra ID admin.
- In Entra ID, the app has the `Mail.ReadWrite` permission.
- The Entra ID admin must provide a ClientID and Client Secret for the module to use to sign in.

> [!WARNING]
> Important
> 
> Before implementing application authentication for this module, see [Understand the Security Implications of Application Authentication for Outlook Mail, OneDrive, and SharePoint Modules](/v1/docs/security-implications-application-authentication-outlook-onedrive-sharepoint). Although that article primarily applies to Lasernet Core 11.2 and later, the *Delegated vs. Application Authentication*, *Permissions Required by Each Module*, and *Reducing the Scope of Access* sections also apply to Lasernet Core 11.0 and 11.1.

Set **Authentication** to **Application**, enter **Client ID** and **Client secret** (and any other necessary settings), then click **Refresh Access Token**.

> [!NOTE]
> Note
> 
> If the client ID and client secret change in the future, repeat the step above and then commit and deploy the Lasernet Core configuration. Doing this ensures that the module remains authenticated.
> 
> 
> 
> At any time, you can click **Refresh Access Token** to test that the currently provided credentials are valid. When you click the button, Lasernet Developer attempts to use those credentials to obtain a new access token.

**Application Authentication Properties**

| **Tenant Domain** | Enter the relevant tenant domain. |
| --- | --- |
| **Client ID** | The Entra ID admin must provide a client ID for the module to use for authentication. |
| **Client Secret** | The Entra ID admin must provide a client secret for the module to use for authentication. |
| **Mailbox** | Specify the mailbox to access (as a UserId, UserPrincipalName, or mail address) |

### Refresh Access Token

If Lasernet Core experiences issues connecting to Outlook Mail, there might be a problem with its current security tokens. In some cases, the **Refresh Access Token** button can resolve connection issues.

Connection issues can occur for a number of reasons, including:

- More than 90 days of inactivity (user authentication).
- The user changed their password (user authentication).
- Permission or security changes to the user (user authentication).
- Revocation of permissions (user authentication or application authentication).

If Lasernet Core experiences connection issues, try the following steps (depending on the authentication method used).

#### User Authentication

Click **Refresh Access Token** to obtain new tokens, then commit and deploy the Lasernet Core configuration.

If doing this does not resolve the issue, click **Remove Authorization** to remove the currently stored security tokens, then click **Obtain Authorization** to reauthenticate using the user account (which will also refresh the security tokens). Then, commit and deploy the Lasernet Core configuration.

#### Application Authentication

Click **Refresh Access Token** to obtain new tokens, then commit and deploy the Lasernet Core configuration.

**Lasernet Core 11.2 and later**

Application authentication for Outlook Mail communication requires that:

- Lasernet Core is registered as an app by an Entra ID admin.
- In Entra ID, the app has the `Mail.ReadWrite` permission.
- The Entra ID admin must provide a ClientID and Client Secret for the module to use to sign in.

> [!WARNING]
> Important
> 
> Before implementing application authentication for this module, see [Understand the Security Implications of Application Authentication for Outlook Mail, OneDrive, and SharePoint Modules](/v1/docs/security-implications-application-authentication-outlook-onedrive-sharepoint).

Enter **Client ID** and **Client secret** (and complete any other necessary settings such as **Tenant Domain** and **Mailbox**), then click **Refresh Access Token**.

![The Setup tab of an Outlook Mail input module.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/outlook%20mail%20input(1).png)

> [!NOTE]
> Note
> 
> If the client ID and client secret change in the future, repeat the step above and then commit and deploy the Lasernet Core configuration. Doing this ensures that the module remains authenticated.
> 
> 
> 
> At any time, you can click **Refresh Access Token** to test that the currently provided credentials are valid. When you click the button, Lasernet Developer attempts to use those credentials to obtain a new access token.

### Application Authentication Properties

| **Tenant Domain** | Enter the relevant tenant domain. |
| --- | --- |
| **Client ID** | The Entra ID admin must provide a client ID for the module to use for authentication. |
| **Client Secret** | The Entra ID admin must provide a client secret for the module to use for authentication. |
| **Mailbox** | Specify the mailbox to access (as a UserId, UserPrincipalName, or email address) |

## Provide Values for Other Module Properties

Use the following information to complete the module configuration.

| **Scan Folder** | Folder that emails are read from. If scanning a subfolder of the Inbox, the syntax is **Inbox\Test** |
| --- | --- |
| **After processing** | Specifies what happens to an email after this module processes it: - **Mark as Read** in the scan folder. - **Move** the email to the folder specified by **Processed Mail Folder**. - **Delete** the email from the scan folder. |
| **Processed Mail Folder** | Specify the destination folder for emails that this module moves after processing. |
| **Process Read Mails** | Select to process incoming mails that are marked as read. |
| **Create Job for mail body** | Select to create a job from the email body, if no attachment is available. |

## JobInfos

When an email is received, a job is created for each attachment; the job’s JobData is the attachment. The following JobInfos are set:

| **InputAttachmentCount** | Total number of attachments included in the incoming email. |
| --- | --- |
| **InputAttachmentNumber** | Handling attachment number for the incoming email. |
| **InputBody** | The body of the mail. |
| **InputFilename** | The filename of the attachment. |
| **InputFromEmail** | The email address of the sender. |
| **InputFromName** | The display name of the sender. |
| **InputHeaderFieldName** and **InputHeaderFieldValue** | A pair of JobInfo lists that contain the names and values of the custom mail headers received by this module. Each header’s name is an item in the InputHeaderFieldName JobInfo list. That header’s value is the corresponding item in the InputHeaderFieldValue list. For example, suppose that the email has an X-MS-Has-Attach header whose value is Yes. If InputHeaderFieldName[5] contains X-MS-Has-Attach, InputHeaderFieldValue[5] contains Yes. |
| **InputMessageID** | Unique identifier for the incoming mail. |
| **InputMimeType** | The mimetype of the attachment. |
| **InputReplyTo** | The “reply to” address of the sender for the incoming email. |
| **InputSubject** | The subject of the mail. |