The Azure Virtual Network limitations page is outdated: Azure Database for PostgreSQL Flexible Server now supports VNet integration with dual-stack IPv4/IPv6 subnets, but database connections still use IPv4.
The two statements describe different support levels:
- VNet/subnet integration: Supported when the delegated subnet contains both IPv4 and IPv6 address ranges, as documented in the April 2026 Flexible Server release notes.^1^
- PostgreSQL connectivity: Still IPv4-only. Flexible Server does not expose IPv6 database connectivity.^1^
- Public-access firewall rules: Must also use IPv4 addresses; IPv6 firewall rules produce a validation error.^2^
Consequently, this statement on the VNet page is no longer accurate as a blanket limitation:
It can't be deployed if there are IPv6 addresses in the virtual network.
That page still contains the earlier restriction and should be updated to distinguish dual-stack subnet support from IPv6 connection support.^3^
Current expected configuration
For VNet-integrated Flexible Server:
- Use a subnet delegated to
Microsoft.DBforPostgreSQL/flexibleServers.
- The subnet may now contain both IPv4 and IPv6 address ranges.
- Configure clients, DNS, routes, and network security rules so PostgreSQL traffic reaches the server over IPv4.
- Use TCP port 5432 unless the server is configured otherwise.
- Do not configure IPv6 addresses in public-access firewall rules.
The private-networking documentation continues to require a dedicated delegated subnet for Flexible Server.^4^
The April 2026 update was initially rolled out region by region, with up to a one-month global rollout period after April 22, 2026.^1^ That rollout window has passed, so a deployment rejection now should not normally be attributed to rollout timing.
If a current deployment into a dual-stack delegated subnet is rejected:
- Open Azure portal → Monitor → Activity Log and inspect the failed deployment operation and its error details.
- Verify that the target subnet is delegated to
Microsoft.DBforPostgreSQL/flexibleServers.
- Treat any remaining rejection specifically caused by the IPv6 prefix as a service validation or documentation discrepancy and open an Azure support request with the operation timestamp, region, error code, and correlation ID.
- Report the stale limitation through the Feedback control on the VNet documentation page.
References
- Azure Database for PostgreSQL flexible server: April 2026 release
- Networking with public access (allowed IP addresses) in Azure Database for PostgreSQL flexible server
- What is IPv6 for Azure Virtual Network?
- Network with private access (virtual network integration) in Azure Database for PostgreSQL flexible server