Today we are excited to announce the general availability of Geo-Replication on partitioned namespaces for Azure Service Bus Premium. You can now combine the throughput benefits of partitioning with the reliability of replicating your messages and metadata to a secondary Azure region.

Throughput and reliability in the same namespace

Large messaging workloads can need more than the 16 messaging units available in a non-partitioned Premium namespace. Partitioned namespaces distribute queues and topics across multiple message brokers and messaging stores within a region, so throughput is no longer limited to a single broker.

These applications depend on the messages Service Bus holds as well as the capacity it provides. Messages waiting in queues and subscriptions represent work that has been accepted but not yet completed. To continue that work in another region, applications need the messages and their processing state, along with the queues, topics, and subscriptions.

Geo-Replication replicates this data and configuration to a secondary region, so applications can resume processing replicated messages there when they need to move the workload. With this support now generally available on partitioned namespaces, large workloads can use both capabilities in the same namespace: the capacity to handle their message volume and replication of the work they still need to process.

Getting started

If you already use a partitioned Premium namespace, you can configure Geo-Replication on that namespace, including its existing queues and topics.

For a new namespace, select Premium and enable Partitioning during namespace creation, then configure Geo-Replication. The partitioning setting cannot be changed on an existing namespace.

To enable Geo-Replication on your partitioned namespace, follow the setup guidance.