details about communities bgp

@LACOUR Jean-Luc OBS/GDO ,

Greetings.

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you are planning to Migrate from Public peering to Microsoft peering and would like to know what the BGP Communities in Public Peering correspond to the same in Microsoft peering, 12076:51052 and 12076:51057.

Let me know if my observation is incorrect.

• Please note that the Public Peering is deprecated.

Public peering for ExpressRoute is being retired on March 31, 2024. For more information, see retirement notice.

• For Migration, see : Move a public peering to Microsoft peering
• You must note that Prefix advertisement with Public peering is Nonselectable by the customer.
• And as such, the above prefixes could be something that is no longer required/supported in the Microsoft Peering
• Instead of comparing the prefixes that are advertised via Public Peering to match it with MS Peering, please consider the list of actual services you would require from MS Peering and configure the corresponding BGP Communities from the Route filter.

TL:DR;

• You do not have to worry about the BGP Communities that were advertised via Public Peering.
• All the BGP Communities and corresponding services/region supported via MS Peering is documented in Support for BGP communities
• Choose the services/region which you would require via the Route Filter and attach it to the ExpressRoute Peering.

Kindly let us know if this helps or you need further assistance on this issue.

Thanks,

Kapil