Service tags can be used from other services to provide access to SB, in this case they can reach namespaces in all SKUs

Author: EldertGrootenboer

articles/service-bus-messaging/network-security.md

@@ -25,9 +25,8 @@ You can use service tags to define network access controls on [network security
 | --- | -------- |:---:|:---:|:---:|:---:|:---:|:---:|:---:|
 | **ServiceBus** | Azure Service Bus traffic. | Outbound | Yes | Yes |
 
-
 > [!NOTE]
-> Service Bus service tags include the IP addresses of namespaces on all SKUs, however, using service tags with private or service endpoints for Service Bus is only supported on **premium** namespaces. If you are using a **standard** namespace, use the FQDN of the namespace instead, in the form of <contoso.servicebus.windows.net>. Alternatively you can use the IP address that you see when you run the following command: `nslookup <host name for the namespace>`, however this is not recommended or supported, and you will need to keep track of changes to the IP addresses. 
+Previously, Service Bus service tags included only the IP addresses of namespaces on the **premium** SKU. This has now been updated to include the IP addresses of **all namespaces**, regardless of the SKU.
 
 ## IP firewall 
 By default, Service Bus namespaces are accessible from internet as long as the request comes with valid authentication and authorization. With IP firewall, you can restrict it further to only a set of IPv4 addresses or IPv4 address ranges in [CIDR (Classless Inter-Domain Routing)](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation.