Better Microsoft 365 integration and alternative connection outage notifications

Created by Mike Harrison
Oct 14, 2021

Microsoft 365 connections improved

Newly created Message Source and Message Outbound connections will now use the Microsoft Graph API under the hood. By using Graph API, you can now integrate JEMHC with Microsoft 365 using per-account user consent, rather than having to grant org-level admin consent like the older EWS API type connections required.

Existing EWS OAuth connections will continue to work for now but will be removed at a later date. We recommend recreating your connections with the “Sign in with Microsoft” button to make use of the new OAuth connection type.

For Azure administrators information, JEMHC will request consent for the following permissions on creation of new Microsoft 365 connections:

  • Mail.ReadWrite (for Message Sources)

  • Mail.Send (for Message Outbounds)

  • offline_access (Maintain access to data you have given it access to)

  • User.Read (Sign in and read user profile)

Alternative connection outage notifications

When an email notification connection is detected as being offline, JEMHC sends notifications via email to your configured “System Notification addresses”.

Now, non-email notification connections can also be selected to be used for such notifications. For example, you can now configure Slack notifications to be sent when your inbound mailbox connection fails. Great!