> 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-233.md).

# Azure Container Registry (ACR) not zone redundant misconfiguration detected in code

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_233                    |
| Category - Subcategory | Storage - Redundancy                  |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |

## Impact

This rule checks to ensure that the Azure Container Registry (ACR) is zone redundant, ensuring resource distribution across multiple zones within the same region. Zone redundancy is important as it guarantees high availability and resilience during zone-wide failures. Without zone redundancy, ACR may experience unavailability during zone-specific issues occur, disrupting services relying on it and potentially leading to substantial business disruptions.

## How to Fix

*Resource:* azurerm\_container\_registry

* *Arguments:* zone\_redundancy\_enabled

To fix this issue, in your Azure Container Registry (ACR) resource, set the zone\_redundancy\_enabled attribute to true.

## This code enables Azure Container Registry (ACR) zone redundancy, by configuring the zone\_redundancy\_enabledsetting to 'true'. ACR data will be replicated across different zones within the region, providing highavailability and durability. \[source,go]

## resource "azurerm\_container\_registry" "acr" { ... sku = "Premium" ... georeplications { ... zone\_redundancy\_enabled = 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-233.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.