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

# Azure Microsoft Defender for Cloud security alert email notifications is not set misconfiguration de

## Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_131                      |
| Category - Subcategory | Monitoring - Alerting And Notifications |
| Provider               | AZURE                                   |
| Severity               | LOW                                     |
| Framework              | ARM, Bicep, Terraform, Terraform Plan   |
| Mapped CSPM/KSPM Rule  | 084973b5-bb39-456c-bfef-6ec42c261c59    |

## Impact

Azure Security Center recommends adding one valid security contact email address for each Microsoft Azure subscription. Security Center emails designated administrators using the defined security contact in case the Microsoft security team find Azure cloud resources are compromised.

## How to Fix

*Resource:* azurerm\_security\_center\_contact

* *Arguments:* email - (Required) The email of the Security Center Contact. \[source,go]

***

resource "azurerm\_security\_center\_contact" "example" {

* email = "<contact@example.com>" ... }

***


---

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