By setting up a custom email domain, Sana notification emails will be sent from your company's email address instead of from Sana. This makes the notification emails look more professional and consistent with your brand, making them instantly recognizable to your recipients. This article will show you how to set it up if Microsoft is your email provider.

By using your domain and SMTP server, you can ensure compliance with legal and industry regulations related to email sending, such as GDPR and CAN-SPAM Act. Emails sent from your domain also enhances brand consistency and recognition.

You will need to first provide us with your tenant ID along with the email that you would like to use. You can view your tenant ID by going to your Entra Portal > Identity > Overview. Once you have provided the credentials to us, you will now see a new option in the Sana platform when you go to Settings > Notifications called Authorize.

Click on the Authorize button in the Notifications section and you should be redirected to the the consent screen for the Sana Entra app, used to send emails from Exchange Online:

Once you authorize, you will get an error message along with a redirect URI. Kindly provide us the redirect URI link that's missing as this will need to be added from our Microsoft application page.

After giving admin consent, you can now navigate to the Entra Portal. Under Identity > Applications > Enterprise Applications, find the Sana Exchange Oauth application (Application ID: 44de40b6-4ac2-42f1-a9da-f26d811f9e23).

To use the New-ServicePrincipal cmdlet, install ExchangeOnlineManagement and connect to your tenant as shown in the following snippet:

Registration of an Microsoft Entra application's service principal in Exchange is shown in the following example:

The tenant admin can find the service principal identifiers referenced above in your Entra AD application's enterprise application instance on the tenant. You can find the list of the enterprise application instances on the tenant in the Enterprise applications blade in the Microsoft Entra view in Azure Portal.

The following example shows how to give your application's service principal access to one mailbox:

Different IDs are used during creation of the Exchange service principal and also later when granting mailbox permissions. The following example may help you to use the correct ID for the different stages. This example uses Microsoft Entra cmdlets; so, you'll need to install the Microsoft Entra PowerShell module, if you haven't already. For more information, see Install Microsoft Entra PowerShell for Graph.

Your Microsoft Entra application can now access the allowed mailboxes via the SMTP, POP, or IMAP protocols using the OAuth 2.0 client credentials grant flow. For more information, see the instructions in Permissions and consent in the Microsoft identity platform.

Bad example output:

New-ServicePrincipal: The term 'New-ServicePrincipal' is not recognized as a name of a cmdlet, function, script file, or executable program.

Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Obtaining permission requirements