Unclassed Hardware CI created by Microsoft TVM and ServiceGraph Connector for Microsoft IntuneIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Current Behavior: When selecting Configuration Item in Vulnerable item then the record shows Unclassed Hardware Expected behavior: When selecting matched Configuration Item then the record should show appropriate CI(Ex: Handheld Computing Device), not Unclassed Hardware. - Vulnerable item(sn_vul_vulnerable_item) - Linked Current CI: unclassed_hardware in above VI(cmdb_ci_unclassed_hardware) - Expected CI: Handheld Computing Device(Example: cmdb_ci_handheld_computing) Note that users are using "ServiceGraph Connector for Microsoft Intune" to import CI infoIn addition, users are using "Vulnerability Response Integration with Microsoft Threat and Vulnerability Management" to import vulnerable info. Reproduce steps: 1. Run SG-Intune Devices to import the CI info(Ex: Handheld Computing Device)2. Imported CI showing FQDN as <device-hostname-1>3. Run the job of Microsoft TVM Machines Integration to create source data in Discovered item, which has FQDN as device-hostname-2, not the same of above CI4. Run the job of Microsoft TVM Machine Vulnerabilities Integration to create the VI linked with unexpected CI created in the steps3 Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The FQDN info between SG-Intune Devices and Microsoft TVM Machines Integration are not the same. So, the asset info of Microsoft TVM Machines Integration was not matched as the same asset info of "SG-Intune Devices" via FQDN of CI lookup rule. This leads to creating Unclassed Hardware CI when running the TVM job. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } To fix the issue: 1. Change the source data of FQDN in TVM side from <device-hostname-2> to <device-hostname-1> to match the correct CI to avoid creating new unwanted CI2. Run Microsoft TVM Machines Integration with backdating of Import since to reimport the same asset info from TVM. The sourceID is the same and only FQDN has been changed in TVM side so the same Discovered Item will be updated with the latest source data with the new FQDN value3. Re-apply CI lookup rule for this discovered item, it will use the new FQDN value to match to the correct CI