An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
Welcome to Microsoft Q&A
Hello @Steve Bulloch I hope you are doing well.
This doesn't appear to be an issue with the VM's internal IP configuration. Commands such as ipconfig /release, ipconfig /renew, or netsh int ip reset only affect the private IP inside the VM. The public IP and its geolocation are determined by Azure's outbound connectivity (for example, a NAT Gateway, Load Balancer, Azure Firewall, or the default outbound IP). Additionally, IP geolocation databases can sometimes report an Azure IP as being in a different country than the actual Azure region.
Please check the following:
- Verify whether the affected user is connected to a VPN or proxy.
- Compare the public IP (
https://ifconfig.me) from the affected VM with a working VM. - If your organization uses a secure web gateway (Zscaler, GlobalProtect, Cisco AnyConnect, etc.), verify that the user is assigned to the correct exit location.
- If no VPN or proxy is in use, review the Azure outbound public IP configuration for the virtual machine or subnet.
- https://learn.microsoft.com/azure/virtual-network/ip-services/default-outbound-access
- https://learn.microsoft.com/azure/nat-gateway/nat-overview
If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!