VPN Gateway should be successfully provisioned

Applies to

• Microsoft.Network/vpnGateways

What CGPulse checks

A resource passes this rule when provisioningState must equal Succeeded. Anything else is reported as a finding with the evaluated property value attached as evidence.

How to fix it

Resolve provisioning failures to ensure the VPN Gateway is operational. In Azure Portal: VPN Gateway > Overview > check provisioning state. See: https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-troubleshoot

CLI

az network vpn-gateway show --ids "{id}" --query "provisioningState" -o tsv

Bicep

// Provisioning failures cannot be fixed via Bicep property changes.
// Check Azure Activity Log for the specific error, common causes:
// - Subnet conflicts or missing GatewaySubnet
// - Quota exceeded for public IPs or gateway resources
// - Region capacity issues
// Re-deploy the gateway after resolving the underlying issue

Terraform

# Provisioning failures cannot be fixed via Terraform property changes. # Check Azure Activity Log for the specific error, common causes: # - Subnet conflicts or missing GatewaySubnet # - Quota exceeded for public IPs or gateway resources # - Region capacity issues # Re-apply the Terraform config after resolving the underlying issue

Compliance frameworks

• Cloud Security: Azure Foundations

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