CI Is getting created after de-dup remediation-Urgent

MDAQUIBK
Tera Contributor

‎05-05-2025 03:55 AM

Hi All,

 

We have recently completed the integration of Tanium with ServiceNow. Currently, we have multiple data sources feeding CI data for servers and computers, including Azure and AWS.

 

Recently, we encountered a duplicate CI issue where both Tanium and Azure were creating records for the same device but with different serial numbers. As part of the remediation, we decided to retain the Tanium record as the primary CI.

After completing the remediation and archiving process, the next day, when both the Azure and Tanium discovery jobs ran again, duplicate records were recreated. Although we retained the Tanium CI as the primary record and merged all related items (including the serial number and CI type), the duplicates were still created and all related items were reset.

 

We would appreciate your assistance in resolving this issue. Our objective is to retain the primary CI (from Tanium) and ensure that Azure and Tanium update the same record, rather than creating duplicates.

 

Regards,

Aquib

0 Helpfuls
  • 327 Views
1 REPLY 1

William44
Mega Guru

‎05-06-2025 08:33 AM

Aquib,

 

 

If you want to allow Azure to create CIs that Tanium hasn't created, you need to modify the Identification Rules for the affected CI classes.

  1. Define the criteria that allows you to identify unique CIs - this may be different for different classes
  2. Update the Identification Rules based on these criteria as described in the Create a CI identification rule documentation

 

If you only want Azure to update CIs and not create them, you can use IRE data source rules to prevent Azure from inserting new CIs for specific classes. This can also serve as an additional layer of protection to prevent Azure from creating new CIs. You will need to configure the both the CI reconciliation rules and the IRE data source rules.

 

0 Helpfuls