Notes About Azure ExpressRoute

What Azure services can be used for private peering from the server on the on-premises side

  • If ExpressRoute is configured with private peering, what Azure services can be used from the server on the on-premises side?
  • As you can see here , any service that can be deployed to a virtual network will be available. So what services can be deployed on a virtual network?
  • If you use the Azure service described here, you can access via ExpressRoute set by private peering. With Azure Private Endpoint, most services can be used for private peering. This seems to be convenient because it was troublesome to use Microsoft peering because it required Global IP and NAT setting was required on the on-premise switch.

How Azure services can be used for Microsoft peering from the server on the on-premises side?

  • Other than the Azure services available for private peering, they are available for Microsoft peering. However, some services are not available.

Switching time when there is a route failure

By enabling BFD for both private peering and Microsoft peering, switching is possible in about 1 second. Since BFD is enabled by default on the Azure side, it is necessary also to enable BFD on the router on the user side.

Resolve the name when accessing the Azure service from the server on the on-premises side

To access services for example Azure Storage Account, Azure Database from the on-premises server, you need to access by FQDN instead of IP address. Therefore, name resolution by DNS is required.

For example we want to directly access DNS in Azure’s Virtual Network via ExpressRoute (Private Peering) instead of referencing DNS via the Internet. However, this Azure DNS cannot be accessed directly from the on-premises side. Therefore, build a DNS Forwarder in the Virtual Network with a VM or container so that this DNS Forwarder forwards DNS queries to Azure’s DNS.

Then, by setting the Private IP address of the DNS Forwarder in the DNS settings of the server on the on-premise side, name resolution can be performed via ExpressRoute.

If possible, and we can use Azure services instead of VMs and containers, but Azure DNS cannot be accessed via ExpressRoute.

Monitor the server on the on-premise side from the Azure side

With Azure Monitor, you can monitor syslog. We only need to install the agent on the server on the pre-premises side.

 by the author.

--

--

--

DevOps Consultant. I’m strongly focused on automation, security, and reliability.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Fix WordPress plugin installation permission issue

TestBash Home 2020 — Explore Black Box Puzzle #35

How to Set up CI/CD Pipelines for Flutter in Bitrise

How to get Jenkins build job details?

Quantum and Classical Stacks

Announcement on LBank will delay the listing of FKX(FortKnoxster)

Clumsy Pete —Community, Contract, Future

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Maciej

Maciej

DevOps Consultant. I’m strongly focused on automation, security, and reliability.

More from Medium

Azure App Service Networking ,Vnet Integration and Access Restriction

Use Terraform and Azure DevOps to Provision Azure Kubernetes Service (AKS)

Automatic Update of API in Azure API Management using Terraform and Swagger

Deploy Web API to Azure API Management via Azure Devops CI/CD pipelines — Part 2