Import users from Azure Active Directory

Run the appropriate script supplied with your Novus solution to create the required app registration in Azure.

Together with the script, you'll have received information about which rights you must have to perform the required tasks on Azure. If you don’t know if you have those rights, ask your organization’s main Azure administrator to help you.

Our developers haven't had time to create the script yet, but they've created this PDF guide that you can follow until the script is ready:

Azure App Registration for Active Directory User Import

Required Active Directory fields

For Zylinc Novus to be able to import users from Active Directory, the following Active Directory fields must currently not be empty:

• FirstName

• LastName

• DisplayName

This will be changed in a upcoming release of Novus. After that release, the only requirement will be that imported users have a valid e-mail address. Examples: janedoe@example.org (valid e-mail address format), jo hn doe@example.org (not valid)

1. Log in to your Novus Configuration Manager, and, in the User Import section, select Azure Active Directory import.

2. Click Create New.

3. Specify a name for your configuration.

4. Make sure that integration of user data from Azure Active Directory is set to Enable.

5. In Priority, specify a priority for this integration (also called a data provider). The priority is global, so if you have other data providers (for example user import from a CSV file) with a higher or lower priority, the priority will determine how the data providers rank against each other. The highest priority is 1 and the lowest priority is 100.

6. In Synchronization interval in minutes, specify how often Zylinc Novus should synchronize user data with Azure Active Directory. The number of minutes must be at least 360 (that is every 6 hours) and a maximum of 1440 (that is every 24 hours).

   Hours to minutes converter

7. Optionally, specify a Synchronization filter. With a filter, you can determine that only, for example, users from a particular group (for example people who belong to the Management group in Active Directory) should be imported and synchronized.

   You can achieve a great deal of flexibility with such filters, especially because you can set up multiple Azure Active Directory user import configurations in Configuration Manager, which can then use different filers. To learn more, and view examples of filters, see Use filters on Azure Active Directory user import (opens on separate browser tab, so you can use the information together with this).

8. Optionally, specify Tags. With tags, you can add searchable keywords to imported users.

   If required, you can use commas in tags. You don't need to specify people's Active Directory group memberships as tags, those groups are searchable by default.

9. Endpoint feature profile is an upcoming feature for adding licensed functionality, such as calendar integration or mobile presence, to imported users. It's not fully implemented yet.

10. User feature profiles is an upcoming feature for adding licensed user-level functionality, such as the ability to handle callbacks in the Web Agent, to imported users. It's not fully implemented yet.

11. Specify your Azure Tenant ID.

    It’s typically your primary domain name on Azure.

12. In Client ID, paste the application ID from your Azure Active Directory user import app registration.

13. In Client secret, paste the client secret from your Azure Active Directory user import app registration.

14. Click Save.