350+ Tools CoveredSource Data Updated Weeklydates

Azure Event Hubs Pricing: Basic, Standard, Premium and Dedicated Tiers

By Egor Burlakov · Edited · Source dates below

Price snapshot

Azure Event Hubs is Microsoft's managed service for real-time event ingestion, with an endpoint that lets existing Apache Kafka clients connect without code changes. Microsoft lists no upfront cost and no termination fees. Rates below are Microsoft's US dollar estimates; actual prices may vary by agreement, purchase date and exchange rate.

Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.

Azure Event Hubs published capacity and ingress rates by tier (USD)

TierCapacity rateIngress events

Basic

$0.015 per hour per Throughput Unit

$0.028 per million events

Standard

$0.03 per hour per Throughput Unit

$0.028 per million events

Premium

$1.233 per hour per Processing Unit (PU)

Included

Dedicated

$6.849 per hour per Capacity Unit (CU); one-hour increments, four-hour minimum charge

Included

Which tier fits

  • Basic suits short-lived streams: retention is capped at 1 day, and Apache Kafka, Schema Registry and archiving to storage are not available. Self-serve capacity stops at 20 Throughput Units.

  • Standard adds Kafka, Schema Registry and up to 7 days of retention. Archiving to storage costs extra. Same 20-unit self-serve cap; a support ticket can raise it to 40.

  • Premium fits when you need retention up to 90 days, archiving included, or geo-replication, which Basic and Standard lack.

  • Dedicated is Microsoft's suggestion once a workload needs more than 40 Throughput Units.

Plan details

Show full plan details

Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.

Azure Event Hubs retention, storage and feature availability by tier

ItemBasicStandardPremiumDedicated

Max retention period

1 day

7 days

90 days

90 days

Included storage

84 GB per Throughput Unit

84 GB per Throughput Unit

1 TB per PU; extra at $0.12 per GB per month

10 TB per CU; extra at $0.12 per GB per month

Capture (archiving to storage)

Not available

$73 per month per Throughput Unit, billed hourly per purchased unit; unit changes apply in whole-hour steps

Included

Included

Apache Kafka and Schema Registry

Not available

Available

Available

Available

Geo-replication data transfer (optional)

Not available

Not available

$0.09 per GB (Zone 1: North America and Europe), $0.12 per GB (Zone 2: Asia, Oceania, Middle East, Africa), $0.23 per GB (Zone 3: South America)

$0.09 per GB (Zone 1), $0.12 per GB (Zone 2), $0.23 per GB (Zone 3)

  • Vendor source · Observed · Stored official pricing capture for azure-event-hubs.
  • Vendor source · Observed · Stored official pricing capture for azure-event-hubs.
  • Vendor source · Observed · Stored official pricing capture for azure-event-hubs.

How billing works

  • Throughput Units (Basic, Standard). You choose the count per namespace. Each unit gives up to 1 MB per second ingress (no more than 1,000 ingress events per second) and up to 2 MB per second egress. Billing is hourly, on the highest number of units selected in that hour.

  • Ingress events (Basic, Standard). An event is 64 KB or less; larger messages are billed in multiples of 64 KB, so a 96 KB message counts as two events. Consumed events and checkpoints are not billable ingress, but use the Throughput Unit allowance.

  • Partitions. There is no fixed charge for partitions.

Worked examples

Microsoft's own geo-replication example for Premium: with 2 Processing Units in the primary region, one secondary, and 100 GB replicated between West US and East US, the charge is (1 × 2 × hourly rate) + (100 × $0.09). For Dedicated, with a 2 CU cluster in each region and 100 GB replicated, the extra geo-replication charge is 100 × $0.09 = $9, and each cluster is billed separately.

Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.

Hypothetical examples from published USD rates, assuming a 730-hour month

CaseWorking and result

Standard, 2 Throughput Units, 100 million events

2 TUs × $0.03 per hour × 730 hours = $43.80 per month, plus 100 × $0.028 per million events = $2.80; before archiving, extra storage and AMQP connection charges

Archiving on that Standard namespace

2 TUs × $73 per month = $146 per month, before charges on your own storage account

Premium, 1 Processing Unit

1 PU × $1.233 per hour × 730 hours = $900.09 per month, ingress included; before storage above 1 TB and geo-replication

Dedicated, 1 CU used for one hour

Four-hour minimum: 4 hours × $6.849 per hour = $27.40, before storage above 10 TB and geo-replication

What drives the bill

  • Peak load. On Basic and Standard, traffic above the Throughput Unit allowance is throttled.

  • Retention. Stored events above the included allowance are charged; on Standard, excess storage is billed at the locally redundant Azure blob storage rate, measured as the daily peak.

Costs to watch

  • AMQP connections. HTTPS sends have no connection charge. AMQP is metered after the first 100 concurrent connections per Basic namespace or the first 1,000 per subscription on Standard, at Service Bus Connections rates. Dedicated has no separate brokered connection charge.

  • Archive storage. Archiving writes to your own storage account, billed to your subscription; a shorter window means more storage transactions.

  • Capacity above 20 TUs. Microsoft does not guarantee immediate availability above 20 TUs per subscription.

Our take

If your stream fits a few Throughput Units and 7 days of retention, price Standard, with archiving as the main add-on. Microsoft offers a $200 credit to explore Azure for 30 days.

Evaluate this price

Sources