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

# App Configuration Using Local Authentication misconfiguration detected in code

## App Configuration Using Local Authentication misconfiguration detected in code

### Rule Details

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

### Impact

Authentication plays a pivotal role in securing Azure App Configuration resources. Azure provides two primary authentication schemes: Azure Active Directory (Azure AD) credentials and access keys. Azure AD credentials offer enhanced security features and are easier to manage, making them the recommended choice by Microsoft over access keys.

This rule ensures that `local_auth_enabled` attribute in Azure App Configuration resources is set to `False`. Setting this attribute to `True` would enable local authentication with access keys, potentially making the resource more susceptible to unauthorized access.

### How to Fix

*Resource:*

* azurerm\_app\_configuration

*Arguments:*

* local\_auth\_enabled \[source,go]

***

resource "azurerm\_app\_configuration" "example" { name = "example-app-configuration" location = azurerm\_resource\_group.example.location resource\_group\_name = azurerm\_resource\_group.example.name

## ... other configurations ...

* local\_auth\_enabled = false // Ensure local authentication is disabled }

***


---

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