Cloud Management CMPv1 Azure VM Discovery IdentifierIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Overview In CMPv1, Discovered VMs are stored in the [cmdb_ci_azure_vm] table, with the discovery process being enabled by the legacy plugin Microsoft Azure. Details During Discovery, the Identification and Reconciliation Engine (IRE) is not used. Instead, the procedure checks on the [normalizedobject_db_mapping] table fields with the following search criteria: Resource Type = VMTarget Table = Azure Virtual Machine Instance"Used to correlate" = true The out of box field used for identification is [correlation_id], which is mapped from "Resource ID" from Azure. Additional Information Azure troubleshooting Azure Functions discovery