Issue with Data Load for Service Graph Connector for Intune

[DebjitGhosh31]

Hi All,

I have made integration with MS Inutne from Servicenow via Service Graph Connector API in my Development instance. Now when I moved the exact same setup (same clientID, Token ID, SecretID) in my Test instance the data loading takes significantly longer. For e.g. in Dev it takes 15 min to load all data whereas in Test it takes 3 hrs or more. Both instances MID Servers are hosted in the same server and both have exact same setup. Can anyone help me why the same setup from same source takes so much longer to push data in test than Dev.

Any help will be much appreciated.

Regards,

Debjit

[Ratnakar7]

Hi @DebjitGhosh31 ,

Here are some things you can check:

1. Check the hardware resources: The test instance may have lower hardware resources compared to the development instance. Check if the test instance has enough CPU, memory, and storage resources to handle the data load.

2. Check the network connectivity: The network connectivity between the test instance and the MS Intune API could be slower or unstable, causing the data load to take longer. Check if there are any network issues or latency between the test instance and MS Intune API.

3. Check the logs: Check the logs in the MID Server in the test instance to see if there are any errors or warnings that could be causing the slower data load. You can also check the logs in the Service Graph Connector API to see if there are any errors or delays.

4. Check the data volume: Check if the test instance has a higher volume of data compared to the development instance. If the test instance has more data, it will take longer to load the data into ServiceNow.

5. Check the data transfer rate: Check if the data transfer rate between the MS Intune API and Service Graph Connector API is slower in the test instance. You can use a network monitoring tool to measure the data transfer rate.

If my response was helpful in resolving the issue, please consider accepting it as a solution by clicking on the ✅Accept solution button and giving it a thumbs up 👍. This will benefit others who may have a similar question in the future.

Thank you!

Ratnakar

[deanmpage · Accepted solution]

Hi @DebjitGhosh31 

I have just noticed an identical issue when implementing the Intune Service Graph Connector in my Dev and Test instances. Two things I discovered that impact the performance of the data load:

1. If possible, set the connection to HTTPS only, and not using a MID Server. I found that when using the MID Server the load took three times longer due to additional network scanning, firewalls, etc.
2. Difference in versions of the Service Graph Connector for Microsoft Intune plugin. My Dev instance was setup using v2.1.2 of the plugin, and Test was setup with v2.2.1. In the version updates ServiceNow has changed how the Data Loader scripts work: the older version pulls managed device data from Intune in bulk and then runs it through the transform map; the newer version is performing two extra calls to Intune for each managed device: getPrimaryUser and getIPAddresses. It's these additional individual calls that account for the additional load time. You can see the differences in loads by going to the Concurrent Import Sets via the Data Sources or Import Schedules and looking at the number of Outbound Http log records. You can also see the differences in the Data Loader scripts by going to Data Sources list view and adding the Data Loader column and comparing Dev & Test instances.

I'm not sure if anything can be done about this other than raise a Case with ServiceNow Support and see if they can do something to improve the performance of the loads i.e. possibly change it from individual calls to bulk loads in a later version.

While this doesn't fix the issue, I hope it helps explain it. 

Regards,

Dean.

[DebjitGhosh31]

Thanks @deanmpage  for you detailed response.

You are absolutely correct. Due to change in Data Loader script between the two versions and the two additional calls (i.e. getUser and getIPAddress), the load time is significantly longer.

Unfortunately we raised a case, but didn't found any solution other than constant tug of war between MS Support and ServiceNow Support, as both kept telling me it's the other tool that's the issue.

Thanks again.

Regards,

Debjit

[Kavitha Babu]

Hi All,

Recently faced the same issue and same situation with servicenow support .And also there is one more thing i would like to know ,if we want to extract additional data from intune e.g:'LAst login' attribute,  what steps do we need to implement?