> 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/monitoring/appsec-azure-custom-1.md).

# Azure resources that support tags do not have tags misconfiguration detected in code

## Rule Details

|                        |                                |
| ---------------------- | ------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_CUSTOM\_1       |
| Category - Subcategory | Monitoring - Tags and metadata |
| Provider               | AZURE                          |
| Severity               | LOW                            |
| Framework              | Terraform, Terraform Plan      |

## Impact

Many different types of Azure resources support tags. Tags allow you to add metadata to a resource to help identify ownership, perform cost / billing analysis, and to enrich a resource with other valuable information, such as descriptions and environment names. While there are many ways that tags can be used, we recommend you follow a tagging practice. View Microsoft's recommended tagging best practices <https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/naming-and-tagging\\[here>].

## How to Fix

## The example below shows how to tag a security group in Terraform. The syntax is generally the same for any taggable resource type. \[source,go]

resource "azurerm\_resource\_group" "example" { name = "example-resources" location = "West Europe" }

resource "azurerm\_managed\_disk" "example" { name = "acctestmd" location = "West US 2" resource\_group\_name = azurerm\_resource\_group.example.name storage\_account\_type = "Standard\_LRS" create\_option = "Empty" disk\_size\_gb = "1"

* tags = {
* environment = "staging" }

} ",

## }


---

# 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/monitoring/appsec-azure-custom-1.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.