Outlook Mail Output

The Outlook Mail module integrates directly with Office 365 to send emails.

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.

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 Lasernet 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.

• Sign you in and read your profile.

The Remove Authorization button deletes the obtained authorization.

Note

Obtain Authorization and Remove Authorization are available only when you select User authentication.

User Authentication Properties

Authenticate as an Application

Authentication as an application for Outlook Mail communication requires that:

• Lasernet is registered as an app by an Entra ID admin.

• The Entra ID admin must provide a ClientID and Client Secret for the module to use to sign in.

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

Note

If the client ID and client secret change in the future, repeat the step above and then commit and deploy the Lasernet 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 attempts to use those credentials to obtain a new access token.

Application Authentication Properties

Refresh Access Token

If Lasernet 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 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 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 configuration.

Application Authentication

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

Properties

Headers

Optionally, you can add custom MIME headers to the emails sent by an Outlook Mail Output module. Some possible uses for custom headers are to enable the sending organization to troubleshoot delivery issues by examining unique codes in the header data in bounced emails, and to enable enhanced workflow visibility by enabling the organization to track emails back to their originating Lasernet process or job.

You can add up to five custom headers.

The Outlook Mail Output module will add the configured custom headers to outgoing email and give each header the specified value. A custom header’s Name must start with X- or x-; for example, x-Invoice-Number.

You can specify a static value for a header; for example, Lasernet Mail. Else you can use JobInfo substitution if you want header values to be dynamic. For example, you could enter a JobInfo reference (like #InvoiceNumber#) as the header’s Value.

If a mail is bounced back to the sender and is read by Lasernet’s Outlook Mail Input module, Lasernet creates JobInfos that have names and values corresponding to the custom headers in the bounced email.