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

# Azure Synapse Spark Pool not using isolated compute misconfiguration detected in code

## Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_242                      |
| Category - Subcategory | Compute - Unsanctioned Resource Or Type |
| Provider               | AZURE                                   |
| Severity               | LOW                                     |
| Framework              | ARM, Bicep, Terraform, Terraform Plan   |

## Impact

This rule detects whether isolated compute is disabled for Synapse Spark pools in Azure. Isolated compute utilizes dedicated resources that are not shared with other customers. This isolation minimizes data breach and unauthorized access risks, enhancing security for your Spark pools. Enabling isolated compute is crucial for maintaining high security standards, especially when handling sensitive data or running critical applications within Synapse Spark pools.

## How to Fix

*Resource:* Microsoft.Synapse/workspaces/bigDataPools

* *Arguments:* properties/isComputeIsolationEnabled

## In this example, the `properties/isComputeIsolationEnabled` property is set to `true` within the `properties` section of the `Microsoft.Synapse/workspaces/bigDataPools` resource definition. \[source,go]

## { ... "resources": \[ { "type": "Microsoft.Synapse/workspaces/bigDataPools", ... "properties": { ... "isComputeIsolationEnabled": 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/ai-and-machine-learning/appsec-azure-242.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.