> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/storage/appsec-azure-228.md).

# Azure Event Hub Namespace is not zone redundant misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_228        |
| Category - Subcategory | Storage - Redundancy      |
| Provider               | AZURE                     |
| Severity               | MEDIUM                    |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule is checking to ensure that an Azure Event Hub Namespace is set to be zone redundant. Zone redundancy means that data is replicated in multiple availability zones for backup and recovery purposes. If the Event Hub Namespace is not set to be zone redundant, it means that any localized glitch or failure in one zone could result in data loss or application unavailability, therefore leading to potential disruption in service. This can be extremely problematic, especially for mission-critical applications where continuous availability and data integrity are of utmost importance. To prevent this risk, it's essential to ensure redundancy across multiple zones.

## How to Fix

*Resource:* azurerm\_eventhub\_namespace

* *Arguments:* zone\_redundant

## Make the Azure Event Hub Namespace zone redundant. \[source,go]

resource "azurerm\_eventhub\_namespace" "example" { name = "example-namespace" location = "West US 2" resource\_group\_name = azurerm\_resource\_group.example.name sku = "Standard"

* zone\_redundant = true }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/storage/appsec-azure-228.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.