Microsoft Azure Mailbox Configuration 

Microsoft has announced the deprecation of basic SMTP and IMAP authentication using a simple username and password. To continue using an email account hosted in Azure in the Navigator system, proper configuration on both Navigator and Azure sides is required. 

Navigator Configuration 

The mailbox configuration in Navigator has not changed significantly. Two new fields, Azure Application ClientID and Azure Application TennantID, have been added. To correctly configure the Azure mailbox, the following information is required: 

• Type: SMTP/IMAP 

• Login: Username in Azure service. This user’s mailbox will be accessed by Navigator, and all emails will be sent through their account. 

• Password: User password in Azure service. 

• SMTP Server: SMTP server address. 

• SMTP Port: Port on the server where the SMTP service is running. 

• IMAP Server: IMAP server address. 

• IMAP Port: Port where the IMAP service is running. 

• Use TLS: Enabling this option creates a secure, encrypted connection with the mail server.
  Note: The server must have encryption options enabled for this method to work. 

• Azure Application ClientID: A unique code generated in the Azure service configuration, associated with the account to which you are connecting. 

• Azure Application TennantID: A unique code generated in the Azure service configuration, associated with the organization within which the account is set up. 

Azure Configuration 

Microsoft has introduced the Microsoft Identity Platform, which is responsible for authenticating users within the system. This will be the only method to access Microsoft services, including IMAP and SMTP servers. To use Azure features in Navigator, you must configure the identity platform for integration with Navigator. 

Prerequisites 

• An active Azure subscription. 

• Permissions to manage applications in Azure Active Directory. The following permissions are required: 

• Application Administrator 

• Cloud Application Administrator 

• Application Developer 

Registering the Application 

On the main screen, you can select Manage Microsoft Entra ID:

and then select App Registration from the right-side menu.

On the next screen, you can manage the existing application or create a new entry:

If you are registering a new application, follow the steps below. When you add new privileges skip to step Additional Permissions.

Any application, including Navigator, that will work with Azure must be registered. 

Application Registration Process: 

1. Sign in to the Azure portal with minimum required permissions.
2. Find the appropriate subscription. If you have access to multiple subscriptions, use the Directories & Subscriptions filter.
3. Select Microsoft Entra ID.
4. In the Manage section, choose App registrations > New registration.
5. Enter a name for the application you are registering. The name can be anything.
6. Choose who can use the application (account type). The following options are available:
   1. Accounts in this organizational directory only: Only users in your subscription can use the application.
   2. Accounts in any organizational directory: Users from any subscription can use the application. Typically chosen by software developers who want to share their app in a SaaS model.
   3. Accounts in any organizational directory and personal Microsoft accounts: Similar to the previous option but allows access to users with personal Microsoft accounts.
   4. Personal Microsoft accounts: Only users with individual Microsoft accounts can access the application.

To integrate Azure email with Navigator, select the first option.

After completing the form, select Register. When the process is complete, you will see a summary page with essential details.

In the summary, you will find the fields needed in Navigator: Application (Client) ID and Directory (Tenant) ID. 

Additional Permissions 

To use the mailbox in Azure, additional permissions are required to allow sending and receiving emails. 

API Permissions 

To configure the permissions, follow these steps: 

1. Enable SMTP and IMAP protocol permissions by going to API Permissions in the application configuration, then click Add and select SMTP and IMAP as needed. 
2. You can add both protocols or just one depending on your needs. 

Administrator privileges are required. Without these permissions and confirmation, the Navigator system will not be able to send mail. A successful configuration is indicated by green checkboxes next to the interface name. 

Authentication 

In the Authentication tab, go to Advanced Settings > Allow public client flow and set it to Yes. 

This option is disabled by default. Without enabling it, the system will not integrate properly with Azure email.