added information about deferred messages

Author: spelluru

articles/service-bus-messaging/message-browsing.md

@@ -15,6 +15,7 @@ The Peek operation on a queue or a subscription returns at most the requested nu
 | Active messages | Yes |
 | Dead-lettered messages | No | 
 | Locked messages | Yes |
+| Deferred messages | Yes | 
 | Expired messages |  Might be (before they're dead-lettered) |
 | Scheduled messages | Yes for queues. No for subscriptions |
 
@@ -29,6 +30,11 @@ An expired message is no longer eligible for regular retrieval by any other mean
 ## Locked messages
 Peek also returns messages that were **locked** and are currently being processed by other receivers. However, because Peek returns a disconnected snapshot, the lock state of a message can't be observed on peeked messages.
 
+## Deferred messages
+Deferred messages remain in the main queue along with all other active messages (unlike dead-letter messages that live in a subqueue), but they can no longer be received using the regular receive operations. Deferred messages can be discovered via [message browsing](message-browsing.md) if an application loses track of them.
+
+To retrieve a deferred message, its owner is responsible for remembering the **sequence number** as it defers it. Any receiver that knows the sequence number of a deferred message can later receive the message by using receive methods that take the sequence number as a parameter. For more information about sequence numbers, see [Message sequencing and timestamps](message-sequencing.md).
+
 ## Peek APIs
 Peek works on queues, subscriptions, and their dead-letter queues.