Azure Compliance ControlsAzure Functions
Function apps should have virtual network integration enabled
Azure Function apps configured with Virtual Network integration uses a chosen subnet so outbound traffic is routed via the VNet and can reach private or service-endpoint-secured resources. The finding reflects whether a function app is associated with a subnet resource ID.
What this control checks
Function apps should have virtual network integration enabled
Framework mappings
The clauses this control is mapped to in each framework.
- 1.2.8: Network security controls (NSCs) are configured and maintained.
- 1.3.1: Network access to and from the cardholder data environment is restricted.
- 1.3.2: Network access to and from the cardholder data environment is restricted.
- 1.4.2: Network connections between trusted and untrusted networks are controlled.
- 1.5.1 Security controls are implemented on any computing devices, including company- and employee-owned devices, that connect to both untrusted networks
1 more clause
- A1.1.3: Multi-tenant service providers protect and separate all customer environments and data.
- 2 Risk management policy
- 5 Supply chain security
- 6 Security in network and information systems acquisition, development and maintenance
Related controls
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
azure_app_function_vnet_integration_enabled - Prowler Check:
app_function_vnet_integration_enabled
Last reviewed: 2026-10-11