No error or status code indicates duplicate detection drop in Azure Service Bus

Goal: Verify whether the Azure Service Bus duplicate‑detection cache persists after a namespace restart, queue pause, or scale operation so that applications can predict if a retried message with the same ID will be silently dropped or treated as a new message.

Uncertainty: Public documentation does not state if the cache is cleared during pause, scaling, or broker node failure, and no error or status code is emitted when a message is suppressed by duplicate detection, making the internal state invisible.

• Does the duplicate‑detection cache survive a Service Bus namespace restart?
• Is the cache cleared when a queue or topic is paused or scaled?
• After a broker node failure, are previously tracked message IDs retained?