Office 365 connectivity
Microsoft has deprecated basic authentication (used here) existing customer are still able to use basicAuth, new customer must use oAuth, see Integrate to Office365/EWS using OAuth
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.
Message Source
Go to Messaging → Message Sources → Create
Complete the form selecting the Type Office 365 EWS.
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
Go to Messaging → Message Outbounds → Create.
Complete the form selecting the Type Office 365 EWS.
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.
Errors: 550 5.7.501 Access denied, spam abuse detected
If the emails JEMHC sends bounce (SMTP or Office 365 EWS) back to the inbox with the following messages
Contact Microsoft Exchange Support explaining the error and asking to whitelist your Office 365 domain.
We have used http://answers.microsoft.com/ and the following thread http://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook/remote-server-returned-550-57501-access-denied/23b2794d-ddc2-4e4d-a4b7-ee1f136a300a
Waiting for an answer!
Related articles
Go to Messaging