AZURE configuration

AZURE configuration #

Microsoft has introduced a new service, the Microsoft Identity Platform, which is responsible for authenticating users on the system. This will be the only way to access Microsoft services. If you want to use Azure elements in Navigator365 then you will need to configure the identity platform for integration with Navigator365.

Basic requirements #

• Azure account with an active subscription
• Permissions to manage applications in Azure Active Directory. It is necessary to have one of the following permissions:
  • Application administrator
  • Cloud application administrator
  • Application Developer

Register an application #

Any application that is to work with Azure, including Navigator365, must be registered with it.

Application registration is as follows:

1. Log in to the Azure portal. Remember the minimum permissions.
2. Find the relevant subscription. If you have access to multiple subscriptions you can use the directories & subscriptions filter.
3. Select Azure Active Directory.
4. Under Manage, select App registration > New registration.
5. Enter a name for the application you are registering. The name can be anything you want.
6. Select who can use the application (supported account types). You can choose from the following options:
   1. Accounts in this organizational directory only – Only users with your subscription will be able to use the app.
   2. Accounts in any organizational directory – Allows users of any subscription to use the application. This option is more likely to be used by software developers who want to make their applications available in the SAAS model.
   3. Accounts in any organizational directory and personal Microsoft accounts – This option is similar to the previous one, however, it also allows people with personal Microsoft accounts to access the application.
   4. Personal Microsoft accounts only – Allows individuals with individual Microsoft accounts to access the application. For integration with Navigator365, select the first option.
7. Leave the Redirect URL field blank for now. We will configure it later.
8. Once you have completed the form, select Register. Once the system has been completed, a registration summary page will be displayed:

In the summary, you will find the relevant information that needs to be transferred to Navigator365. This field is the Application (client) ID.

Client secret #

The next parameter to be configured on the Azure platform is the secret key (Client secrets). Once the key (Secret ID) has been generated, it needs to be copied into Navigator365.

API permissions #

For authentication to work properly, you still need to add permissions to the APIs (API permissions). The minimum permissions required by the interface are to log in and read the user profile (User.Read) and to read the data activity in the organization (ActivityFeed.Read).

Authentication #

In the Authentication tab, we need to add redirect URLs to our application. An example entry is shown in the following screenshot. The URL for Navigator365 will be https://mycompany.navigator365.com/Login.aspx.

Make sure to enter all URLs that will be used with Navigator365.

Additionally, look for the Advanced settings > Allow public client flows option and tick it to Yes.