Customers using Office 365 with custom firewall or security policies in place must ensure that the following exceptions are set to allow Crelate’s Office 365 Connection to work.
Crelate’s servers will connect to your organizations Office 365 instance to send emails on behalf of users. The specific permissions our application requests are documented in the Application Authorization Consent Request.
Crelate’s servers connect using the Microsoft Graph API via REST servers over the internet.
Some organizations may have locked down access to Exchange Web Services (EWS) via customer specific policies. If this is the case, please have your administrator verify if there are any policies in place that may block access to Crelate. Administrators of Microsoft Office 365 Exchange instances may use the Exchange Online Management module of PowerShell manage these settings.
Application Level blocking - Ensure that your does not have any global blocks on applications. If there is a block in place, be sure to add the Crelate Application to the Allow List.
Get-OrganizationConfig| select EwsApplicationAccessPolicy, EwsAllowList, EwsBlockList
To learn more, refer here: Get Organization Config
IP Level blocking – Ensure that your organization does not have IP filtering in place. If it does, please contact Crelate Support for a list of IP addresses to add to your Allowed IP List. Note: Our IP addresses are subject to change. Example command:
Set-ClientAccessRule ‘YOURRULENAME’ -ExceptAnyClientIPAddressOrRanges @{add=’CRELATEIP’}
Protocol blocking – Ensure that access to the REST protocol is allowed. Client Access Rules are scoped by protocol (Ex: REST, IMAP4, ExchangeActiveSync, Etc.)
Ensure that any Client Access Rules are properly scoped and that Crelate’s IP addresses are allowed to connect to the REST protocol within your organization.
To learn more, refer here: Set Client Rule Access
What's Next?
With your connection added, learn more about how to send emails from Crelate!