> 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/networking/appsec2-azure-56.md).

# Azure MySQL Flexible Server not configured with private endpoint misconfiguration detected in code

## Rule Details

|                       |                           |
| --------------------- | ------------------------- |
| Cortex AppSec Rule ID | APPSEC2\_AZURE\_56        |
| Category              | Networking                |
| Provider              | AZURE                     |
| Severity              | MEDIUM                    |
| Framework             | Terraform, Terraform Plan |

## Impact

This rule checks whether Azure MySQL Flexible Server is configured to use a private endpoint. Private endpoints allow secure connections to Azure services over a private IP address within a virtual network, preventing exposure to the public internet.

Failing to configure private endpoints for Azure MySQL Flexible Server can lead to several security issues, including unauthorized access and data breaches. When databases are accessible over the public internet, they are more vulnerable to attacks, increasing the risk of exploitation by malicious actors. By using private endpoints, organizations can enhance their security posture, ensuring that data communication is restricted to trusted private networks and significantly reducing the attack surface.

## How to Fix

## To comply with the rule, ensure that your Azure MySQL Flexible Server is configured with a private endpoint. This involves creating a `private_endpoint_connection` block within your `azurerm_mysql_flexible_server` resource to secure the server's connection and ensure it does not expose any public IP addresses. \[source,go]

resource "azurerm\_mysql\_flexible\_server" "example" { name = "example" ... }

* resource "azurerm\_private\_endpoint" "example" {
* ...
* private\_service\_connection {
* ...
* private\_connection\_resource\_id = azurerm\_mysql\_flexible\_server.example.id
* }
* }

***


---

# 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/networking/appsec2-azure-56.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.