1
...
. Build Objects/Attributes
Once you completed After completing the Source and Destination configurations, it is 's time to create Object Types and their relations according to relationships based on the Azure AD data model.
You may can also choose to enable or disable Object Schema sharing.
Info |
---|
Pro Tip: Commonly, Many of our customers create references from other Object Schemas and are in need of accessing access to the Azure AD data. We recommend enabling the Object Schema sharing. |
Review the options and , then click the "Build Objects/Attributes" button.
Note |
---|
This step only 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 stepcompleted 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 test will import the first 100 Entra ID (Azure AD) Users to users into your Object Schema. After the test run runs, wait for a few minutes for the process to finish and complete, then check your Object Schema.
You may To monitor the progress, click the Check Import Status button to check view the import execution status.
If you are happy with the results of the test run, please run a manual full import.
Please note that there is one known and accepted limitation.the following known limitation:
Note |
---|
Known Limitation A user can have max be mapped to a maximum of 20 groups mapped. |
If your users are members of more than 20 groups then , you may can follow the step-by-step guide forhere:
Mapping Azure AD (Entra ID) Users with Jira Users and Jira Groups
Contact Alternatively, contact us to find discuss the best option solution for your site.
Info |
---|
Pro Tips:
|
...
|
3. Schedule
You have 3 4 options for the scheduling.
Info |
---|
Pro Tip:
|
Note |
---|
Importantnote regarding daily importsNote: Multiple Daily ImportsWhen 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. |
Note |
---|
Important Note: Daily ImportsDaily imports are commonly typically scheduled for during late-night hours (00:00-06:00), when there is no heavy load on the systemthe system is under lighter load. However, it is also good to know keep in mind that these times hours are also used by Atlassian for the JSM/Assets version updates by Atlassian. In case If there is 's a conflict, the import process fails. You would see the may fail, and you will see an error message in your logs. Please To ensure smooth operation, check your import flow daily and configure enable the Notify Me feature if you want to get notified when there is to receive alerts if an error occurs. We highly recommend following reviewing the Operational tips Tips provided on the following page: Operations |