Forum Discussion

HB2019-'s avatar
HB2019-
Copper Contributor
Apr 01, 2019

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 ExpressRoute circuits. Azure services are available on Microsoft peering.

 

The issue is our DR environment hosted in Azure Site Recovery uses an ExpressRoute circuit that is configured with Microsoft peering. However, Azure AD pass through authentication does not seem to wrok in Azure. Do we need an ExpressRoute premium connector to support this? please help

 

 

  • Hannes_LG's avatar
    Hannes_LG
    Brass Contributor
    Hi,

    I don‘t here/see about any issues with ExpressRoute and AD pass through authentication.
    Do you have any express route filters configured?
    • HB2019-'s avatar
      HB2019-
      Copper Contributor

      Hannes_LG Do you have Other Office 365 services enabled for the BGP filter? I requested this from MS but still dont have approval. Can you confirm that is what you need to get that working?

      • Hannes_LG's avatar
        Hannes_LG
        Brass Contributor
        Hi,
        I had many customer engagements in the past where we use the Microsoft peering for Office365.
        We always had many troubles after we enable the service, that’s the reason why Microsoft disable that feature per default.
        For my point of view Office365 over express route make sense if you use Skype voice because you can use QoS.
        I don’t think that’s your issue. Do you see any connection issues in AzureAD (Pass through Authentication)

Resources