An Azure Virtual Desktop deployment contains 500 session host VMs. All outbound internet traffic from those VMs goes through a NAT gateway. During peak hours some users cannot reach internet resources, and Azure Monitor reports many failed SNAT connections. You need to increase the number of available SNAT connections for outbound from the session hosts. What should you do?

Adding a public IP address to the NAT gateway increases the number of available Source Network Address Translation (SNAT) ports. Each public IP address provides 64,512 SNAT ports, so adding more public IPs directly expands the pool of available connections, resolving the SNAT exhaustion issue. Binding the NAT gateway to another subnet will not increase the number of SNAT ports; it only changes which subnet uses the existing NAT gateway. Deploying an Azure Standard Load Balancer with outbound rules is a valid solution for SNAT exhaustion, but the question asks what you should do to increase the number of available SNAT connections for outbound from the session hosts using the existing NAT gateway. Adding a public IP address directly addresses the SNAT port limitation of the NAT gateway.