Integrate to Office 365 using Exchange Web Services

Owned by Fernando Boucquez (Deactivated)
Last updated: Apr 06, 2023 by Ryan Clifton
2 min read

Office 365 connectivity

Deprecation of basic authentication

Microsoft has deprecated the basic authentication mechanism shown on this page. We recommend that users migrate to the newer connection type which uses OAuth 2.0. See for more information.

Although Office 365 can be integrated to JEMHC through POP3, IMAP and SMTP, JEMH Cloud also supports inbound messaging and outbound notifications via Microsoft's Exchange Web Service.

To use EWS, just select the type Office 365 EWS when creating Message Source or Message Outbound configurations.

The below requires that you are using at least the Microsoft 365 Business Standard plan.

Message Source

  1. Go to Messaging → Message Sources → Create

  2. Complete the form selecting the Type Office 365 EWS. 


  3. When saving, JEMHC will test how many messages are ready to be processed.

You can now use the EWS Message Source in Message Handlers to poll messages like any other Message Source.

Message Outbound

  1. Go to Messaging → Message Outbounds → Create.

  2. Complete the form selecting the Type Office 365 EWS. 

  3. When saving, JEMHC will send a test email to the To Email address.


The EWS Message Outbound can be used to send email though Email Notification Mappings, Post Functions Notifications and Ad-Hoc Notifications.

JEMHC uses the autodiscover feature to detect the EWS server URL.

Check out Office 365 section in Common Problems.

 

User Impersonation (for mail retrieval from several/many mailboxes)

The following doc has been referred by a customer using JEMHC + EWS with an on premesis Exchange 2016 server and “User Impersonation”. It enables a ‘main’ account to retrieve mail from ‘many’ mailboxes, not unlike Aliases. It may work with cloud o365, as yet this is unverified/tested, here for information only! We hope it would be Graph compatible, as yet unknown.