> 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/ai-and-machine-learning/appsec2-azure-51.md).

# Azure Synapse SQL Pool does not have a security alert policy misconfiguration detected in code

## Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_AZURE\_51                      |
| Category - Subcategory | Monitoring - Alerting And Notifications |
| Provider               | AZURE                                   |
| Severity               | LOW                                     |
| Framework              | ARM, Bicep, Terraform, Terraform Plan   |

## Impact

This rule detects whether a Synapse SQL Pool has a security alert policy configured. A security alert policy is used to set up alerts for specific security incidents, abnormal activities, and threats in the SQL pool. This is crucial for real-time monitoring and maintaining the security posture of a Synapse workspace, helping to ensure the protection of your data.

## How to Fix

**Terraform**

* **Resource:** azurerm\_synapse\_sql\_pool
* **Arguments:** azurerm\_synapse\_sql\_pool\_security\_alert\_policy

Configure a security alert policy for your Synapse SQL Pool. Associate each `azurerm_synapse_sql_pool` resource with a `azurerm_synapse_sql_pool_security_alert_policy` block. This block defines the security alert policies for the pool.

In this example, a security alert policy for an Azure Synapse SQL Pool is configured using Terraform templates.

```go
resource "azurerm_synapse_sql_pool" "example" {
  name                 = "examplesqlpool"
  ...
}

+ resource "azurerm_synapse_sql_pool_security_alert_policy" "example" {
+   sql_pool_id                = azurerm_synapse_sql_pool.example.id
+   policy_state               = "Enabled"
+   ...
+ }
```


---

# 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/ai-and-machine-learning/appsec2-azure-51.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.