Admin Configuration

Admin Configuration

1. Import Status

You can view the current status of an import here and cancel it if needed.

2. Import History

This section displays the import history, including details such as:

  • Status

  • Triggered By

  • Result

  • Type

  • Start Time

  • End Time

  • Duration

You can also review detailed statistics of objects and export them to an Excel file for further analysis or chart creation.

3. Object Types

Under the Admin tab, you can select the Object Types you wish to import. Update these settings and enable or disable any Object Types that are not relevant to your organization’s use cases.

4. User Attributes

The Attributes section lets you choose which User properties to import. Disable any attributes that are unnecessary for your implementation.

5. Group Attributes

We've recently added an option to import group owners. Select this option if you want group owners to be included in the import. Please note that some group filters may not work with this setting. If you want group owners to be imported you have to enable it as some of the group filters won’t work after this is enabled.

Screenshot 2025-10-13 at 11.34.05.png

 

6. Directory Extension Attributes (Beta)

We've recently added an option to import directory extensions. Directory extensions provide developers with a strongly typed, discoverable and filterable extension experience for directory objects.

Directory extensions are first registered on an application through the Create extensionProperty operation and must be explicitly targeted to specific and supported directory objects. After a user or an admin has consented to the application in the tenant, the extension properties become immediately accessible in the tenant. All authorized applications in the tenant can read and write data on any extension properties defined on an instance of the target directory object.

The Entra ID importer allows you to map directory extension attributes from your Azure AD applications to predefined fields in the User object schema.

How it Works

  • 20 Pre-defined Extension Attribute Slots: The User object schema includes 20 dedicated directory extension attribute fields (directoryExtensionAttribute1 through directoryExtensionAttribute20)

  • Application Selection: The system retrieves all Azure AD applications in your tenant using the Microsoft Graph API endpoint: applications?$select=id,displayName,appId

  • Extension Property Discovery: For each selected application, the system fetches available extension properties using: applications/{appId}/extensionProperties

  • Attribute Mapping: You can map any extension property from your applications to one of the 20 available slots. These mappings are stored securely and included in user data imports.

  • Dynamic Import: During user imports, the mapped extension attributes are automatically included in the Microsoft Graph API query alongside standard user attributes.

Configuration Steps

  1. Navigate to AdminDirectory Extension Attributes (Beta)

  2. Click Edit Extension Attributes to reveal the configuration form

  3. For each attribute slot (1-20):

    • Click Select to open the attribute picker modal

    • Choose an application from the dropdown

    • Select the specific extension attribute from that application

    • The attribute name will populate automatically

  4. Click Save Attributes to store your mappings

Technical Details

  • Storage: Extension attribute mappings are stored in the DirectoryCustomAttributes secret storage

  • API Integration: Extension attributes are appended to the user query using the $select parameter

  • Schema Mapping: Each attribute slot maps to a corresponding field in the JSM Assets User object

  • Empty Values: Only non-empty attribute values are included in the final import

In case you currently have an earlier version than 4.19.0, we highly recommend upgrading to the latest version.