Azure VM Discovery creates new child CIs (disks, NICs) instead of updating the parent VM when the Azure payload is missing a unique VM identifier<!-- /*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: ; } } Issue During Azure cloud discovery, the parent virtual machine CI is not updated; instead, new CIs are created for child resources such as disks and NICs, resulting in incorrect or duplicate records. Symptoms After an Azure discovery run, the existing parent VM CI is not updated.New CIs appear for the VM's child resources (disks, network interfaces) rather than attaching to the existing VM CI.The behavior is observed for Azure VMs whose discovery payload does not include a unique VM identifier (for example, a serial number or VM UUID). Cause The Identification and Reconciliation Engine (IRE) requires a unique identifier to match discovered data to an existing CI. When the payload returned by the Azure API for a virtual machine does not include a unique VM identifier (such as a serial number or VM UUID), IRE cannot reconcile the discovered VM against the existing parent CI. As a result, it does not update the parent VM and instead creates new CIs for the child resources. This originates in the data returned by the source system (Azure), not in the ServiceNow discovery process. Resolution For an affected VM, review the discovery results and ECC queue payload and confirm whether a unique VM identifier (serial number or VM UUID) is present for the virtual machine itself.If the unique identifier is absent from the Azure payload, IRE has no key to reconcile against, which explains why child-resource CIs are created instead of the parent VM being updated.Because the missing identifier originates in the data Azure returns, the corrective action is on the Azure side - ensure the affected VMs expose the required unique identifier in the API/discovery payload.Re-run discovery after the identifier is present in the payload and confirm the parent VM CI updates correctly and the child resources attach to it.