Page Comparison

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:

Set a descriptive name for this map
Set source system to Azure AD
Asset Schema is pre-filled. This is the schema in JSM Assets on which you started the configuration.
Select the Object Type within your schema.
Select schedule frequency
Attribute mapping - see below table for more details.

Sample Azure AD Object Schema

Image Added

Here’s the associated mapping

key:userPrincipalName=WorkerID
map:userPrincipalName=Email
map:displayName=Name
map:CostCenterEmployeeOrg=Department|Name=${CostCenterEmployeeOrg}
map:DivisionEmployeeOrg=Division|Name=${DivisionEmployeeOrg}
map:EmployeeManager=Manager Name|Name=${EmployeeManager}
map:usageLocation=Usage Location
config:export_azure_groups=true
config:export_azure_licenses=true

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
`map:userPrincipalName=Email`

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

Panel

bgColor	#FFFFFF

CostCenterEmployeeOrg=Department|Name=${CostCenterEmployeeOrg}- this maps employee Cost Center in Azure to Department attribute in your schema, where department is a reference and the lookup happens by name
EmployeeManager=ManagerObject|Name=${EmployeeManager}
OnLink has below configuration parameters:
1. 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.
2. config:export_azure_groups=true
3. config:export_azure_licenses=true

r

Versions Compared

Old Version 3

New Version 4

Key