Different VPN point2site VPN server URL

Question

Hi Team

I am have exported VPN client profile from Azure portal for P2S azure vpn client. I found their 2 VPN server url in profile.

1. wan.xxxxx.vpn.azure.com
2. hub0.xxxxx.vpn.azure.com

Do you anyone know what is the different? Which one should I perfer to use?

Thanks

Pisitpong

Answer 1

Thanks for posting your question in the Microsoft Q&A forum.

A Virtual Hub is a virtual network created and used by Virtual WAN. It serves as the core of your Virtual WAN network in a specific region.

https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-point-to-site-portal#hub

If you have a specific use case where you need to connect to a particular hub within your Virtual WAN, choose hub0.xxxxx.vpn.azure.com.

Otherwise using Azure Virtual WAN as a whole and benefit from its comprehensive features, go with wan.xxxxx.vpn.azure.com.

** Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful **

Answer 2

Hello @PISITPONG VISARLCHAROENYING ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you have exported VPN client profile from Azure Virtual WAN for P2S Azure VPN client where you found 2 VPN server urls (wan.xxxxx.vpn.azure.com & hub0.xxxxx.vpn.azure.com) in the profile and would like to know the difference between the 2 URLs.

Azure Virtual WAN offers two types of connection profiles for User VPN clients:

• Global profiles
• Hub profiles

The type of profile you choose depends on whether you want the VPN client to connect to a geographically load-balanced WAN-level profile (global profile), or you want to restrict the VPN client to connect only to a certain hub (hub profile).

Global profiles:

The global profile associated with a User VPN configuration points to a Global Traffic Manager. The Global Traffic Manager includes all active User VPN hubs that are using that User VPN configuration. However, you can choose to exclude hubs from the Global Traffic Manager if necessary. A user connected to the global profile is directed to the hub that's closest to the user's geographic location. This is especially useful if you have users that travel between multiple locations frequently.

For example, a User VPN Configuration is associated with two different hubs for the same virtual WAN, one in West US and one in Southeast Asia. If a user connects to the global profile associated with the User VPN configuration, they'll connect to the closest Virtual WAN hub based on their location.

When you use a global profile, if for some reason a hub is unavailable, the built-in traffic management provided by the service ensures connectivity (via a different hub) to Azure resources for point-to-site users.

Hub profiles:

You can use this type of profile when you want VPN users to be able to connect only to a single specified hub. The files you generate and download at the hub-level contain different settings than the files you generate and download at the WAN-level global profile.

For more information, you can refer the below docs:

https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-point-to-site-portal#download

https://learn.microsoft.com/en-us/azure/virtual-wan/global-hub-profile

Kindly let us know if the above helps or you need further assistance on this issue.

---

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.