Hi @ExtAbhayPat ,

What’s happening: Azure reuses IPs for VM instances but allocates a new Object ID when the VM is re-created or restarted.

Why: The IRE (Identification & Reconciliation Engine) is designed to treat Object ID (cloud-native identifier) as a unique key for the CI.

Best Practice Fix:
* Ensure the Identification Rule for cmdb_ci_vm_instance includes the Cloud Resource Identifier (Object ID / Azure Resource ID) along with Subscription + Tenant rather than relying on IP alone.
* This way, IRE won’t merge CIs incorrectly and avoids duplication due to reused IPs.
* Keep IP as a contributing identifier, but not the only key.

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