Azure Event Hubs Pricing Concepts

Understanding the pricing model for Azure Event Hubs is crucial for cost management and resource optimization. Event Hubs pricing is primarily based on the volume of data processed and the provisioned throughput units (TUs) or processing units (PUs).

Key Pricing Components

1. Data Ingestion and Egress

This is the most fundamental aspect of Event Hubs pricing. You are charged for the number of incoming events (ingress) and outgoing events (egress) that are processed by your Event Hubs namespace.

Pricing is typically per 1 million events. Event Hubs compresses data before it's stored, so the billable size might be less than the actual transmitted size.

2. Throughput Units (TUs) / Processing Units (PUs)

When using the Standard or Premium tiers, you provision throughput units (or processing units for Premium) that define the maximum ingress and egress traffic capacity for your Event Hubs namespace per hour.

You are charged for the number of provisioned TUs/PUs, regardless of whether you fully utilize them.

3. Event Compression

Event Hubs can automatically compress events. This can significantly reduce the billable ingress and egress data volume, leading to cost savings. You can enable or disable compression.

4. Capture Feature

If you use the Event Hubs Capture feature to automatically archive events to Azure Blob Storage or Azure Data Lake Storage, you will incur charges for both Event Hubs (for the capture operation itself) and the destination storage service.

Pricing Tiers

Azure Event Hubs offers different tiers, each with distinct pricing characteristics:

Feature Basic Standard Premium
Primary Metric Data Ingress/Egress (per million events) Data Ingress/Egress (per million events) + Provisioned Throughput Units (per hour) Data Ingress/Egress (per million events) + Processing Units (per hour)
Throughput Automatic scaling, shared capacity Dedicated capacity per TU Dedicated capacity, predictable performance
Capture Feature Supported Supported Supported
Use Cases Development, testing, low-volume applications Production workloads, moderate to high throughput Mission-critical applications, predictable low latency, high throughput
Important: The Basic tier has limitations on ingress and egress, and it's generally not recommended for production workloads requiring guaranteed performance. The Standard and Premium tiers offer more control and scalability.

Example Scenario

Let's consider a scenario with the Standard tier:

Your estimated cost would involve:

  1. Cost of Provisioned TUs: (10 TUs/hour) * (730 hours) * (Price per TU per hour)
  2. Cost of Ingress Data: (500 million events / 1 million) * (Price per 1 million ingress events)
  3. Cost of Egress Data: (400 million events / 1 million) * (Price per 1 million egress events)

Remember to check the official Azure pricing calculator for the most up-to-date and accurate figures for your region and specific needs.

Cost Optimization Tips

For detailed pricing information, please refer to the Azure Event Hubs Pricing Page.