Azure Event Hubs

About Azure Event Hubs

Azure Event Hubs is Microsoft Azure's fully managed real-time event streaming and ingestion service for workloads that need to receive, retain and process large volumes of telemetry, logs, clickstreams and application events. It uses partitioned event streams so producers and consumers can scale independently, and it supports native Event Hubs clients plus Apache Kafka protocol compatibility. Event Hubs is strongest when the requirement is high-throughput event ingestion and replay rather than durable command queues or simple event notification.

What is Azure Event Hubs used for?

Azure Event Hubs is designed for high-volume event ingestion. Common scenarios include IoT telemetry, application logs, clickstream analytics, security events, financial event streams, operational monitoring and real-time data pipelines. Microsoft describes the service as capable of ingesting millions of events per second with low latency, while consumers can process the stream independently through partitions and consumer groups.

The service acts as a time-retained event buffer rather than a traditional message queue. Producers send events continuously and consumers read from the retained stream at their own pace. This makes Event Hubs useful when several analytics or processing applications need the same stream, when consumers need to replay retained events, or when the ingestion rate is much higher than a downstream system can process immediately.

How do partitions and consumer groups work?

An event hub is split into partitions. Each partition is an ordered append-only sequence of events, and producers can use partition keys when events with the same key need to stay together. More partitions allow more parallel processing, but partition count also becomes part of the long-term design because ordering is only guaranteed inside a partition.

Consumer groups give different applications independent views of the same event stream. Each consumer application can track its own position in every partition without preventing another application from reading the same events. This is useful when one stream feeds several systems, such as real-time analytics, fraud detection and long-term storage. Teams should plan partitions around expected throughput and parallelism rather than simply choosing the largest number available.

How do Basic, Standard, Premium and Dedicated tiers differ?

Microsoft currently documents Basic, Standard, Premium and Dedicated Event Hubs tiers. Basic is the most limited option and does not support Apache Kafka workloads or Capture. Standard adds Kafka compatibility, more consumer groups and longer retention. Premium provides reserved processing capacity, stronger isolation, higher partition and consumer-group limits, longer retention and availability-zone support where available. Dedicated provides single-tenant capacity for the highest-scale streaming workloads.

Current Microsoft limits also differ by tier. Basic supports one day of retention, Standard up to seven days, and Premium and Dedicated up to 90 days. Maximum event publication size is 256 KB in Basic, 1 MB in Standard and Premium, and 20 MB in Dedicated. Buyers should confirm the exact tier limits before production because retention, event size, connection counts, partitions and scaling capacity differ materially.

How does Event Hubs pricing and capacity work?

Event Hubs does not have one fixed monthly price. Microsoft prices the service according to the selected tier and capacity model. Basic and Standard use throughput units, Premium uses processing units, and Dedicated uses capacity units. Additional meters can apply to features such as Capture in Standard, while Capture is included in Premium and Dedicated. Pricing was checked against Microsoft's current Event Hubs pricing page on August 25, 2026.

For Basic and Standard, Microsoft currently documents each throughput unit with up to 1 MB per second or 1,000 events per second of ingress and up to 2 MB per second or 4,096 events per second of egress. Premium and Dedicated use reserved capacity models rather than the same per-unit throughput ceiling. Teams should estimate incoming event size, events per second, consumer egress, retention, partitions and Capture requirements together because all can affect capacity and cost.

What does Apache Kafka compatibility mean?

Event Hubs exposes an Apache Kafka endpoint so many Kafka producer and consumer applications can connect without running a Kafka cluster. Microsoft documents support for Kafka protocol clients and positions this as a way to keep familiar Kafka APIs while Azure manages the streaming infrastructure.

Kafka compatibility should still be tested against the application's exact features. Event Hubs and self-managed Apache Kafka are conceptually similar but not identical. Teams should verify protocol versions, authentication, partition behavior, consumer-group semantics and any broker-specific features their application relies on. Organizations that need full control of Kafka brokers, storage layout or Kafka-specific platform behavior may prefer a managed Kafka service or their own Kafka deployment.

How does Event Hubs Capture work?

Event Hubs Capture automatically writes streaming events to Azure Blob Storage or Azure Data Lake Storage for long-term retention and batch processing. Microsoft documents configurable time or size windows for Capture, allowing the same incoming stream to feed both real-time consumers and a storage-based cold path without a separate custom ingestion service.

Capture does not replace Event Hubs retention. Event Hubs remains the short-term streaming buffer, while Capture writes copies to storage for longer-lived analytics or archival use. Microsoft states that Standard charges separately for Capture according to throughput units, while Premium and Dedicated include the feature. Teams should also check the destination storage account, file format and downstream processing design before treating Capture as a complete data-lake architecture.

How does Event Hubs compare with Service Bus and Event Grid?

Azure Event Hubs is optimized for high-throughput streams of events that consumers may replay. Azure Service Bus is designed for durable business messaging, commands, queues, transactions, sessions and brokered delivery semantics. Azure Event Grid is designed for event notification and routing, where publishers emit discrete events and subscribers react to them.

A useful rule is to start with the communication pattern. Telemetry, logs and clickstreams usually point toward Event Hubs. Reliable work queues and business commands usually point toward Service Bus. Lightweight notifications that trigger handlers across Azure services often fit Event Grid. These services can be combined, but buyers should not use Event Hubs as a generic replacement for every messaging requirement.

What are the main limitations and tradeoffs?

Event Hubs gives teams a managed streaming platform, but application architecture still matters. Poor partition-key choices can create uneven load, too few partitions can restrict parallelism, and too many consumers or oversized events can run into tier quotas. Retention is finite, so applications that need durable historical storage should use Capture or another storage pipeline.

The service also does not process or analyze events by itself. Teams still need consumers such as Azure Functions, Stream Analytics, Azure Data Explorer, Spark or custom applications. Monitoring consumer lag, checkpointing, authentication, network access and replay behavior remains an application responsibility. Premium or Dedicated can improve isolation and scale, but they increase cost and may be unnecessary for smaller streams.

Who should choose something else?

Teams that mainly need reliable business commands, transactions, ordered work queues or dead-letter handling should compare Azure Service Bus. Applications that only need event notification and routing may find Event Grid simpler. Organizations that require deep control of Kafka brokers or Kafka-specific platform features should compare a managed Kafka platform or self-managed Kafka rather than assuming Event Hubs is identical.

Azure Event Hubs is strongest when the workload genuinely needs sustained high-throughput ingestion, partitioned event streams, multiple independent consumers, replay within a retention window and Azure-native integration. Buyers should choose it because the streaming model fits the workload, not simply because events are involved.