Versions Compared

Old Version 6

changes.mady.by.user Girish Reddy

Saved on

compared with

New Version 7

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.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 for more details.

Sample Azure AD Object Schema

image-20240322-091828.png

Here’s the associated mapping

key:userPrincipalName=WorkerID
map:userPrincipalName=Atlassian Account ID
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

  • 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

  • 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

    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:CostCenterEmployeeOrg=Department|Name=${CostCenterEmployeeOrg}

    This maps employee Cost Center in Azure to Department attribute in 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 Division is a reference and the lookup happens by name

    EmployeeManager=ManagerObject|Name=${EmployeeManager}

    This maps employee’s manager to Manager Object, which is of type Azure Users. Lookup happens by name in this example but can be changed to Email.

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

    Panel
    bgColor#FFFFFF

    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

    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:data_limit=100

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