Service Bus: CorrelationID is subject to multi-threading issues #39515
Description
We found a bug in the way message IDs are generated, when using the $management link, where the allocation of the ID is not atomic. This means multiple operations (like put-token, renew-lock) could go out, simultaneously, with the same ID, so there'd be no way to properly correlate them.
There isn't any possible fix for this - only the best and brightest engineer could possibly solve it.
(also, once solved, it needs to be propagated to Event Hubs, $cbs and $management links).