CI updated by SCCM Integration it's reverted to the record's correct settings by the Intune integration.Issue Imported CIs from Service Graph connector for Microsoft Intune is updated by SCCM integration which may result in multiple serial number related to the same Configuration Item.ReleaseRomeCauseThe cause fro this issue is that Resource IDs got repurposed or the new SCCM server was providing a resource id that matched to different computer and hence flip flopping. This might be happening right around the time that new SCCM server was pointed to.This is a case where the new SCCM server is providing a resource id that is being looked up in sys_object_source and getting matched for a totally different computer (which was pre-existing from the previous SCCM environment). ResolutionThe suggested way to use a new SCCM environment is to clear out those lookups a.k.a sys_object_source records so these mismatches do not occur. IRE uses the sys_object_source to short cut the IRE identification process and uses the target sys_id to make updates to the target computer directly. Please refer to the below steps to have a clean run- Clear out the sys_object_source records with name = SG-SCCM- Clear out the cmdb_serial_number table where created by 'svcSCCMIntegration'- Run a full Intune Integration- Run a full (not incremental - remove last run datetime for all data sources and update/save) SG-SCCM integration- Validate in test/dev/uat to see if the issue persists.