How do I choose the right number of partitions?

Partitions determine the maximum downstream parallelism — each partition can have at most one active consumer per consumer group. The number of partitions should match (or exceed) your expected number of parallel consumers. Start with the number of concurrent processing functions or threads you plan to run. Partitions cannot be reduced after creation (only increased in Premium/Dedicated tiers), so err on the higher side. For most workloads, 4-32 partitions are sufficient. Event Hubs supports up to 32 partitions in Standard tier and up to 100 in Premium tier.

What is the difference between Standard, Premium, and Dedicated tiers?

Standard tier uses throughput units (TUs) — each TU provides 1 MB/s ingress and 2 MB/s egress. Premium tier uses processing units (PUs) that include compute isolation, larger message sizes (1 MB vs 256 KB), and no TU management. Dedicated tier provides single-tenant clusters with the highest throughput and capacity guarantees. Standard is cost-effective for most workloads. Premium adds data residency, private networking, and larger messages. Dedicated is for extreme throughput requirements or strict isolation mandates.

Event Hub Config Builder

ServerlessAzure

Build Event Hub namespace and event hub configurations with capture and consumer groups.

Event Hubs Configuration

Build Event Hub namespace and consumer group configs with partitioning, capture, and network rules.

Required Fields

namespaceNameresourceGroupsku.nameeventHubseventHubs[0].nameeventHubs[0].partitionCount

{
  "namespaceName": "evhns-telemetry-prod",
  "resourceGroup": "rg-messaging",
  "location": "eastus2",
  "sku": {
    "name": "Standard",
    "tier": "Standard",
    "capacity": 2
  },
  "properties": {
    "isAutoInflateEnabled": true,
    "maximumThroughputUnits": 10,
    "kafkaEnabled": true,
    "zoneRedundant": true,
    "minimumTlsVersion": "1.2",
    "publicNetworkAccess": "SecuredByPerimeter",
    "disableLocalAuth": true
  },
  "eventHubs": [
    {
      "name": "telemetry-events",
      "partitionCount": 8,
      "messageRetentionInDays": 7,
      "captureDescription": {
        "enabled": true,
        "encoding": "Avro",
        "intervalInSeconds": 300,
        "sizeLimitInBytes": 314572800,
        "destination": {
          "name": "EventHubArchive.AzureBlockBlob",
          "storageAccountResourceId": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-data/providers/Microsoft.Storage/storageAccounts/sttelemetryarchive",
          "blobContainer": "telemetry-capture",
          "archiveNameFormat": "{Namespace}/{EventHub}/{PartitionId}/{Year}/{Month}/{Day}/{Hour}/{Minute}/{Second}"
        }
      },
      "consumerGroups": [
        {
          "name": "cg-stream-analytics",
          "userMetadata": "Stream Analytics real-time processing"
        },
        {
          "name": "cg-databricks",
          "userMetadata": "Databricks batch processing pipeline"
        },
        {
          "name": "cg-function-alerts",
          "userMetadata": "Azure Functions anomaly detection"
        }
      ]
    },
    {
      "name": "audit-events",
      "partitionCount": 4,
      "messageRetentionInDays": 14,
      "consumerGroups": [
        {
          "name": "cg-compliance",
          "userMetadata": "Compliance and audit log processing"
        }
      ]
    }
  ],
  "authorizationRules": [
    {
      "name": "send-telemetry",
      "rights": ["Send"]
    },
    {
      "name": "listen-analytics",
      "rights": ["Listen"]
    }
  ],
  "networkRuleSet": {
    "defaultAction": "Deny",
    "trustedServiceAccessEnabled": true,
    "virtualNetworkRules": [
      {
        "subnetId": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-networking/providers/Microsoft.Network/virtualNetworks/vnet-app/subnets/snet-eventhub"
      }
    ]
  }
}

Generated Output

Output will appear here...

About This Tool

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.

When to Use This Tool

•Configuring Event Hub namespaces with the right throughput units or processing units for expected ingestion rates
•Setting up event hubs with optimal partition counts for downstream consumer parallelism
•Building Capture configurations that automatically archive events to Blob Storage in Avro format for batch analytics
•Defining consumer groups for multiple downstream applications that independently process the same event stream

Frequently Asked Questions

How do I choose the right number of partitions?: Partitions determine the maximum downstream parallelism — each partition can have at most one active consumer per consumer group. The number of partitions should match (or exceed) your expected number of parallel consumers. Start with the number of concurrent processing functions or threads you plan to run. Partitions cannot be reduced after creation (only increased in Premium/Dedicated tiers), so err on the higher side. For most workloads, 4-32 partitions are sufficient. Event Hubs supports up to 32 partitions in Standard tier and up to 100 in Premium tier.
What is the difference between Standard, Premium, and Dedicated tiers?: Standard tier uses throughput units (TUs) — each TU provides 1 MB/s ingress and 2 MB/s egress. Premium tier uses processing units (PUs) that include compute isolation, larger message sizes (1 MB vs 256 KB), and no TU management. Dedicated tier provides single-tenant clusters with the highest throughput and capacity guarantees. Standard is cost-effective for most workloads. Premium adds data residency, private networking, and larger messages. Dedicated is for extreme throughput requirements or strict isolation mandates.

Related Learning Guides

Service Bus vs Event Grid vs Event Hubs24 min read

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.