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

# Azure Microsoft Defender for Cloud security contact phone number is not set misconfiguration detecte

## Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_20                       |
| Category - Subcategory | Monitoring - Alerting And Notifications |
| Provider               | AZURE                                   |
| Severity               | LOW                                     |
| Framework              | ARM, Bicep, Terraform, Terraform Plan   |
| Mapped CSPM/KSPM Rule  | 51be4654-4d2d-43c4-9279-58bb38a1d741    |

## Impact

Microsoft reaches out to the designated security contact in case its security team finds that the organization's resources are compromised. This ensures that the correct people are aware of any potential compromise and can mitigate the risk in a timely fashion. We recommend you provide a security contact phone number, but before taking any action make sure that the information provided is valid because the communication is not digitally signed.

## How to Fix

*Resource:* azurerm\_security\_center\_contact

* *Arguments:* phone \[source,go]

***

## resource "azurerm\_security\_center\_contact" "example" { email = "<contact@example.com>" phone = "+1-555-555-5555" }


---

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