Enable partitioning for an Azure Service Bus Premium namespace (Preview)

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. In addition, a temporary outage of a message broker, for example during an upgrade, 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. For more information, see Partitioned queues and topics. This article shows you different ways to enable duplicate partitioning for a Service Bus Premium namespace. All entities in this namespace will be partitioned.


This feature is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.


  • This feature is currently available only in the East US and North Europe regions, with other regions being added during the public preview.
  • Partitioning is available at entity creation for namespaces in the Premium SKU. Any previously existing partitioned entities in Premium namespaces continue to work as expected.
  • It's not possible to change the partitioning option on any existing namespace. You can only set the option when you create a namespace.
  • The assigned messaging units are always a multiplier of the amount of partitions in a namespace, and are equally distributed across the partitions. For example, in a namespace with 16MU and 4 partitions, each partition will be assigned 4MU.
  • Multiple partitions with lower messaging units (MU) give you a better performance over a single partition with higher MUs.

Some limitations may be encountered during public preview, which will be resolved before going into GA.

  • It is currently not possible to use JMS on partitioned entities.
  • Metrics are currently only available on an aggregated namespace level, not for individual partitions.

Use Azure portal

When creating a namespace in the Azure portal, set the Partitioning to Enabled and choose the number of partitions, as shown in the following image. Screenshot of screen where partitioning is enabled at the time of the namespace creation.

Use Azure Resource Manager template

To create a namespace with partitioning enabled, set partitions to a number larger than 1 in the namespace properties section. In the example below a partitioned namespace is created with 4 partitions, and 1 messaging unit assigned to each partition. For more information, see Microsoft.ServiceBus namespaces template reference.

  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "",
  "parameters": {
    "serviceBusNamespaceName": {
      "type": "string",
      "metadata": {
        "description": "Name of the Service Bus namespace"
    "location": {
      "type": "string",
      "defaultValue": "[resourceGroup().location]",
      "metadata": {
        "description": "Location for all resources."
  "resources": [
      "type": "Microsoft.ServiceBus/namespaces",
      "apiVersion": "2022-10-01-preview",
      "name": "[parameters('serviceBusNamespaceName')]",
      "location": "[parameters('location')]",
      "sku": {
        "name": "Premium",
        "capacity": 4      
      "properties": {
        "premiumMessagingPartitions": 4

Next steps

Try the samples in the language of your choice to explore Azure Service Bus features.