The horizontal discovery 'Windows OS - Servers' pattern updates the AWS / Azure Windows Server CI object_id twice in one run

HD discovery updates the Azure Windows Server CI object_id twice in one single run of 'Windows OS - Servers' once with azure$ or amazon$ before the object_id value and then the object_id expected value.

These flapping changes are audited of the configuration item resulting in undesired entries in the history of the configuration item.

1. Run a horizontal quick discovery against an Azure-hosted Windows server.
2. Review the history of the created cmdb_ci_win_server.

Notice that the object_id of the configuration item is updated twice. At first the object_id is set to azure$object_id_value, then it is set to the expected object_id value.

There is no known workaround for this issue. If you are able to upgrade, review the "Intended Fix Version" section below below to determine the versions that have a permanent fix.