Microsoft 365 Connector

Usage

You can use a Microsoft 365 connector to fetch e-mails or to send e-mails using OAuth2 client credential flow.

Connector types

Input Connector

Fetches provided number of e-mails. The Scheduler is activated for this connector, by default.
Output Connector

Send e-mails without attachments.

Make sure that the Office365 server can be reached from the computer where the INUBIT Process Engine is installed.

Also check, whether your application is registered with Azure Active Directory with proper graph application permission, ask your Microsoft Azure administrator for the application registration with required permission.

Register your application with Azure AD

Refer to https://docs.microsoft.com/en-us/power-apps/developer/data-platform/walkthrough-register-app-azure-active-directory

Assigning required Application permissions:

An application permission is granted to an application by an organization’s administrator, and can be used only to access data owned by that organization and its employees. For example, below are the Microsoft Graph exposed application permissions for fetching and sending mails with Microsoft 365 Connector.

Mail.Read: Read mail in all mailboxes
Mail.ReadWrite: Read and write mail in all mailboxes
Mail.Send: Send mail as any user
Director.Read.All: Read directory data

Dialog Authorization Panel

(Input Connector/Output Connector)

In this dialog, you specify the registered application details with Azure Active Directory.

Use OAuth2 Authorization

Grant Type

Client Credentials. Currently grant type for OAuth2 authorization is supported.
Tenant GUID

A Global Unique Identifier (GUID) for your Microsoft 365 tenant.
Client ID

Client identifier issued to the client during the application registration process.
Client secret

Client secret issued to the client during the application registration process.
Scopes of access request

Set the scope of the access request; multiple space-delimited constraints are possible.
Username

Name/E-mail of the user to be authorized.

Connection test

Click on Test connection for testing whether the connection can be successfully established using your configuration.

Dialog Sender Configuration

(Output Connector)

Message
- From: Sender address.
- To: Recipient address. Separate multiple recipient addresses with semicolon.
- Cc: Additional recipient addresses; separate recipient addresses with semicolon.
- Bcc: Recipient addresses that are not visible to To and Cc recipients. Separate multiple recipient addresses with semicolon.
- Reply to: Fill in this field if the sender address is not the address to which you want recipients to reply to.
- Subject: Specify the subject of the e-mail.
Delivery Receipt
- Enable DSN : This option will enable the user to get a delivery receipt for each recipient.
- Include Attachment
  
  To send the input message as an attachment to an e-mail (beta feature).

Dialog Receiver Configuration

(Input Connector)

Message
- Message Box: Read e-mails from the following sub-folder of a mailbox (default: INBOX).
- Number Of Mails: Mention the number of mails you wish to receive as opposed to receiving all mails in the inbox.
- Include Attachment: This field is used to set output message as XML along with attachment data (beta feature).
- IBIS Raw MIME: Set output data as IBIS Raw MIME.
  
  The MIME specification already includes e-mails with attachment data content in it.
Delete after reading
- Delete: If activated, the messages are copied from the mail server to the INUBIT Process Engine and are then deleted from the mail server.
Copy or Move after reading
- Copy: If activated, e-mails are copied to the target directory and kept in the inbox.
- Move: If activated, e-mails are copied to the target directory and removed from the inbox.
- Directory: Select the target directory to which e-mails are copied or moved.
Mark as read
- Leave all retrieved messages in the state "unread": Activate this checkbox to mark messages as "unread".