Skip to content

Commit 63c27c3

Browse files
authored
Update expressroute-howto-coexist-resource-manager.md
1 parent 02b37aa commit 63c27c3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/expressroute/expressroute-howto-coexist-resource-manager.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The steps to configure both scenarios are covered in this article. This article
2929
## Limits and limitations
3030

3131
* **Only route-based VPN gateway is supported.** You must use a route-based [VPN gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md). You can also use a route-based VPN gateway with a VPN connection configured for 'policy-based traffic selectors' as described in [Connect to multiple policy-based VPN devices](../vpn-gateway/vpn-gateway-connect-multiple-policybased-rm-ps.md).
32-
* ExpressRoute-VPN Gateway coexist configurations are **not supported with Basic SKU public IP**.
32+
* ExpressRoute-VPN Gateway coexist configurations are **not supported with Basic SKU VPN Gateway**.
3333
* If you want to use transit routing between ExpressRoute and VPN, **the ASN of Azure VPN Gateway must be set to 65515, and Azure Route Server should be used.** Azure VPN Gateway supports the BGP routing protocol. For ExpressRoute and Azure VPN to work together, you must keep the Autonomous System Number of your Azure VPN gateway at its default value, 65515. If you previously selected an ASN other than 65515 and you change the setting to 65515, you must reset the VPN gateway for the setting to take effect.
3434
* **The gateway subnet must be /27 or a shorter prefix**, such as /26 or /25, or you receive an error message when you add the ExpressRoute virtual network gateway.
3535

0 commit comments

Comments
 (0)