Import
- Pio
- Eva Ruzheva
1. Build Objects/Attributes
After completing the Source and Destination configurations, it's time to create Object Types and their relationships based on the Azure AD data model.
You can also choose to enable or disable Object Schema sharing.
Pro Tip: Many of our customers create references from other Object Schemas and need access to the Azure AD data. We recommend enabling Object Schema sharing.
Review the options, then click the "Build Objects/Attributes" button.
 |
This step only needs to be completed once. Once the build is successful, you won’t need to repeat it. If this step has already been completed, a message will appear confirming it.
You may check your new Object Schema now and make sure the Object Types and Attributes are successfully created.
 |
The Object Schema Graph will be as follows:
 |
2. Import
You can test the configuration by clicking the Test Import button. This will import the first 100 Entra ID (Azure AD) users into your Object Schema. After the test runs, wait a few minutes for the process to complete, then check your Object Schema.
To monitor the progress, click the Check Import Status button to view the import execution status.
|
If you are happy with the results of the test run, please run a manual full import.
Please note the following known limitation:
Known Limitation
A user can be mapped to a maximum of 20 groups.
If your users are members of more than 20 groups, you can follow the step-by-step guide here:
Mapping Azure AD (Entra ID) Users with Jira Users and Jira Groups
Alternatively, contact us to discuss the best solution for your site.
Pro Tips:
You can select the data types (Object Types) and user properties (Attributes) you wish to import, helping reduce the amount of data transferred to your Assets. For more details, refer to our guide: Admin Configuration .
Please note:
If you have a large number of Azure AD users or groups, the import may take some time. We recommend testing the import during off-peak hours when JSM Assets is not heavily used.If you haven’t filtered Users and Groups on the Source tab, now would be a good time to configure those settings before clicking the Start Import button.
3. Schedule
You have 4 options for the scheduling.
 |
Pro Tip:
We recommend starting with a manual import by clicking the “Full Import” button to measure the import duration.
If the full import takes an extended amount of time (e.g., over an hour), or if multiple imports are scheduled simultaneously in your JSM Site, hourly scheduling may not be ideal. In such cases, we suggest using Daily scheduling, which is the most commonly used import schedule among JSM customers.
Important Note: Multiple Daily Imports
When scheduling multiple imports per day, ensure there is a gap of at least 3 to 4 hours between each one. It's also best to schedule imports during periods of low JSM Assets usage to minimize impact on performance.
Important Note: Daily Imports
Daily imports are typically scheduled during late-night hours (00:00-06:00), when the system is under lighter load. However, keep in mind that these hours are also used by Atlassian for JSM/Assets version updates. If there's a conflict, the import process may fail, and you will see an error message in your logs.
To ensure smooth operation, check your import flow daily and enable the Notify Me feature to receive alerts if an error occurs. We highly recommend reviewing the Operational Tips provided on the following page: Operations