Versions Compared

Old Version 1

changes.mady.by.user Girish Reddy

Saved on

compared with

New Version 2

changes.mady.by.user Girish Reddy

Saved on

Key

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

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.pngImage Added

  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. 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

  2. EmployeeManager=ManagerObject|Name=${EmployeeManager}

  4. 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