Azure Service Bus Pricing by Tier

Azure Service Bus pricing depends on the tier. Basic bills per operation and gives you queues only. Standard adds topics, sessions, transactions and duplicate detection for a small base charge plus tiered per-operation and brokered connection charges. Premium sells dedicated messaging units by the hour, with no per-operation or connection charges, and is the only tier with 100 MB messages, private endpoints, JMS 2.0 and Geo-Replication.

The figures below are the US dollar list prices on Microsoft Service Bus pricing page as checked in October 2026. Microsoft states that prices vary by region, currency, agreement type and purchase date, so treat the numbers as a model and confirm them in the Azure pricing calculator for your region. This guide covers what each tier charges for, which features force Premium, and how to estimate a bill before you build.

An operation is any API call: send, receive, complete, lock renewal, and management calls such as listing a queue. A message up to 64 KB is one operation per call, and larger messages count in multiples of 64 KB. A message that is sent, received and completed costs three operations. Redeliveries after an abandon, defer or dead-letter count again, and a message fanned out to three topic subscriptions costs one send plus three receives. A brokered connection is an AMQP connection or an HTTP receive with a non-zero timeout, charged on the hourly peak of concurrent connections.

You choose 1, 2, 4, 8 or 16 messaging units per namespace, and Microsoft bills hourly on the highest number allocated in each hour. If you scale up for ten minutes you pay for the extra units for the full hour, and scaling back down inside the hour does not reduce that hour's charge. One MU runs around the clock whether or not it is busy. With Geo-Replication, the cost is the number of replicas times the MUs on the primary times hours times the hourly rate, plus the GB replicated at the data transfer rate for the primary's zone.

For sizing, Microsoft suggests starting with one or two MUs, or one per partition, then watching the namespace's CPU and memory metrics: scale down below 25% CPU, scale up above 75% CPU, and scale up when memory passes 60%, because memory use can rise quickly. The pricing page's FAQ still describes a daily rate and 1, 2 or 4 MUs, which is out of date against the table and the Premium documentation; use the hourly rate and the five sizes.

• Private networking. Service tags, virtual network service endpoints and private endpoints are Premium only. Configuring the IP firewall in the portal is also Premium only, though other tiers can set it with templates, the CLI or the API.
• Large messages. Up to 100 MB, over AMQP only; Basic and Standard stop at 256 KB. Large messages lower throughput and raise latency.
• JMS 2.0. Premium supports JMS 1.1 and 2.0; Standard supports a JMS 1.1 subset focused on queues.
• Geo-Replication of metadata and message data to a secondary region, and customer-managed encryption keys.
• Predictable latency. Microsoft's own comparison describes Standard as variable throughput with variable latency and Premium as predictable performance on isolated CPU and memory.

Availability zone support is listed as available in all three tiers on the pricing page, so it no longer pushes you to Premium.

1. Count messages and consumers. Operations per message = 1 send + 1 receive + 1 complete, plus one more receive per extra subscription, plus retries and lock renewals.
2. Split features from volume. If you need private endpoints or messages over 256 KB, the price question is how many MUs, not which tier.
3. Price Standard. At 100 million operations a month, the base charge of about $9.86 plus 87 million operations at $0.80 per million is about $79, before connection charges. The same volume on Basic would be $5, if you can live without topics.
4. Find the crossover. On the list prices above, one MU at about $677 a month equals Standard at roughly 1.3 billion operations a month. At three operations per message, that is about 430 million messages, or around 165 messages a second sustained. Below that, Standard is cheaper unless a feature forces Premium; above it, Premium is cheaper and adds isolation.
5. Add the quiet costs: polling receivers that return empty (each call is an operation), thousands of AMQP clients, messages just over 64 KB that double the operation count, and Geo-Replication transfer.

These are list prices, not quotes. Enterprise agreements and reservations change them.

Azure Event Hubs is cheaper for streaming, not a drop-in for queues. Its Standard tier lists $0.03 per throughput unit per hour (about $22 a month) plus $0.028 per million ingress events, Premium lists $1.233 per processing unit per hour, and a Kafka endpoint is included from Standard up, with 7-day retention on Standard and 90 days on Premium. It has no per-message settlement, dead-lettering or sessions, so use it for telemetry and event streams and keep Service Bus for commands and workflows. Our Kafka use cases guide covers when a log beats a queue.

Self-hosted RabbitMQ has no per-operation or per-connection charge. You pay for nodes (typically three), storage, cross-zone traffic and the engineers who patch and upgrade it, and commercial support is a separate line. It tends to win at high sustained volume, or when needing Premium-only features (isolation, large messages, private networking) pushes Service Bus to Premium. It rarely wins at low volume, where Basic or Standard costs tens of dollars. Our RabbitMQ vs Azure Service Bus comparison covers control, latency and compliance beyond cost, RabbitMQ on Azure hosting options the ways to run it, and our cost comparison assessment how we frame the numbers. AceMQ's RabbitMQ support covers the self-hosted route.

AceMQ's Azure Service Bus support engineers size tiers and messaging units from real traffic, find the operations driving a Standard bill, and take the call when throttling, lock errors or networking problems hit production.

• Microsoft Azure: Service Bus pricing
• Microsoft Azure: pricing calculator for Service Bus
• Microsoft Learn: Service Bus premium messaging tier
• Microsoft Learn: Service Bus network security
• Microsoft Learn: Service Bus Geo-Replication
• Microsoft Azure: Event Hubs pricing