wish help you to fix your issue You should do it by creating a MassTransit-based receiver, that receives the messages from the given topic, and then forwards the messages (by using Rebus' one-way client) to your Rebus endpoint(s). The reason why you should do it like this, is that MassTransit and Rebus are most likely using Azure Service Bus in slightly different ways, and with very different headers on the messages, meaning that the two service buses will not be readily wire-compatible.
will be helpful for those in need You are observing the correct behavior :) As stated in the Message Auditing documentation messages get copied to the audit queue before the message disappears, i.e. either
Handle Publish/Subscribe in Rebus with Azure Service Bus
I hope this helps you . Rebus uses topics by creating a subscription for each topic you subscribe to, and then configure the subscription to forward received messages to the input queue of the bus. If the bus does not have an input queue with the expected name (either one created by Rebus, or one you created manually), things will not work.
Code example for using Rebus with Azure Service Bus, Queue and Topic