Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Virtual WAN is updated regularly. Stay up to date with the latest announcements. This article provides you with information about:
- Recent releases
- Previews underway with known limitations (if applicable)
- Known issues
- Deprecated functionality (if applicable)
You can also find the latest Azure Virtual WAN updates and subscribe to the RSS feed here.
Recent releases
| Type | Area | Name | Description | Date added | Limitations |
|---|---|---|---|---|---|
| Feature | ExpressRoute | ExpressRoute circuit page now shows vWAN connection | August 2022 | ||
| Feature | Branch connectivity/Site-to-site VPN | Multi-APIPA BGP | Ability to specify multiple custom BGP IPs for VPN gateway instances in vWAN. | June 2022 | Currently only available via portal. (Not available yet in PowerShell) |
| Feature | Branch connectivity/Site-to-site VPN | Custom traffic selectors | Ability to specify what traffic selector pairs site-to-site VPN gateway negotiates | May 2022 | Azure negotiates traffic selectors for all pairs of remote and local prefixes. You can't specify individual pairs of Traffic selectors to negotiate. |
| Feature | Branch connectivity/Site-to-site VPN | Site-to-site connection mode choices | Ability to configure if customer or vWAN gateway should initiate the site-to-site connection while creating a new S2S connection. | February 2022 | |
| Feature | Branch connectivity/Site-to-site VPN | Packet capture | Ability for customer to perform packet captures on site-to-site VPN gateway. | November 2021 | |
| Feature | Remote User connectivity/Point-to-site VPN | Global profile include/exclude | Ability to mark a point-to-site gateway as "excluded", meaning users who connect to global profile will not be load-balanced to that gateway. | February 2022 | |
| Feature | Remote User connectivity/Point-to-site VPN | Forced tunneling for P2S VPN | Ability to force all traffic to Azure Virtual WAN for egress. | October 2021 | Only available for Azure VPN Client version 2:1900:39.0 or newer. |
| Feature | Remote User connectivity/Point-to-site VPN | macOS Azure VPN client | General Availability of Azure VPN Client for macOS. | August 2021 | |
| Feature | Remote User connectivity/Point-to-site VPN | Remote RADIUS server | Ability for a P2S VPN gateway to forward authentication traffic to a RADIUS server in a virtual network connected to a different hub, or a RADIUS server hosted on-premises. | April 2021 | |
| Feature | Remote User connectivity/Point-to-site VPN | Dual-RADIUS server | Ability to specify primary and backup RADIUS servers to service authentication traffic. | March 2021 | |
| Feature | Remote User connectivity/Point-to-site VPN | Custom IPsec policies | Ability to specify connection/encryption parameters for IKEv2 point-to-site connections. | March 2021 | Only supported for IKEv2- based connections. View the list of available parameters. |
| SKU | Remote User connectivity/Point-to-site VPN | Support up to 100K users connected to a single hub | Increased maximum number of concurrent users connected to a single gateway to 100,000. | March 2021 | |
| Feature | Remote User connectivity/Point-to-site VPN | Multiple-authentication methods | Ability for a single gateway to use multiple authentication mechanisms. | June 2023 | Supported for gateways running all protocol combinations. Note that Microsoft Entra authentication still requires the use of OpenVPN |
Known issues
| # | Issue | Description | Date first reported | Mitigation |
|---|---|---|---|---|
| 1 | ExpressRoute connectivity with Azure Storage and the 0.0.0.0/0 route | If you configured a 0.0.0.0/0 route statically in a virtual hub route table or dynamically via a network virtual appliance for traffic inspection, that traffic bypasses inspection when destined for Azure Storage and is in the same region as the ExpressRoute gateway in the virtual hub. | As a workaround, you can either use Private Link to access Azure Storage or put the Azure Storage service in a different region than the virtual hub. | |
| 2 | Default routes (0/0) won't propagate inter-hub | 0/0 routes won't propagate between two virtual WAN hubs. | June 2020 | None. Note: While the Virtual WAN team has fixed the issue, wherein static routes defined in the static route section of the VNet peering page propagate to route tables listed in "propagate to route tables" or the labels listed in "propagate to route tables" on the VNet connection page, default routes (0/0) won't propagate inter-hub. |
| 3 | Two ExpressRoute circuits in the same peering location connected to multiple hubs | If you have two ExpressRoute circuits in the same peering location, and both of these circuits are connected to multiple virtual hubs in the same Virtual WAN, then connectivity to your Azure resources might be impacted. | July 2023 | Make sure each virtual hub has at least 1 virtual network connected to it. This ensures connectivity to your Azure resources. The Virtual WAN team is also working on a fix for this issue. |
Next steps
For more information about Azure Virtual WAN, see What is Azure Virtual WAN and frequently asked questions- FAQ.