Serial Number field value not getting updated on the Server table Issue ProblemWhen Server CI data is imported via the SG-Azure connector, the 'Serial Number' field on the target Server CI record is not updated with the new value from the import payload. Instead, a new record is created in the cmdb_serial_number table, but the main CI record retains the old serial number.To reproduce the issue:1. Identify a Windows Server CI with an existing serial number value.2. Note the new serial number value provided in the import payload.3. Run the SG-Azure import process (SG-Azure Virtual Machines).4. Verify that the Serial Number field on the Server CI record remains unchanged, and a new record is created in the cmdb_serial_number table instead. Release N/A Cause Root Cause1. The SG-Azure import process prioritizes the serial number value from the sys_object_source table over the new value in the payload when an existing CI is found, as per designed logic.2. The Azure VM API response does not return the hardware serial number, only the UUID, and the import process does not directly update the CI's Serial Number field in this scenario.3. Deep discovery via 'Run Command' was not enabled in the environment, preventing automated retrieval of the updated serial number from the VM instance. Resolution Steps to Resolve1. Confirm that the SG-Azure import process is functioning as designed, as it uses the first non-null value from the sys_object_source table or properties.vmId from the API response.2. Enable deep discovery using the 'Run Command' feature to retrieve and update the hardware serial number for Azure VMs. This involves executing commands like GetCimInstance for Windows on the VM instance.3. Refer to the ServiceNow documentation for detailed instructions on configuring deep discovery: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2001668.