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

# Azure Data Explorer without SLA misconfiguration detected in code

## Azure Data Explorer without SLA misconfiguration detected in code

### Rule Details

|                        |                                   |
| ---------------------- | --------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_180                |
| Category - Subcategory | Public Exposure - Resource Health |
| Provider               | AZURE                             |
| Severity               | LOW                               |
| Framework              | Terraform, Terraform Plan         |

### Impact

Azure Data Explorer is a fast, fully managed data analytics service for real-time analysis on large volumes of data streaming from applications, websites, IoT devices, and more. Service Level Agreements (SLA) ensure that services are up and running. Using SKUs without an SLA may introduce risks in terms of availability.

This rule checks that the Azure Data Explorer cluster does not use a SKU which lacks an SLA.

### How to Fix

*Resource:*

* azurerm\_kusto\_cluster

*Argument:*

* sku/\[0]/name \[source,go]

***

resource "azurerm\_kusto\_cluster" "example" { name = "example-cluster" location = azurerm\_resource\_group.example.location resource\_group\_name = azurerm\_resource\_group.example.name

## ... other configurations ...

* sku {
* name = "Dev(No SLA)\_Standard\_D11\_v2" // Not recommended
* capacity = 2
* }
* sku {
* name = "Standard\_D13\_v2" // Use a SKU with an SLA
* capacity = 2
* }

}

***


---

# 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/storage/appsec-azure-180.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.