Merge pull request #236680 from spelluru/sbusupdates0502

JMS doesn't support receiving over sessions

Author: prmerger-automator[bot]

articles/service-bus-messaging/jms-developer-guide.md

@@ -2,7 +2,7 @@
 title: Azure Service Bus JMS 2.0 developer guide
 description: How to use the Java Message Service (JMS) 2.0 API to communicate with Azure Service Bus
 ms.topic: article
-ms.date: 02/12/2022
+ms.date: 05/02/2023
 ---
 
 # Azure Service Bus JMS 2.0 developer guide
@@ -174,6 +174,9 @@ A session can be created from the connection object as shown below.
 Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);
 ```
 
+> [!NOTE]
+> JMS API doesn't support receiving messages from service bus queues or topics with messaging sessions enabled. 
+
 #### Session modes
 
 A session can be created with any of the below modes.

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

@@ -3,7 +3,7 @@ title: Azure Service Bus premium and standard tiers
 description: This article describes standard and premium tiers of Azure Service Bus. Compares these tiers and provides technical differences.
 ms.topic: conceptual
 ms.custom: ignite-2022
-ms.date: 10/12/2022
+ms.date: 05/02/2023
 ---
 
 # Service Bus Premium and Standard messaging tiers
@@ -87,7 +87,7 @@ Azure Service Bus premium tier namespaces support the ability to send large mess
 
 Here are some considerations when sending large messages on Azure Service Bus -
    * Supported on Azure Service Bus premium tier namespaces only.
-   * Supported only when using the AMQP protocol. Not supported when using the SBMP protocol.
+   * Supported only when using the AMQP protocol. Not supported when using SBMP or HTTP protocols.
    * Supported when using [Java Message Service (JMS) 2.0 client SDK](how-to-use-java-message-service-20.md) and other language client SDKs.
    * Sending large messages will result in decreased throughput and increased latency.
    * While 100 MB message payloads are supported, it's recommended to keep the message payloads as small as possible to ensure reliable performance from the Service Bus namespace.

articles/service-bus-messaging/service-bus-troubleshooting-guide.md

@@ -29,7 +29,7 @@ The following steps may help you with troubleshooting connectivity/certificate/t
         </Detail>
     </Error>
     ```
-- Run the following command to check if any port is blocked on the firewall. Ports used are 443 (HTTPS), 5671 and 5672 (AMQP) and 9354 (Net Messaging/SBMP). Depending on the library you use, other ports are also used. Here is the sample command that check whether the 5671 port is blocked. C 
+- Run the following command to check if any port is blocked on the firewall. Ports used are 443 (HTTPS), 5671 and 5672 (AMQP) and 9354 (Net Messaging/SBMP). Depending on the library you use, other ports are also used. Here's the sample command that check whether the 5671 port is blocked. C 
 
     ```powershell
     tnc <yournamespacename>.servicebus.windows.net -port 5671
@@ -40,7 +40,7 @@ The following steps may help you with troubleshooting connectivity/certificate/t
     ```shell
     telnet <yournamespacename>.servicebus.windows.net 5671
     ```
-- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. This command will try to establish 25 different TCP connections every 1 second with the service. Then, you can check how many of them succeeded/failed and also see TCP connection latency. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
+- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. This command tries to establish 25 different TCP connections every 1 second with the service. Then, you can check how many of them succeeded/failed and also see TCP connection latency. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
 
     ```shell
     .\psping.exe -n 25 -i 1 -q <yournamespace>.servicebus.windows.net:5671 -nobanner     
@@ -62,7 +62,7 @@ The following steps may help you with troubleshooting connectivity/certificate/t
 Backend service upgrades and restarts may cause these issues in your applications.
 
 ### Resolution
-If the application code uses SDK, the [retry policy](/azure/architecture/best-practices/retry-service-specific#service-bus) is already built in and active. The application will reconnect without significant impact to the application/workflow.
+If the application code uses SDK, the [retry policy](/azure/architecture/best-practices/retry-service-specific#service-bus) is already built in and active. The application reconnects without significant impact to the application/workflow.
 
 ## Unauthorized access: Send claims are required
 
@@ -84,7 +84,7 @@ To learn how to assign permissions to roles, see [Authenticate a managed identit
 ## Service Bus Exception: Put token failed
 
 ### Symptoms
-You'll receive the following error message: 
+You receive the following error message: 
 
 `Microsoft.Azure.ServiceBus.ServiceBusException: Put token failed. status-code: 403, status-description: The maximum number of '1000' tokens per connection has been reached.` 
 
@@ -117,6 +117,17 @@ Specify the full Azure Resource Manager ID of the subnet that includes the name
 Remove-AzServiceBusVirtualNetworkRule -ResourceGroupName myRG -Namespace myNamespace -SubnetId "/subscriptions/SubscriptionId/resourcegroups/ResourceGroup/myOtherRG/providers/Microsoft.Network/virtualNetworks/myVNet/subnets/mySubnet"
 ```
 
+## Resource locks don't work when using the data plane SDK
+
+### Symptoms
+You have configured a delete lock on a Service Bus namespace, but you're able to delete resources in the namespace (queues, topics, etc.) by using the Service Bus Explorer. 
+
+### Cause
+Resource lock is preserved in Azure Resource Manager (control plane) and it doesn't prevent the data plane SDK call from deleting the resource directly from the namespace. The standalone Service Bus Explorer uses the data plane SDK, so the deletion goes through. 
+
+### Resolution
+We recommend that you use the Azure Resource Manager based API via Azure portal, PowerShell, CLI, or Resource Manager template to delete entities so that the resource lock will prevent the resources from being accidentally deleted.
+
 ## Next steps
 See the following articles: