title: best practices with poison message handling for Azure service bus topic
body: <p>Dealing with poison messages (throwing exception while consuming) from Azure Service Bus can lead to loops till number of retries has reached <code>maxDeliveryCount</code> setting of topic subscription. </p>
  
  <ol>
  <li>Does the <code>SequenceNumber</code> of message added by Azure Service bus keeps on increasing on each failed attempt till it reaches <code>maxDeliveryCount</code> ?</li>
  <li>Setting <code>maxDeliveryCount</code> = 1, is that best practice to deal with poison messages so that consumer never attempt twice to process message once it failed </li>
  </ol>