Standardize 'SKU' to 'tier' in Service Bus documentation

Author: EldertGrootenboerMS

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

@@ -11,13 +11,13 @@ ms.devlang: azurecli
 Service Bus partitions enable queues and topics, or messaging entities, to be partitioned across multiple message brokers. Partitioning means that the overall throughput of a partitioned entity is no longer limited by the performance of a single message broker. Partitioned queues and topics can contain all advanced Service Bus features, such as support for transactions and sessions. For more information, see [Partitioned queues and topics](service-bus-partitioning.md). This article shows you different ways to enable partitioning for a Service Bus Premium namespace. All entities in this namespace will be partitioned.
 
 > [!NOTE]
-> - Partitioning can be enabled during namespace creation in the Premium SKU.
+> - Partitioning can be enabled during namespace creation in the Premium tier.
 > - Creating non-partitioned entities in a partitioned namespace isn't allowed.
 > - Changing the partitioning option on any existing namespace isn't possible. The number of partitions can only be set during namespace creation.
 > - The number of assigned messaging units are always a multiplier of the number of partitions in a namespace, and are equally distributed across the partitions. For example, in a namespace with 16MU and 4 partitions, each partition is assigned 4MU.
 > - Using multiple partitions with lower messaging units (MU) gives you a better performance over a single partition with higher MUs.
 > - When using the Service Bus [Geo-disaster recovery](service-bus-geo-dr.md) feature, ensure not to pair a partitioned namespace with a non-partitioned namespace.
-> - It's not possible to [migrate](service-bus-migrate-standard-premium.md) a standard SKU namespace to a Premium SKU partitioned namespace.
+> - It's not possible to [migrate](service-bus-migrate-standard-premium.md) a Standard tier namespace to a Premium tier partitioned namespace.
 > - JMS is currently not supported on partitioned namespaces.
 > - Batching messages with distinct SessionId or PartitionKey isn't supported on partitioned namespaces.
 > - This feature is currently available in all regions except West India and Austria East.

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

@@ -26,7 +26,7 @@ You can use service tags to define network access controls on [network security
 | **ServiceBus** | Azure Service Bus traffic. | Outbound | Yes | Yes |
 
 > [!NOTE]
->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.
+>Previously, Service Bus service tags included only the IP addresses of namespaces on the **Premium** tier. This has now been updated to include the IP addresses of **all namespaces**, regardless of the tier.
 
 ## 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.

articles/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted.md

@@ -134,7 +134,7 @@ This section compares Storage queues and Service Bus queues from the perspective
 * With Storage queues, if the content of the message isn't XML-safe, then it must be **Base64** encoded. If you **Base64**-encode the message, the user payload can be up to 48 KB, instead of 64 KB.
 * With Service Bus queues, each message stored in a queue is composed of two parts: a header and a body. The total size of the message can't exceed the maximum message size supported by the service tier.
 * When clients communicate with Service Bus queues over the TCP protocol, the maximum number of concurrent connections to a single Service Bus queue is limited to 100. This number is shared between senders and receivers. If this quota is reached, requests for additional connections will be rejected and an exception will be received by the calling code. This limit isn't imposed on clients connecting to the queues using REST-based API.
-* To scale beyond 10,000 queues with Service Bus Standard Stock Keeping Unit (SKU) or 1000 queues/Messaging Unit with Service Bus Premium SKU, you can also create additional namespaces using the [Azure portal].
+* To scale beyond 10,000 queues with Service Bus Standard tier or 1000 queues/Messaging Unit with Service Bus Premium tier, you can also create additional namespaces using the [Azure portal].
 
 ## Management and operations
 This section compares the management features provided by Storage queues and Service Bus queues.

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

@@ -12,11 +12,11 @@ ms.devlang: csharp
 Azure Service Bus employs multiple message brokers to process messages and multiple messaging stores to store messages. A conventional queue or topic is handled by a single message broker and stored in one messaging store. Service Bus *partitions* enable queues and topics, or *messaging entities*, to be partitioned across multiple message brokers and messaging stores. Partitioning means that the overall throughput of a partitioned entity is no longer limited by the performance of a single message broker or messaging store. In addition, a temporary outage of a messaging store doesn't render a partitioned queue or topic unavailable. Partitioned queues and topics can contain all advanced Service Bus features, such as support for transactions and sessions.
 
 > [!NOTE]
-> There are some differences between the Basic / Standard and Premium SKU when it comes to partitioning.
-> - Partitioning is available at entity creation for all queues and topics in Basic or Standard SKUs. A namespace can have both partitioned and non-partitioned entities.
-> - Partitioning is available at namespace creation for the Premium messaging SKU, and all queues and topics in that namespace will be partitioned. Any previously migrated partitioned entities in Premium namespaces will continue to work as expected.
-> - When partitioning is enabled in the Basic or Standard SKUs, we will always create 16 partitions.
-> - When partitioning is enabled in the Premium SKU, the number of partitions is specified during namespace creation.
+> There are some differences between the Basic / Standard and Premium tiers when it comes to partitioning.
+> - Partitioning is available at entity creation for all queues and topics in Basic or Standard tiers. A namespace can have both partitioned and non-partitioned entities.
+> - Partitioning is available at namespace creation for the Premium tier, and all queues and topics in that namespace will be partitioned. Any previously migrated partitioned entities in Premium namespaces will continue to work as expected.
+> - When partitioning is enabled in the Basic or Standard tiers, we will always create 16 partitions.
+> - When partitioning is enabled in the Premium tier, the number of partitions is specified during namespace creation.
  
 It isn't possible to change the partitioning option on any existing namespace, queue, or topic; you can only set the option when you create the entity.
 
@@ -111,7 +111,7 @@ Service Bus supports automatic message forwarding from, to, or between partition
 Currently Service Bus imposes the following limitations on partitioned queues and topics:
 
 - Partitioned queues and topics don't support sending messages that belong to different sessions in a single transaction.
-- Service Bus currently allows up to 100 partitioned queues or topics per namespace for the Basic and Standard SKU. Each partitioned queue or topic counts towards the quota of 10,000 entities per namespace.
+- Service Bus currently allows up to 100 partitioned queues or topics per namespace for the Basic and Standard tiers. Each partitioned queue or topic counts towards the quota of 10,000 entities per namespace.
 
 ## Next steps
 You can enable partitioning by using Azure portal, PowerShell, CLI, Resource Manager template, .NET, Java, Python, and JavaScript. For more information, see [Enable partitioning (Basic / Standard)](enable-partitions-basic-standard.md).