Entra ID (Azure AD) to JSM Assets
Import Entra ID users, groups, licenses, and attributes into JSM Assets
Use OnLink to import Microsoft Entra ID user data into Jira Service Management Assets, including users, groups, software licenses, organizational attributes such as cost center and division, and other supported Microsoft Graph user properties.
Overview
This guide explains how to configure an OnLink Assets import from Entra ID, map Microsoft Graph fields to Assets attributes, and enable optional exports for groups, licenses, manager relationships, filters, and sign-in activity. The configuration uses simple mapping statements such as key:, map:, and config: entries.
Prerequisites
A Assets schema and object type for imported users.
OnLink installed and available from Manage your apps.
An Entra ID application connection configured for OnLink.
Required Microsoft Graph permissions for the data you plan to import. Sign-in activity requires
AuditLog.Read.All.For setup steps, review the OnLink Assets import setup instructions here.
Setup overview
Configuration screen
Open the OnLink app from Manage your apps.
Create or edit an Assets import configuration.
Enter a descriptive map name.
Set Source system to Azure AD.
Confirm the pre-filled Assets schema. This is the JSM Assets schema where the import was started.
Select the target object type within the schema.
Select the schedule frequency.
Add attribute mappings using the syntax described below.
Example configuration
Sample Assets object schema
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=100Mapping reference
Use the following reference to define source fields, destination Assets attributes, and optional import settings.
Mapping or setting | Purpose and usage |
|---|---|
| Defines the unique key used to match and update existing Assets objects. In this example, Entra ID |
| Maps |
| Maps a Microsoft Graph user property to an Assets attribute. Any supported string, boolean, or date property can be used as a source field. See the Microsoft Graph user properties reference: https://learn.microsoft.com/en-us/graph/api/resources/user?view=graph-rest-1.0#properties Common source fields include |
| Maps the first value in the Entra ID |
| Maps the employee cost center from Entra ID to the Assets |
| Maps the employee division from Entra ID to the Assets |
|
To enable manager expansion, add key:id=WorkerID
map:EmployeeManager=ManagerObject|WorkerID=${EmployeeManager}|create=true
config:data_limit=10000Set |
| Exports all Entra ID groups assigned to each user. Before enabling this setting, create an Assets schema named Azure Groups with these text attributes: Also add an Azure Groups reference attribute to the user object type. This attribute must point to the Azure Groups object type. |
| Exports all licenses assigned to each user. Before enabling this setting, create an Assets schema named Azure Licenses with these text attributes: |
| Optionally limits the imported users by using a Microsoft Graph filter expression. Any valid Microsoft Graph filter expression can be used. To pull User of type Member To remove users with email that starts with test
To pull only employees
|
| Maps sign-in activity fields, such as:
To fetch these fields, grant the OnLink app |
| Optionally limits the number of users imported from Entra ID. Use this setting for initial testing or validation. |
| Overrides the default |
Notes and caveats
Manager mappings: Use
config:expand=managerand consider a dedicated manager import job because Entra ID manager expansion does not support filters.Groups and licenses: The required Assets schemas and attribute names must exist before enabling group or license export.
Filters: Validate Microsoft Graph filter syntax before adding it to the import configuration.
Sign-in activity: The OnLink Entra ID app must have
AuditLog.Read.Allpermission to read sign-in activity fields.Testing: Start with a small
config:data_limit, confirm the mapping results, and then increase the limit for production imports.