Skip to content

Use zone redundant Event Hub namespaces#

Reliability · Event Hub · Rule · 2025_12 · Important

Use zone redundant Event Hub namespaces in supported regions to improve reliability.

Description#

Azure Event Hubs supports zone redundancy to provide enhanced resiliency and high availability. When zone redundancy is enabled, Event Hubs automatically replicates namespace metadata and event data across multiple availability zones within a region.

Availability zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. This physical separation protects your Event Hubs namespace from zone-level failures, ensuring continuous availability even if an entire availability zone experiences an outage.

With zone redundancy enabled, Azure Event Hubs provides:

  • Synchronous replication of metadata and events across zones.
  • Continuous availability during zonal failures.
  • Protection against datacenter-level disasters while maintaining low-latency access.

Zone redundancy must be configured when you create an Event Hub namespace by setting zoneRedundant to true. This setting cannot be changed after the namespace is created. Zone redundancy is only available in regions that support availability zones.

Recommendation#

Consider using using a minimum of Standard Event Hub namespaces configured with zone redundancy to improve workload resiliency.

Examples#

Configure with Azure template#

To deploy Event Hub namespaces that pass this rule:

  • Set the properties.zoneRedundant property to true.

For example:

Azure Template snippet
{
  "type": "Microsoft.EventHub/namespaces",
  "apiVersion": "2024-01-01",
  "name": "[parameters('name')]",
  "location": "[parameters('location')]",
  "sku": {
    "name": "Standard",
    "tier": "Standard"
  },
  "properties": {
    "disableLocalAuth": true,
    "minimumTlsVersion": "1.2",
    "zoneRedundant": true
  }
}

Configure with Bicep#

To deploy Event Hub namespaces that pass this rule:

  • Set the properties.zoneRedundant property to true.

For example:

Azure Bicep snippet
resource eventHubNamespace 'Microsoft.EventHub/namespaces@2024-01-01' = {
  name: name
  location: location
  sku: {
    name: 'Standard'
    tier: 'Standard'
  }
  properties: {
    disableLocalAuth: true
    minimumTlsVersion: '1.2'
    zoneRedundant: true
  }
}

Configure with Azure Verified Modules

A pre-validated module supported by Microsoft is available from the Azure Bicep public registry. To reference the module, please use the following syntax:

br/public:avm/res/event-hub/namespace:<version>

To use the latest version:

br/public:avm/res/event-hub/namespace:0.9.1

Notes#

Availability zones is supported on Standard, Premium, and Dedicated tiers.

For the Dedicated tier, availability zones require a minimum of three capacity units (CUs).

Comments