Trace both address families through a dual-stack Load Balancer deployment

Source facts

Microsoft’s dual-stack application example includes IPv4 and IPv6 load-balancer frontends, a dual-stack VNet and subnet, dual IP configurations on VM network interfaces, and corresponding network-security rules. Its NIC procedure creates one IPv4 configuration and one IPv6 configuration for each VM interface. A second public frontend alone does not reproduce that documented design. Microsoft Learn.

Applicability

Use this review when proposing the Standard Load Balancer pattern described by the source. Identify both public endpoints, the backend associations, subnet prefixes and application listeners. Keep the assessment separate from Application Gateway’s different IPv6 feature set.

DSE recommendation

DSE recommends a two-column configuration checklist for IPv4 and IPv6. At each layer, record the intended resource, address and permitted application path. Have the network and application owners resolve missing entries before opening client traffic. Review the current source’s complete configuration rather than copying sample addresses or broad administrative-access rules into production.

Verification

Use approved clients with working connectivity for each address family. Test the same application operation through both frontends and correlate backend observations with the planned interfaces. Check the intended security decisions separately. Preserve evidence by address family so a successful IPv4 request does not close an untested or incomplete IPv6 path.

Official references

Microsoft Learn: Deploy IPv6 dual stack application.