Private Endpoint connection should be in Approved state
High
Azure
General
privateendpoints-private-endpoint
Applies to
Microsoft.Network/privateEndpoints
What CGPulse checks
A resource passes this rule when connectionStatus must equal Approved. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Approve the private endpoint connection to enable secure private access. In Azure Portal: Resource > Networking > Private endpoint connections > Approve. See: https://learn.microsoft.com/en-us/azure/private-link/manage-private-endpoint
CLI
az network private-endpoint-connection approve --id "<connection-id>" --description "Approved"Bicep
// Private endpoint approval cannot be done in Bicep. Use az network private-endpoint-connection approve --id "<connection-id>"Terraform
# Approval happens automatically when is_manual_connection = false
resource "azurerm_private_endpoint" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
subnet_id = var.subnet_id
private_service_connection {
name = "{name}-plsc"
private_connection_resource_id = "<target-resource-id>"
subresource_names = ["<group-id>"]
is_manual_connection = false
}
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Azure rules
- Action Group should be enabled
- Activity Log Alert should be enabled
- AKS cluster logs should be sent to Log Analytics
- AKS cluster must enable RBAC
- AKS cluster must enable RBAC
- AKS cluster should be a private cluster
- AKS cluster should disable local accounts
- AKS cluster should enable Azure RBAC for Kubernetes