Azure express route private peering issue

Hi Harinath Gorthy

Thanks for reaching out to Microsoft Q&A.

Kindly follow this document for troubleshooting express route connectivity issues- https://learn.microsoft.com/en-us/azure/expressroute/expressroute-troubleshooting-expressroute-overview

Also, please click the Metrics blade and select the BgpAvailability/ArpAvailability metric to determine, which BGP peer and which device(s) are not currently healthy. Please check below document for reference on how to check the metrics table

https://learn.microsoft.com/en-us/azure/expressroute/monitor-expressroute-reference

If the state of a eBGP peering between an MSEE and a CE/PE-MSEE is Active or Idle, check if the assigned primary and secondary peer subnets match the configuration on the linked CE/PE-MSEE. Also check if the correct VlanId, AzureASN, and PeerASN values are used on MSEEs, and if these values map to the ones used on the linked CE/PE-MSEE. If MD5 hashing is chosen, the shared key should be the same on MSEE and CE/PE-MSEE pairs. If you need to change any of these configurations on an MSEE router, see Create and modify routing for an ExpressRoute circuit.

Refer: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-troubleshooting-expressroute-overview#validate-bgp-and-routes-on-the-msee

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.