Commissioning Microsoft Entra ID personnel data import

This interface can retrieve personnel data from Microsoft Entra ID. The data is imported into the personnel list using the existing personnel data import interface.

Prerequisite

• A license for the personnel data import interface is available

• You have administrative rights in both your Office account and the eTASK.FM portal

Procedure

1. Log in to https://portal.azure.com using your Microsoft credentials.

2. Click on Microsoft Entra ID.

3. Click on App Registrations.

4. Click New registration.

5. Set the authentication type to Single Tenant.

6. A secret must be created for the interface. To do this, click the New Secret Client Key button

7. To configure the API permissions, set the “User.Read.All” permission in Microsoft Graph as an application.

Procedure in the FM Portal

Path to the starting point: Control Panel - Portal Options - Interfaces - Interface Configuration - Azure AD

The basic configuration is already provided with the “5255” interface plugin. Among other things, a large part of the mapping is already available here. However, this must be adapted to the customer’s existing structure. The personnel code or personnel number is fixed as the primary key for data synchronization.

1. For the general configuration of the Entra ID interface, the value for AZURETENTANTID (directory ID) from Azure must be specified in the system configuration.

2. The plugin has already created a record here. Open the corresponding record. Enter the value for AZURETENTANTID (directory ID), the client ID from Azure, and the secret.

3. Under "Mapping," configure the fields to be retrieved from Azure AD. The interface plugin already imports most of the standard fields into the portal.

Note: Additional fields cannot currently be created manually (this is currently done via the customer-specific plugin).

Note: Additionally, the mapping to the fields available in eTASK is performed in the mapping section. This is done within the respective records. The extensionAttributes are a minor exception here. These are further broken down within the record into extensionAttribute1 through 15.

4. When retrieving data from Azure AD, you can specify filters. These filters are defined by Azure AD and can be configured via the Import Filter field. For more information on the available filters: Filter Options [external link]

5. The stored configuration can be tested here under Import Test.

Note: However, the configuration of IF_SPALTE_T must be complete for this (see point 6).

Note: The interface plugin already includes the default configuration in the IF_SPALTE_T table.

6. If additional fields are required for mapping values from Azure to eTASK, or if fields from eTASK that have not yet been configured are needed, these must be configured in IF_SPALTE_T. This configuration can be found under Control Panel - Portal Options - Interfaces - Interface Configuration - Personnel Data Import - IF_SPALTE_T Configuration.

Note: However, this configuration requires knowledge of our database structure, as the data types (varchar, int, bit, etc.) must be specified in this configuration.

7. Under Control Panel - Portal Options - Portal Administration - Timer Jobs - Job Management, enable the timer job “Import and Update Azure AD Personnel”.

8. Set the Azure AD profile to Active.