Import Configuration for Microsoft Intune Importer
1. Create an Import Connection
Once you complete Source and Destination configurations, it is time to create the Import Connection and begin the import process. Navigate to Import Tab and select “+” button.
 |
Choose a distinctive name for your connection and select the Source and Destination you created for this import. Additionally, you have the option to set a schedule for your import or choose "None." To save your changes, please click the "Save" button.
2. Build Schema
Once you complete creating the import connection, it is time to create Object Types and their relations according to the Okta data model.
Start by clicking on the “Build “ button:
|
Review the options and click the Build Schema Model 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:
|
Please find an explanation for the common question regarding the schema below:
2. Test and Full Imports
You can test the configuration by clicking the Test Import button. This will import the first 100 Microsoft Intune Managed Devices to 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 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. The maximum number of records you can import is 1000 by default. You can update this value from the Admin tab.
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.
Due to the way Atlassian’s Forge platform handles scheduling, functions are repeatedly invoked at set intervals. Each trigger starts approximately five minutes after the app is deployed. As a result, it is not possible to specify the exact minute when the scheduled import will run. For more details, refer to Atlassian’s documentation Atlassian’s Documentation.