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

# Data Explorer Not Using Managed Identities misconfiguration detected in code

## Data Explorer Not Using Managed Identities misconfiguration detected in code

### Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_181            |
| Category - Subcategory | IAM - Authentication Policies |
| Provider               | AZURE                         |
| Severity               | MEDIUM                        |
| Framework              | Terraform, Terraform Plan     |

### Impact

Azure Data Explorer (or Kusto) is a fast and scalable data analytics service that makes it simple and cost-effective to explore and analyze all of your data. To ensure secure access to other Azure services, it's best practice to use managed identities, which offer a secure, Azure AD integrated method of authenticating to Azure services.

This rule checks that the Azure Data Explorer (Kusto) clusters are configured to use managed identities for secure access.

### How to Fix

*Resource:*

* azurerm\_kusto\_cluster

*Argument:*

* identity/\[0]/type \[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 ...

* identity {
* type = "SystemAssigned" // Use managed identity
* }

}

***


---

# 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/iam/appsec-azure-181.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.