Azure Event Hubs cost: throughput units vs Premium and Dedicated

Quick answer

Event Hubs Standard bills per throughput unit by the hour plus a small charge per million ingress events; each throughput unit allows about 1 MB/s in. Premium and Dedicated allocate reserved processing capacity at a higher fixed cost for large, steady streams. Size throughput units to real peak: too few throttles, too many overpays.

Azure Event Hubs ingests high-throughput event streams. On the Standard tier its cost has two parts: reserved throughput capacity and the events you ingest. Getting the capacity right is the whole game.

Throughput units set the capacity and the floor

A throughput unit allows roughly 1 MB per second or 1,000 events per second of ingress, and a proportional egress. You reserve throughput units by the hour and pay for them whether or not the stream is busy, so they are your cost floor. Auto-inflate can raise units under load, but the baseline you set is what you pay most hours.

Ingress events

Dimension	Rate (approximate)
Throughput unit (Standard)	Per unit, hourly
Ingress events	Per million events
Premium / Dedicated	Reserved capacity, higher fixed cost

Sizing throughput units

Under-provision and events are throttled, which backs up producers and breaks the pipeline. Over-provision and you pay for capacity you never use. Size to real peak ingress plus margin, enable auto-inflate to handle spikes, and set its maximum so a burst cannot scale cost without bound, the same cost-versus-headroom balance as autoscaling.

When to move to Premium or Dedicated

Premium and Dedicated allocate isolated, reserved capacity for large, steady, latency-sensitive streams, at a higher fixed cost. They are worth it when Standard throughput units would need to be numerous and constant anyway, or when isolation and predictable performance are required. For variable or moderate streams, Standard with sized throughput units is cheaper.

FAQ

How is Azure Event Hubs priced?

On Standard, per throughput unit by the hour (each allowing about 1 MB/s or 1,000 events/s ingress) plus a charge per million ingress events. Premium and Dedicated allocate reserved processing capacity at a higher fixed cost for large, steady streams.

What is a throughput unit in Event Hubs?

A unit of reserved capacity allowing roughly 1 MB per second or 1,000 events per second of ingress. You pay per throughput unit by the hour whether the stream is busy or idle, so it is your cost floor on the Standard tier.

How do I size Event Hubs throughput units?

Size to real peak ingress plus margin. Too few throttles events and backs up producers; too many wastes reserved capacity. Enable auto-inflate to handle spikes and cap its maximum so a burst cannot scale cost without bound.

When should I use Event Hubs Premium or Dedicated?

For large, steady, latency-sensitive streams where you would otherwise reserve many constant throughput units, or where isolation and predictable performance are required. For moderate or variable streams, Standard with sized throughput units is cheaper.

How do I reduce Event Hubs cost?

Right-size throughput units to real peak, use auto-inflate with a capped maximum instead of over-reserving, batch events to reduce per-event overhead, and choose Standard over Premium unless the scale or isolation genuinely requires it.

Does C3X estimate Event Hubs cost?

C3X prices the azurerm_eventhub_namespace and its SKU and capacity from your Terraform, so throughput-unit cost appears before deploy. Ingress event volume is a usage assumption you provide.

What to do next

Size your stream before you deploy it. C3X reads your Terraform and prices Event Hubs and the rest of your stack against a live catalog. Start with the quickstart.