Build Event Hub namespace and event hub configurations with capture and consumer groups.
Last verified: May 2026
Build Event Hub namespace and consumer group configs with partitioning, capture, and network rules.
Required Fields
namespaceNameresourceGroupsku.nameeventHubseventHubs[0].nameeventHubs[0].partitionCountOutput will appear here...Your team is building a clickstream analytics pipeline expecting 50K events/sec peak, 10K avg. The builder generates: Standard tier namespace with 5 TUs (auto-inflate to 20), event hub with 32 partitions, capture enabled to ADLS Gen2 in Avro format with 5-min/100MB rollover, 4 consumer groups (real-time dashboard, fraud detection, ML feature store, archival). The architecture supports parallel processing across all 4 consumers without affecting each other; capture provides the 'replay last 30 days' capability needed for ML model retraining.
Azure Event Hubs is a fully managed real-time data ingestion service capable of receiving millions of events per second from any source. Configuration involves creating a namespace (the management container), defining event hubs within it with partition counts, setting consumer groups for parallel processing, and optionally enabling Capture to automatically stream events to Azure Blob Storage or Data Lake. The Event Hub Config Builder helps you define namespace settings, event hub properties, consumer groups, and Capture configurations for high-throughput streaming architectures.
The builder constructs Event Hub configurations: namespace (tier: Standard/Premium/Dedicated, throughput units or processing units, auto-inflate), event hub (partition count 1-32, message retention 1-7 days, capture config to Blob/ADLS), consumer groups (one per downstream consumer for independent positioning), and Schema Registry settings if used. Output is generated as az eventhubs commands and Terraform azurerm_eventhub_namespace + azurerm_eventhub resources.
Partition count is PERMANENT in Standard tier — you cannot increase or decrease after creation. Premium and Dedicated tiers support increase only (still no decrease). Always over-provision partitions at creation. A common pattern: provision 32 partitions on day 1 even if you only need 4, leaving room for future consumer parallelism.
Capture is the killer feature for analytics. Enable it to automatically stream events to Blob Storage or ADLS Gen2 in Avro format — no separate consumer code needed. Use this for compliance archives, cold-path analytics, or as a replay buffer for ML training data.
Premium tier is dramatically more expensive than Standard but includes processing unit isolation and supports messages up to 1 MB (vs Standard's 256 KB). The break-even is roughly when you have >5 TUs of Standard ingestion AND need data residency or larger messages. Below that, Standard is the right choice.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.