Allow duplicate CIs with same Serial Number but different Model IDs

[MarLoi]

We have a few devices that have the same serial numbers but different model IDs. We tried modifying the Hardware identification rule, but during the next data import through Intune SGC, still no records were made and the existing CIs were updated. We had to manually create the records.

Are there other ways to address this permanently? Thanks in advance for the help.

[AJ-TechTrek]

Hi @MarLoi ,

Great question — this is actually a common real‑world challenge in CMDB when integrating with sources like Intune SGC (Service Graph Connector).


As per my understanding,Let’s break down why it happens and how to fix it properly:

Problem recap
* You have multiple devices with:
* Same serial_number
* Different model_id
* Hardware Identification Rule is using serial_number (and maybe model_id) to identify uniquely.
* When Intune SGC runs:
* It updates existing CI instead of creating separate ones.
* Manual creation works but isn't sustainable.

Root cause
* The Identification Rule is still matching the existing record based on serial_number.
* model_id in most cases is not treated as an identifier field in OOB rules — it’s often just an attribute.
* So even if model differs, the same serial number makes it look like the same device.

Solution (permanent fix)
1. Adjust Identification Rule
* Go to:
Identification Rules > Hardware
* In the Identifier Entries section:
* Instead of just serial_number, create a composite key:
serial_number + model_id
* This tells IRE:
“Only treat as same CI if both serial number and model ID match.”
* Be careful: if you add model_id as identifier, you must ensure it’s consistently populated in Intune SGC and other sources, otherwise it can cause unwanted duplicate CIs.

2. Review SGC Transform Maps
* Check the transform map or data source behind Intune SGC:
* Make sure model_id is properly mapped to the CI.
* Missing or inconsistent model_id data = rule won’t work as planned.

3. Test your new rule safely
* Create a test identification rule first.
* Use a staging table or sandbox environment to run the SGC import.
* Verify:
* Does it create two separate CIs?
* Does it stop updating the wrong CI?

4. Optional: Add fallback rule
* Sometimes, devices truly share serials (rare, but e.g. thin clients).
* Consider adding other identifiers (e.g., asset_tag or name) if they’re available and reliable.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025