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

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

## Rule Details

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

## Impact

This rule is checking to see if the App Service Plan for Azure is zone redundant. Zone redundancy means that the application's resources are distributed across multiple zones, which can protect against failures. If the plan isn't zone redundant, it could be a potential vulnerability. For instance, if there was an issue in one zone - like a natural disaster, power outage, or hardware failure - and the plan wasn't zone redundant, it could result in an application outage. Thus, not having an App Service Plan that is zone redundant could lead to service interruptions, which could negatively affect user experience, data, and potentially revenue.

## How to Fix

*Resource:* azurerm\_service\_plan

* *Arguments:* zone\_balancing\_enabled

## To fix this issue, you need to ensure that your App Service Plan is geographically distributed and has a failover policy. This can be achieved by turning on the "zone\_balancing\_enabled" attribute in your Terraform configuration. \[source,go]

resource "azurerm\_service\_plan" "pass" { name = "example" resource\_group\_name = azurerm\_resource\_group.example.name location = azurerm\_resource\_group.example.location os\_type = "Linux" sku\_name = "P1v2"

* zone\_balancing\_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-225.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.