Merge pull request #300536 from spelluru/main

Freshness review

Author: prmerger-automator[bot]

articles/service-bus-messaging/duplicate-detection.md

@@ -2,7 +2,7 @@
 title: Azure Service Bus duplicate message detection | Microsoft Docs
 description: This article explains how you can detect duplicates in Azure Service Bus messages. The duplicate message can be ignored and dropped.
 ms.topic: article
-ms.date: 07/23/2024
+ms.date: 05/28/2025
 ---
 
 # Duplicate detection
@@ -29,7 +29,7 @@ The `MessageId` can always be some GUID, but anchoring the identifier to the bus
 >- When **partitioning** is **enabled**, `MessageId+PartitionKey` is used to determine uniqueness. When sessions are enabled, partition key and session ID must be the same. 
 >- When **partitioning** is **disabled** (default), only `MessageId` is used to determine uniqueness.
 >- For information about `SessionId`, `PartitionKey`, and `MessageId`, see [Use of partition keys](service-bus-partitioning.md#use-of-partition-keys).
->- When using **partitioning** and sending **batches** of messages, you should ensure that they do not contain any partition identifying properties. Since deduplication relies on explicitly setting message IDs to determine uniqueness, it is not recommended to use deduplication and batching together with partitioning.
+>- When using **partitioning** and sending **batches** of messages, you should ensure that they don't contain any partition identifying properties. Since deduplication relies on explicitly setting message IDs to determine uniqueness, it isn't recommended to use deduplication and batching together with partitioning.
 
 > [!NOTE]
 > Scheduled messages are included in duplicate detection. Therefore, if you send a scheduled message and then send a duplicate non-scheduled message, the non-scheduled message gets dropped. Similarly, if you send a non-scheduled message and then a duplicate scheduled message, the scheduled message is dropped. 

articles/service-bus-messaging/service-bus-filter-examples.md

@@ -2,7 +2,7 @@
 title: Set subscriptions filters in Azure Service Bus | Microsoft Docs
 description: This article provides examples for defining filters and actions on Azure Service Bus topic subscriptions.
 ms.topic: how-to
-ms.date: 07/18/2024
+ms.date: 05/28/2025
 ms.devlang: csharp
 ms.custom: devx-track-dotnet
 ---

articles/service-bus-messaging/service-bus-premium-messaging.md

@@ -3,7 +3,7 @@ title: Azure Service Bus premium messaging tier
 description: This article describes standard and premium tiers of Azure Service Bus. Compares these tiers and provides technical differences.
 ms.topic: conceptual
 ms.custom: devx-track-extended-java
-ms.date: 07/22/2024
+ms.date: 05/28/2025
 ---
 
 # Service Bus premium messaging tier
@@ -72,7 +72,7 @@ To learn how to configure a Service Bus namespace to automatically scale (increa
 >
 >  * **Reactive**: If additional workloads are identified by studying the resource usage metrics, then additional resources can be allocated to the namespace to incorporate increasing demand.
 >
-> The billing meters for Service Bus are hourly. In the case of scaling up, you only pay for the additional resources for the hours that these were used.
+> The billing meters for Service Bus are hourly. When scaling up, you only pay for the additional resources for the hours that these were used.
 >
 
 ## Get started with premium messaging
@@ -114,6 +114,7 @@ You can also enable support for large message for existing queues (or topics), b
 ## Network security
 The following network security features are available only in the premium tier. For details, see [Network security](network-security.md).
 
+- [Service tags](network-security.md#service-tags)
 - [Network service endpoints](network-security.md#network-service-endpoints)
 - [Private endpoints](network-security.md#private-endpoints)
 
@@ -156,7 +157,7 @@ This feature allows promoting any secondary region to primary, at any time. Prom
 
 
 
-## Java Message Service (JMS) support
+## Java Message Service (JMS) 
 The premium tier supports JMS 1.1 and JMS 2.0. For more information, see [How to use JMS 2.0 with Azure Service Bus Premium](how-to-use-java-message-service-20.md).
 
 The standard tier supports only JMS 1.1 subset focused on queues. For more information, see [Use Java Message Service 1.1 with Azure Service Bus standard](service-bus-java-how-to-use-jms-api-amqp.md).