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

# App Service is not registered with an Azure Active Directory account misconfiguration detected in co

## Rule Details

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

## Impact

Managed service identity in *App Service* increases security by eliminating secrets from the app, for example, credentials in the connection strings. *App Service* provides a highly-scalable, self-patching web hosting service in Azure. It also provides a managed identity for apps, which is a turn-key solution for securing access to an Azure SQL Database and other Azure services. We recommend you register the *App Service* with your Azure Active Directory account ensuring the app will connect securely to other Azure services without the need of usernames and passwords.

## How to Fix

*Resource:* azurerm\_app\_service

* *Field:* identity \[source,go]

***

resource "azurerm\_app\_service" "example" { ...

* identity {
* type = "UserAssigned"
* identity\_ids = "12345" } }

***


---

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