Forum Discussion
Microsoft Peering with ExpressRoute (Transitioning to from Public Peering)
Azure public peering has been deprecated, as is not available for new ExpressRoute circuits. New Circuits support Microsoft peering and private peering. Public peering has been disabled on new Expres...
Hannes_LG appears to be working now over the public peer. My issue is can I still use the public peer or do I need to move to the Microsoft peer? Public peering has been deprecated for new circuits but how long will it last on my existing circuit?
Hi,
if your internal IT policy requires, that the traffic for Azure AD Authentication routes over express route, you have to change the peering.
At the moment there isn’t any official statement from Microsoft when the public peering will be disabled for exist connections.
Here is a migration guide:
https://docs.microsoft.com/en-us/azure/expressroute/how-to-move-peering
But keep in mind, you maybe need the premium addon for the “Other Office 365 Services“ which include the Azure AD IPs.
For my point of view there is no need to route the Azure AD pass through authentication over the express route circuit, but when the security required that option it’s okay.
if your internal IT policy requires, that the traffic for Azure AD Authentication routes over express route, you have to change the peering.
At the moment there isn’t any official statement from Microsoft when the public peering will be disabled for exist connections.
Here is a migration guide:
https://docs.microsoft.com/en-us/azure/expressroute/how-to-move-peering
But keep in mind, you maybe need the premium addon for the “Other Office 365 Services“ which include the Azure AD IPs.
For my point of view there is no need to route the Azure AD pass through authentication over the express route circuit, but when the security required that option it’s okay.