Versions Compared

Version Old Version 3 New Version Current
Changes made by

Girish Reddy

Girish Reddy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Import users, groups, software licenses, organizations (cost center, division) and other attributes from Entra ID to JSM Assets.

Please review instructions here to get started with setting up an Assets import configuration. You can then access OnLink app from the “Manage your apps” menu to further configure and set the field level mapping. Here’s an example configuration:

image-20240322-090943.png

  1. Set a descriptive name for this map

  2. Set source system to Azure AD

  3. Asset Schema is pre-filled. This is the schema in JSM Assets on which you started the configuration.

  4. Select the Object Type within your schema.

  5. Select schedule frequency

  6. Attribute mapping - see below table for more details.

For Azure, we support several custom mapping schemes e.g.

Panel
bgColor#FFFFFF

  1. .

Sample Azure AD Object Schema

image-20240322-091828.pngImage Added

Here’s the associated mapping

key:id=UserID
map:id=Name
map:userPrincipalName=UserPrincipalName
map:displayName=DisplayName
map:companyName=CompanyName
map:department=Department
map:jobTitle=JobTitle
config:export_azure_groups=false
config:export_azure_licenses=false
config:data_limit=100

Here’s a detailed breakdown of each of the mapping items:

Key or Map

Description

key:userPrincipalName=WorkerID

The keyword “key” refers to using userPrincipalName as a unique identifier. This allows OnLink to update the record. WorkerID is a text attribute.

map:userPrincipalName=Email

The userPrincipalName is also mapped to Atlassian Account ID, which is an attribute of type “User”. Here OnLink looksup the Atlassian User object based on userPrincipalName.

map:usageLocation=Usage Location

Maps usageLocation property from Azure to Usage Location. Any field (string, boolean, date) from Azure AD API can be used as the source field. Here’s the list of fields: https://learn.microsoft.com/en-us/graph/api/resources/user?view=graph-rest-1.0#properties

Some common fields are:

  1. companyName

  2. country

  3. department

  4. displayName

  5. employeeHireDate

  6. employeeType

  7. givenName

  8. jobTitle

  9. mailNickname

  10. mobilePhone

  11. officeLocation

  12. preferredName

  13. surname

  14. userPrincipalName

map:CostCenterEmployeeOrg=Department|Name=${CostCenterEmployeeOrg}

- this

This maps employee Cost Center in Azure to Department attribute in

your

Assets schema, where Department is a reference and the lookup happens by name

map:DivisionEmployeeOrg=Division|Name=${DivisionEmployeeOrg}

This maps employee Division in Azure to Division attribute in Assets schema, where

department

Division is a reference and the lookup happens by name

map:EmployeeManager=ManagerObject|
Name

  • config:data_limit=100 set to 100 for testing purposes, max is 1500. Each scheduled job processes a max of 1500 records. OnLink automatically fetches the next set of data in the next scheduled run.

    • WorkerID=${EmployeeManager}

    OnLink has below configuration parameters:

    “EmployeeManager” is a special property that OnLink provides to get user’s manager ID. In this mapping example, ManagerObject is an attribute in your Asset Object type. It’s a self-referencing object i.e., an object attribute that points back to the parent object type.

    image-20240719-164809.pngImage Added

    To map the manager field, the Azure User ID field is used. In this case, this Azure User ID is mapped to WorkerID attribute.

    Note: this is only enabled when you are importing less than 1,000 users at the moment. This can be enabled by setting this property in your mapping attributes: config:expand=manager. Since Azure API does not support filters when exporting managers, we recommend that you create a separate OnLink import job just for managers with below config:

    key:id=WorkerID
    map:EmployeeManager=ManagerObject|UserID=${EmployeeManager}

    config:export_azure_groups=true

    This allows OnLink to pull all Groups assigned to a user. Please note that a pre-defined schema needs to be created exactly like below.

    Schema name is Azure Groups. Three text attributes - Group Display Name, Group Description, Group ID.

    image-20240322-092841.pngImage Added

    OnLink pulls Azure Groups into this schema and maps them to your users schema.

    config:export_azure_licenses=true

    r

    Similar to Groups, this setting allows OnLink to pull all Licenses assigned to a user. Please note that a pre-defined schema needs to be created exactly like below.

    Schema name is Azure Licenses. Three text attributes - License ID, License SKU Part Number, License SKU ID

    image-20240322-093051.pngImage Added

    config:filter=country eq 'United States' (example)

    Optional parameter to add filter to list users; any valid filter expression can be used here

    config:data_limit=100

    Optional parameter to limit the number of users to pull from Azure. This can be used for initial testing.