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

# Azure Machine Learning Compute Cluster Minimum Nodes is not set to 0 misconfiguration detected in co

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_150        |
| Category - Subcategory | Compute - Overprovisioned |
| Provider               | AZURE                     |
| Severity               | LOW                       |
| Framework              | Terraform                 |

## Impact

Setting the minimum number of nodes for your Azure Machine Learning Compute Clusters to 0 can help reduce the cost of running the cluster when it is not in use. When the minimum number of nodes is set to 0, the cluster is scaled down to 0 nodes when it is not in use, and no resources are consumed. By setting the minimum number of nodes to 0, you can ensure that the cluster is not consuming resources when it is not in use, which can help reduce your costs. This can be especially useful if you only need to use the cluster occasionally or on an as-needed basis.

## How to Fix

*Resource:* azurerm\_machine\_learning\_compute\_cluster

* *Arguments:* scale\_settings.min\_node\_count \[source,go]

***

resource "azurerm\_machine\_learning\_compute\_cluster" "ckv\_unittest\_pass" { name = "example" location = "West Europe" vm\_priority = "LowPriority" vm\_size = "Standard\_DS2\_v2" machine\_learning\_workspace\_id = azurerm\_machine\_learning\_workspace.example.id subnet\_resource\_id = azurerm\_subnet.example.id

## scale\_settings { min\_node\_count = 0 max\_node\_count = 1 scale\_down\_nodes\_after\_idle\_duration = "PT30S" # 30 seconds } }


---

# 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-150.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.