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

# App Service Environment is not zone redundant misconfiguration detected in code

## Rule Details

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

## Impact

This rule is designed to verify if the App Service Environment is zone redundant. Zone redundancy refers to the distribution of resources across different geographical zones to ensure business continuity and disaster recovery. A lack of zone redundancy could lead to service disruptions if the zone hosting the App Service Environment faces any unexpected issues such as outages or natural disasters. Therefore, it's crucial to establish zone redundancy to prevent service availability issues and potential data loss.

## How to Fix

*Resource:* azurerm\_app\_service\_environment\_v3

* *Arguments:* zone\_redundant

## To fix this issue, you need to enable zone redundancy for the App Service Environment by setting the `zone_redundant` attribute to `true`. \[source,go]

## resource "azurerm\_app\_service\_environment\_v3" "example" { name = "example-ase" // ... 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.