Mail server
Elimity Insights servers send out emails for multiple reasons:
to invite new user accounts
to update subscribed users when stored query results change
to warn subscribed connector admins when imports fail
to request access reviews
to log change requests in your IT ticketing system
For SaaS customers we perform the setup and maintenance of mail servers behind the scenes. These installation instructions are mainly useful for on-prem deployments.
From an Elimity Insights server's point of view, the only requirement is an SMTP server to accept the outgoing emails. In practice this means you can probably just use a mail server that is already available in your organization. We currently support the following authentication options:
None: Elimity Insights will simply send mails to your SMTP server without prior authentication.
Direct: Elimity Insights will try a variety of 'direct' SMTP authentication options (e.g.
PLAIN,LOGIN,CRAM-MD5, ...) using a configured username and password.OAuth2: Elimity Insights will exchange configured client credentials for an access token and use it together with a configured username for
XOAUTH2authentication at your SMTP server.
For example, many of our customers use Exchange Online as their mail server for Elimity Insights. Setting this up correctly is not easy though, so we highly recommend carefully reading through the official documentation from Microsoft. Some points that require extra attention:
the OAuth2 token URL should have the following format:
https://login.microsoftonline.com/{tenantId}/oauth2/v2.0/tokenthe OAuth2 scope should be
https://outlook.office365.com/.defaultthe mailbox you want to send emails from should have a license
you should grant your app registration full access to this mailbox using PowerShell
you should also grant the necessary API permission to your app registration:
'APIs my organization uses'
search for 'Office 365 Exchange Online'
'Application permissions'
'SMTP.SendAsApp'
you should grant admin consent for this permission
Last updated