azure-docs icon indicating copy to clipboard operation
azure-docs copied to clipboard

Wording for BGP requirements is confusing.

Open david-frazee opened this issue 4 years ago • 4 comments

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.

david-frazee avatar Feb 26 '21 21:02 david-frazee

Thanks for the feedback! We are currently investigating and will update you shortly.

SaiKishor-MSFT avatar Feb 26 '21 22:02 SaiKishor-MSFT

@cherylmc Could you please look into this? Thank you!

SaiKishor-MSFT avatar Mar 03 '21 20:03 SaiKishor-MSFT

@SaiKishor-MSFT, Any update on this?

samsmith-MSFT avatar Dec 13 '22 16:12 samsmith-MSFT

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.

abudhu avatar Dec 13 '22 16:12 abudhu

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

asudbring avatar Apr 24 '23 19:04 asudbring