Matrix42 is building support for sending and receiving email in Pro ESM through the Microsoft Graph API, as an alternative to SMTP and IMAP. This article describes how the integration behaves, what its status is, and where it is heading. For registering the application, the platform settings and the task configuration, see Email Integration Using Microsoft GraphAPI (BETA).

Status and timeline

Graph email is a technical preview in 26.2. Use it in test environments only.

The timeline for 27.1 and later is an estimate only. It is not a commitment to deliver any capability in that time. Your existing SMTP and IMAP configuration keeps working, and no end-of-life date has been set for it.

How it works

Receiving emails

The [BETA]GraphApiMailTask scheduled task stores each unread email of the configured mailbox folder as a data card of the Email system template, and it links the email to a data card of the template that you choose. The task looks for the tracking tag in the subject of the email. When the tag matches a data card, the task links the email to that card. When the email has no tag, or no matching card is found, the task creates a new data card in the folder that you configure and fills its subject and body from the email.

An email that fails to import stays in the mailbox, and the task tries it again at the next run. The task imports attachments together with the email. When file type validation for integrations is switched on, the task skips attachments with a file type that is not allowed. This is controlled by the platform setting file.upload.type.validation.integrations.enabled, which is off by default. Setting names and availability can change between versions.

You can create several tasks to read several mailboxes.

Sending emails

When the data card already has received emails, Pro ESM sends the new email as a reply to the latest received email. Otherwise, Pro ESM starts a new email. Pro ESM stores each sent email as a data card that is linked to the data card where the user wrote it, and it shows on that card whether the email was sent or failed. The message queue retries a failed send automatically.

Automated emails

Emails that listeners, workflows and events send still go out over SMTP in 26.2. They do not use Graph.

What is not available in 26.2

The limits of the send form, such as one recipient and no attachments, are listed in the setup article. In addition, the following are not available:

• Automated emails cannot be sent through Graph.
• Emails can be sent from one mailbox only.
• Email message templates are minimal. They do not yet hold sender, recipients, subject text, body text or attachments. See the setup article for details.
• Expressions cannot send email through Graph.
• Graph email is not supported in production environments.

Where this is heading

The plan is to make Graph a complete alternative to SMTP and IMAP in Pro ESM, in stages.

The goal for 27.1 is that the technical building blocks for full email sending and receiving are in place. The areas under consideration are automated emails sent through Graph, sending from more than one mailbox, a more complete manual email experience with more recipient options, attachments and message handling, and better handling of templates and of deleting emails.

These areas describe the direction and not a feature list. Their scope, order and timing can change as the work is assessed in more detail.

After that, the focus moves to making it safe for production environments to migrate, including guidance for moving over existing email configuration. No date has been set for this stage.

Planning currently assumes that the mailboxes used for sending belong to the same Microsoft 365 tenant as the application that is connected to Pro ESM.

How you can prepare

You do not need to change anything in production for 26.2. The following steps help you be ready when production migration becomes possible.

1. Try the preview in a test environment by following the setup article. If something is missing for your use, raise it as an idea in the Matrix42 Idea Portal.
2. Make an inventory of your current email use. List the mailboxes that Pro ESM reads from and sends from today, and the workflows, listeners and scheduled tasks that send email.
3. List the From addresses that you use. Graph sends as real Microsoft 365 mailboxes, so each sender address needs to be a mailbox that the application has permission to send from. Check which of your current sender addresses are real mailboxes and which are only display addresses.
4. Involve your Microsoft 365 administrator. Creating the Entra application, granting permissions, and deciding which mailboxes the application can access are done on your side. Agree who owns these tasks and how mailbox access is limited.
5. Check your mailbox rules. Pro ESM removes incoming emails from the mailbox after import, so make sure no other system or user depends on the same mailbox and folder.

Questions and feedback

If you want to start using the preview, contact your Matrix42 representative. If you have ideas or requirements for email over Graph, raise them in the Matrix42 Idea Portal.