Merge pull request #269789 from spelluru/sbusgit0321

Service Bus Git issues

Author: prmerger-automator[bot]

articles/service-bus-messaging/compare-messaging-services.md

@@ -58,7 +58,7 @@ Service Bus is a fully managed enterprise message broker with message queues and
 
 Service Bus is a brokered messaging system. It stores messages in a "broker" (for example, a queue) until the consuming party is ready to receive the messages. It has the following characteristics:
 
-- Reliable asynchronous message delivery (enterprise messaging as a service) that requires polling
+- Reliable asynchronous message delivery (enterprise messaging as a service) that requires polling. If you're using Service Bus and you need to receive messages without having to poll the queue, you can achieve it by using a **long polling** receive operation using the TCP-based protocols that Service Bus supports. 
 - Advanced messaging features like first-in and first-out (FIFO), batching/sessions, transactions, dead-lettering, temporal control, routing and filtering, and duplicate detection
 - At least once delivery of a message
 - Optional ordered delivery of messages

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

@@ -1,8 +1,9 @@
 ---
 title: Azure Service Bus - Browse or peek messages
 description: Browse and peek Service Bus messages enables an Azure Service Bus client to enumerate all messages in a queue or subscription.
-ms.topic: article
+ms.topic: concept-article
 ms.date: 06/08/2023
+#customer intent: As a developer, I want to know how to browse or peek messages in a queue or a subscription, for diagnostic and debugging purposes. 
 ---
 
 # Browse or peek messages
@@ -15,6 +16,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 +31,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. 
 
@@ -132,7 +139,7 @@ print("Receive is done.")
 
 ---
 
-## Next steps
+## Related content
 Try the samples in the language of your choice to explore Azure Service Bus features. 
 
 - [Azure Service Bus client library samples for .NET (latest)](/samples/azure/azure-sdk-for-net/azuremessagingservicebus-samples/) - - **Sending and receiving messages** sample.