Configuring Office 365 SMTP
Last updated
Last updated
Pre-requisites:
Inforiver installation is On-premises and the SMTP environment variable should be set to Office365 as shown in the image below.
You need to have admin privileges in Office 365 as well as be the workspace admin for Inforiver to configure these steps.
Microsoft supports OAuth2.0 client credential flow for application permissions which allows us to authenticate to Azure AD without the need of having an authenticating user in the process. The authentication is entirely based on the tenant ID, client ID and client secret of an application (Inforiver).
Using GRAPH API authentication, Inforiver captures the required user tokens for sending emails.
Inforiver requires the following permissions to be granted in Office 365 as explained below.
Mail.Send: This permission is required to send emails which would be granted when the user configures the Office365 SMTP settings and provides consent.
Mail.ReadWrite: This additional permission is required to send large file attachments, which would be granted if the user enables the large file attachment settings.
Let us see the steps to configure the above settings.
Go to the Tenant Settings page by clicking on the Settings menu on the left side of the window. (Note: Only Workspace Admin has access to the Tenant Settings page of Inforiver).
Enter the required From Email Address. A mail box should be configured for the user or for the group that is specified in the From Email Address. (They should have a shared mail box access).
The email entered is form-validated by the app, after which the Enable button is enabled on the screen.
Click Enable. This opens the Microsoft 365 consent screen where the user has to provide the consent. Admin privileges are required to provide consent.
After providing the consent, Inforiver is granted the Mail.Send permission.
Since we have provided a pre-configured From Email Address in MS Office SMTP settings who is going to be the sole sender, Enable Single Sender Identity option will be greyed out and locked for toggle.
The tenant settings table will save the encrypted user tokens after a successful login.
Click Reset to reset the SMTP user tokens and settings.
After reset, the configured email address is removed. The user can then configure it again if required by following the above steps.
Go to the Tenant Settings page.
Reset SMTP user tokens as explained above.
Enter the desired email ID in the From Email Address and provide the consent in the Microsoft 365 consent screen.
The new Email Address (sender) is updated successfully.
You can update the From Email Address without resetting the SMTP settings as explained below:
Go to the Tenant Settings page.
Check if the Office SMTP is configured. If it is configured, please enter a valid From Email Address that is to be updated.
Click Save button.
This opens the consent popup screen.
After providing the consent, the new From Email address is updated.
To enable large file attachments, toggle the button Enable large file attachments and click Save.
Note: If the From Email Address is not configured already, please configure it by following the steps listed here. While configuring, you can toggle the large attachments button before clicking Enable.
After clicking Save (or Enable, in case you're configuring the email now) the consent screen appears.
By providing the consent, Inforiver is granted both the Mail.Send and Mail.ReadWrite permissions.
The tenant settings table will save the user tokens (encrypted) after a successful login.
Note: The toggle button to enable/disable large file attachments is locked and greyed out after authorizing it.
The acquired tokens can be deleted by a Reset and then you can disable the large file attachments if required.
You can create an empty group email and delegate the complete access of the group email to any org email user using the Send As permission. This configuration needs to be done in the portal for groups.
Once configured, the From Email Address will be the group email ID of the empty distribution list.
But internally, it uses the graph access tokens of the delegated user.
Note: The delegated user should have configured the SMTP settings and provided consent.