1-Build Objects/Attributes
Once you completed Source and Destination configurations, it is time to create Object Types and their relations according to the Azure AD data model.
You may also choose to enable or disable Object Schema sharing.
Pro Tip: Commonly, our customers create references from other Object Schemas and are in need of accessing the Azure AD data. We recommend enabling the Object Schema sharing.
Review the options and click the Build Objects/Attributes button.
 |
This needs to be done only one time. When this build is completed successfully you don't need to do it again. You will get a message if you already completed this step.
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- Test Run
You can test the configuration by clicking the Test Run button. This will import the first 100 Entra ID (Azure AD) Users to your Object Schema. After the test run wait for a few minutes for the process to finish and check your Object Schema.
You may click the Check Test Import Status button to check the import execution status.
 |
3- Import Run / Schedule
If you are happy with the results of the test run, please run a manual import.
 |
Pro Tips:
You can select which data types you would like to import. This way you can decrease the amount of data transferred to your Assets.
Please note that if you have a large number of Azure AD users or groups, this import will take time. We suggest testing it outside of the busy hours when JSM Assets is not used heavily.
If you didn’t filter Users and Groups on the Source tab, it may be a good time to think and configure before clicking the Start Import button.
In case you currently have an earlier version than 4.6.0, we highly recommend upgrading to the latest version. We now have a new feature called “Full Throttle”. You may enable it on the Admin page. This will allow you to import large amount of users and groups.
Please note that there is one known and accepted limitation for the Full Throttle mode.
Known Limitation
A user can have max 20 groups mapped.
If your users are members of more than 20 groups then you may follow the step-by-step guide for:
Mapping Azure AD Users with Jira Users and Jira Groups
Contact us to find the best option for your site.
4- Schedule
You have 3 options for the scheduling.
 |
Pro Tip:
We recommend importing manually first by clicking the “Start Import“ button and measuring the import duration. In case a full import takes long time (i.e. more than an hour), or if there are multiple imports scheduled at the same time in your JSM Site, then hourly scheduling may not be the best option. Prefer Daily scheduling in such case which is the most common import schedule among the JSM customers.
Important note regarding daily imports
Daily imports are commonly scheduled for late night hours (00:00-06:00) when there is no heavy load on the system. However, it is also good to know that these times are also used for the JSM/Assets version updates by Atlassian. In case there is a conflict, the import process fails. You would see the error message in your logs. Please check your import flow daily and configure the Notify Me feature if you want to get notified when there is an error. We highly recommend following the Operational tips provided on the following page: Operations