We are enabling the Outbox feature on an endpoint to prevent phantom records and ensure consistency. We understand that the Outbox provides an “at-least-once” guarantee, meaning duplicate messages can occasionally be sent.Since we do not control the downstream endpoints, we cannot guarantee they are idempotent. To mitigate this, I am considering enabling native Duplicate Detection on the transport level (Azure Service Bus).My specific question is: If a message is dispatched multiple times by the Outbox, (e.g. if NServiceBus does not receive the ACK from the transport due to a network error and retries the dispatch) will NServiceBus use the exact same physical Message ID for each attempt? If the physical MessageId is stable across these dispatch retries, my assumption is that ASB’s native deduplication will correctly identify and drop the duplicates. Could you confirm if this is how the Outbox-to-ASB dispatching logic behaves?
Thanks for your help