Azure Service Bus Pricing and Features: Cloud Messaging Service

Azure Service Bus: Pricing and Features Guide

Azure Service Bus is a fully managed enterprise message broker. It decouples applications and services using queues and publish-subscribe topics. Service Bus supports advanced patterns: dead-lettering, sessions, scheduled messages, duplicate detection, and transactions. EPC Group architecats Service Bus solutions for healthcare, financial services, and government enterprises with HIPAA, SOC 2, and FedRAMP compliance. 29 years of Microsoft experience.

Key facts

• Messaging models: queues (point-to-point) and topics with subscriptions (publish-subscribe).
• Pricing: Basic tier ($0.05/million operations), Standard tier ($10/month base + $0.01/million), Premium tier (messaging units, dedicated capacity).
• Premium message size: up to 100 MB per message (vs. 256 KB on Standard).
• SLA: 99.9% for Standard. 99.99% for Premium (with geo-redundancy).
• Compliance: HIPAA, SOC 2, FedRAMP, GDPR via private endpoints and Entra ID.
• EPC Group: 29 years Microsoft consulting, 10,000+ enterprise deployments. HIPAA, SOC 2, FedRAMP architected.

What is Azure Service Bus?

Azure Service Bus is a fully managed cloud messaging service. It acts as a broker between applications — accepting messages from senders, storing them reliably, and delivering them to receivers.

Service Bus supports the messaging patterns that enterprise integration architectures require:

• Temporal decoupling — Sender and receiver do not need to be online at the same time.
• Load leveling — Messages queue up during peak demand. Consumers process at their own rate.
• Publish-subscribe — One sender, multiple topic subscriptions. Each subscription receives a copy of every message.
• Ordered delivery — FIFO delivery within message sessions. Required for order-sensitive workflows.
• Dead-letter queue — Undeliverable messages moved to a dead-letter subqueue for investigation and replay.

Azure Service Bus Pricing (2026)

Service Bus has three pricing tiers. The right tier depends on message size, throughput, and compliance requirements:

| Feature | Basic | Standard | Premium | |---|---|---|---| | Monthly base | $0 | $10 | Per messaging unit | | Operations | $0.05/million | $0.01/million | Included | | Max message size | 256 KB | 256 KB | 100 MB | | Topics (pub-sub) | No | Yes | Yes | | Dead-letter queue | No | Yes | Yes | | Sessions | No | Yes | Yes | | Private endpoints | No | No | Yes | | Geo-redundancy | No | No | Yes | | SLA | 99.9% | 99.9% | 99.99% |

Key Features

• Queues — Point-to-point messaging. Messages stored until the receiver is ready. Supports FIFO, duplicate detection, and at-least-once or exactly-once delivery.
• Topics and subscriptions — Publish-subscribe model. One message published to a topic, delivered to all active subscriptions. Subscriptions support filter rules.
• Sessions — Logical grouping of related messages. Ensures related messages are processed in order by the same consumer. Required for workflows with state.
• Scheduled messages — Delay message delivery until a future time. Common for reminder workflows and time-triggered processing.
• Duplicate detection — Configurable window for detecting and discarding duplicate messages. Common in financial transaction processing.
• Transactions — Atomic operations across multiple message sends and receives. Required for financial and order management workflows.
• Auto-forwarding — Automatically forward messages from one queue or subscription to another. Used to build message routing chains.

Azure Service Bus vs. Event Grid vs. Event Hubs

| Use case | Service Bus | Event Grid | Event Hubs | |---|---|---|---| | Enterprise messaging | Best | Adequate | Not designed for | | High-throughput streaming | Poor | Poor | Best | | Event-driven routing | Adequate | Best | Adequate | | FIFO ordering | Yes (sessions) | No | Partition-level | | Dead-letter | Yes | Yes | Yes | | Max message size | 256 KB / 100 MB | 1 MB | 1 MB | | Replay | No | No | Yes |

Compliance: HIPAA, SOC 2, FedRAMP

EPC Group has architected Service Bus solutions for healthcare systems processing millions of HIPAA-compliant transactions, financial services firms requiring SOC 2 audit trails, and government agencies under FedRAMP controls.

Key compliance controls for Service Bus:

• Private endpoints (Premium) — Service Bus Premium supports Azure Private Link. Keep all messaging traffic inside your VNet with no public internet exposure.
• Entra ID authentication — Managed identities for senders and receivers. No connection string credentials in code.
• Encryption at rest — All messages encrypted at rest with AES-256. Customer-managed keys (CMK) available.
• Audit logging — Service Bus activity logged to Azure Monitor. Required for SOC 2 and FedRAMP audit trails.
• Geo-redundancy (Premium) — Geo-disaster recovery pairs two Service Bus namespaces for business continuity.

Frequently asked questions

What is Azure Service Bus?

Azure Service Bus is a fully managed enterprise message broker. It decouples applications using queues (point-to-point) and topics with subscriptions (publish-subscribe). It supports FIFO ordering, dead-letter queues, sessions, transactions, and scheduled messages for complex enterprise workflows.

How much does Azure Service Bus cost?

Basic tier: $0.05/million operations. Standard tier: $10/month base plus $0.01/million operations. Premium tier: priced per messaging unit (dedicated capacity). Premium is required for private endpoints, 100 MB messages, and 99.99% SLA.

What is the difference between Service Bus queues and topics?

Queues are point-to-point: one sender, one receiver. Topics are publish-subscribe: one sender, multiple subscriptions (each acting as an independent receiver). Topics require Standard or Premium tier.

When should I use Service Bus vs. Event Grid?

Use Service Bus for reliable enterprise messaging: order processing, HIPAA-compliant transaction routing, financial workflows. Use Event Grid for reactive event notification: trigger Functions when a blob uploads, notify subscribers when a resource changes. Many architectures use both.

Does Azure Service Bus support HIPAA?

Yes. With Premium tier private endpoints, Entra ID managed identity authentication, AES-256 encryption at rest, customer-managed keys, and audit logging to Azure Monitor, Azure Service Bus supports HIPAA-compliant messaging architectures. EPC Group has deployed HIPAA-compliant Service Bus for major healthcare systems.

Design your enterprise messaging architecture

Talk to an EPC Group integration architect about Azure Service Bus design, compliance, and integration patterns. Call (888) 381-9725 or request a 30-minute discovery call.