azure-docs
azure-docs copied to clipboard
Wording for BGP requirements is confusing.
In the sections "Traffic from on-premises networks to Azure" and "Traffic from Azure to on-premises networks", it is mentioned that the VPN portion of the environment is using BGP: For traffic from on-premises networks to Azure, the Azure prefixes are advertised via both the ExpressRoute private peering BGP, and the VPN BGP. Advertise more specific prefixes on the VPN BGP session for the VPN-connected network. You can advertise a larger range that encompasses the VPN-connected network over ExpressRoute private peering, then more specific ranges in the VPN BGP session.
When we look at the example steps for the Portal, the "Configure BGP" and "Enable BGP" options are not enabled for both the VPN Gateway and the Connection object. This is confusing and isn't clear if it is required that the VPN tunnel use BGP or not. Based off of the set-up though, I would assume BGP is not necessary for the VPN portion as long as a more defined route is annotated on the Local Network Gateway for the VPN. Is this the case? Can this be more clearly defined for customers?
Thanks!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 56e6b95b-6755-01d7-6e2d-72dfeb474a1a
- Version Independent ID: ef384f98-fe94-688e-12b2-841bb404cdbe
- Content: Site-to-Site VPN connections over ExpressRoute private peering
- Content Source: articles/vpn-gateway/site-to-site-vpn-private-peering.md
- Service: vpn-gateway
- GitHub Login: @cherylmc
- Microsoft Alias: cherylmc
Thanks for the feedback! We are currently investigating and will update you shortly.
@cherylmc Could you please look into this? Thank you!
@SaiKishor-MSFT, Any update on this?
This remains an issue to this day:
https://learn.microsoft.com/en-us/azure/vpn-gateway/site-to-site-vpn-private-peering?toc=%2Fazure%2Fexpressroute%2Ftoc.json
Still has no clear indication that you need to enable BGP under the VPN connection.
Thank you for you dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close