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

# Azure SQL Database Namespace is not zone redundant misconfiguration detected in code

## Rule Details

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

## Impact

This rule is verifying whether the Azure SQL Database Namespace is zone redundant. Zone redundancy is a crucial factor in ensuring high availability and disaster recovery if a zone failure occurs. When an Azure SQL Database namespace is not zone redundant, it may lead to potential data loss or unavailability in case of a zone-wide issue in Azure. Thus, to prevent any disruptions in service or data loss, it's essential to have this redundancy setup.

## How to Fix

*Resource:* azurerm\_mssql\_database

* *Arguments:* zone\_redundant

## To fix this issue, you need to set the `zone_redundant` parameter to `true` within the `azurerm_mssql_database` resource section of your Terraform code. \[source,go]

## resource "azurerm\_mssql\_database" "example" { name = "example-sql-db" resource\_group\_name = azurerm\_resource\_group.example.name server\_name = azurerm\_sql\_server.example.name location = azurerm\_resource\_group.example.location edition = "Standard" collation = "SQL\_Latin1\_General\_CP1\_CI\_AS" max\_size\_bytes = "1073741824" 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-229.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.