We had auto discovery turned on for Change Management so when a change progressed to the Review state it automatically kicked off the discovery process for any CI's in the change request and kept the CMDB close to real time as possible as our scheduled discovery process varies by location.
When we recently migrated our Epic environment to Azure, duplicate servers are being created in the CMDB as a server reboot in the Azure environment changes the serial number each time the server is rebooted.
Has anyone encountered this issue and is there a known workaround or fix available?
