Bad Intune data was imported into our HAM module. Help!

[William Habekot]

When our HAM module was implemented prior to me coming on board, the implementation partner recommended we connect via servicegraph to our Intune instance.  This data source was not and continues to be inaccurate.  I have several thousand devices that have been retired, but were never unenrolled from Intune.  Therefore, I now have several thousand devices that have been pulled into our ServiceNow HAM module as "in use" devices.  Looking for tips, tricks, and ideas from the community on how to best clean up this mess.  Has anyone experienced this issue?  Please help!  Thanks.

Will

State of Oklahoma IT Asset Manager

[Ashok Sasidhara]

As you mentioned that the source data itself has a problem, the first step is to connect with the team managing intune and ask them to fix the data. Otherwise inaccurate data will keep coming into ServiceNow. 

For the devices which are already populated with the wrong state in ServiceNow, the Asset state should be updated in bulk to 'Retired'. This correction should be done in the CMDB as the integration actually populates the CMDB and there may be some CI classes populated which may not have an Asset class linked to it (assuming you may need corrections on those also). For all CI classes linked with asset classes, the asset state will anyways sync to Retired when the corresponding CI's status is updated as Retired.

[Amarjeet Pal]

Hello @William Habekot ,

If you have several thousand devices that were retired but never unenrolled from Intune, and these devices are being pulled into your ServiceNow HAM module as "in use" devices, there are a few steps you can take to clean up this mess:
1. Identify the retired devices that are still enrolled in Intune
2. Update ServiceNow with accurate device status

3. Remove retired devices from Intune
4. Develop a process for device retirement

Thanks

Amarjeet Pal