Microsoft connect cache no se puede establecer la conexión con el router

Hello @Will Lanz ,

Thank for reaching out to Microsoft Q&A!

 The eBGP peer is currently stuck in the Connect state, indicating that the Microsoft Connected Cache server is unable to establish a TCP connection (port 179) with the configured router. In an Azure eBGP configuration, this is typically caused by connectivity-related issues rather than BGP itself. Common causes include an IPsec tunnel that is not established, an incorrect BGP peer IP address (for example, using a public IP instead of the BGP peering IP), TCP port 179 being blocked by a firewall or NSG, an ASN mismatch between Azure and the on-premises network, or a general network reachability issue between the peers. Please verify the tunnel status, validate the peer IP and ASN configuration, ensure TCP port 179 is open in both directions, and confirm connectivity between the Azure and on-premises endpoints. Once the underlying connectivity issue is resolved, the eBGP session should transition to the Established state.

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