Hi Marcio Manrique,
Is there any solution that doesn't require creation of a new subnet and Nat Gateway?
It could be worthwhile to reach out to Whitepages support to confirm if their system is blocking Azure IP ranges.
Go to Azure Portal → Create a NAT Gateway
Assign:
- A static Public IP Address
- A Virtual Network (new or existing)
- A Subnet to associate with the NAT Gateway (you may need to move your AVD session hosts here)
Move AVD Hosts to a NAT-enabled Subnet
If you already have AVD hosts in a subnet, and cannot use NAT there, create a new subnet, configure NAT on it, and move the AVD hosts to this subnet.
You cannot apply NAT Gateway to existing subnets if using basic load balancers or conflicting network settings.
After NAT is applied, all outbound traffic from AVDs will share the same public IP. and test the access to https://www.whitepages.com/
https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview
https://learn.microsoft.com/en-us/azure/nat-gateway/manage-nat-gateway?tabs=manage-nat-portal
If you found information helpful, please click "Upvote" on the post to let us know.
If you have any further queries, feel free to reach out — we’re always happy to assist you.
Thank You.