> 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/appsec-azure-241.md).

# Azure Synapse SQL pool not encrypted misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_241        |
| Category - Subcategory | Storage - Encryption      |
| Provider               | AZURE                     |
| Severity               | LOW                       |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule detects whether Synapse SQL pools in Microsoft Azure are unencrypted. Encryption is vital for protecting sensitive data from unauthorized access and breaches. By enforcing encryption, this rule safeguards the confidentiality and integrity of the data stored within the SQL pools. Without encryption, data becomes vulnerable to cyberattacks, potentially leading to data leaks, financial losses, and reputational damage.

## How to Fix

**Terraform**

* **Resource:** azurerm\_synapse\_sql\_pool
* **Arguments:** data\_encrypted

Enable encryption for your Azure Synapse SQL pool: Set the `data_encrypted` property to `true` within the corresponding `azurerm_synapse_sql_pool` resource definition.

To fix this issue, ensure that `data_encrypted` is set to `true` for your `azurerm_synapse_sql_pool` resource.

```go
resource "azurerm_synapse_sql_pool" "example" {
  ...
+  data_encrypted = 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/ai-and-machine-learning/appsec-azure-241.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.