Inject transport messageId into headers for debug and investigation

At my company we’ve experienced some hiccups using Service Bus, we opened a support ticket and got some assistance from Particular, we also opened support tickets with Microsoft to little effect as they were not able to track down the messages on their side, due to us not being able to provide the MessageId

My question: Is it possible to get access to the MessageId assigned by the transport, in this case, Azure Service Bus, and assign it to the headers for potential debugging scenarios?

Hi Riaan,

Unfortunately, this is currently not possible. I’ve raised a feature request on your behalf.
Please subscribe to it to get notified and add comments to provide more details.

Thank you,