Posts

In distributed Azure architectures, it’s necessary to split up your virtual network infrastructure into different parts. This may happen over different Azure regions, or different subscriptions. Even in networks that are distributed, we’ll need a mechanism to communicate between these different networks. For this, we can use virtual network peering. Virtual network peering enables us to connect two or more virtual networks in Azure, whether they are in the same Azure region or not. The traffic between peered virtual networks is private, and they appear as one for connectivity purposes. Traffic between virtual machines in peered networks uses the Microsoft backbone infrastructure. ...

To facilitate communication between resources in Azure deployed in virtual networks, we can use domain name resolution over relying on IP address, making the communication process simpler. In Azure, DNS is split into two areas: Public DNS, and Private DNS. Domain Name System, otherwise known as DNS, is responsible for resolving a service name to an IP address. Azure DNS provides DNS hosting, resolution, and load balancing for your Azure applications. In this article, I’ll talk about the differences between Public DNS Domains and how we can delegate DNS domains. Then i’ll talk about how Private DNS works in Azure, and how we can set up Private DNS Zones in Azure. ...

Azure Virtual Networks use private IP addresses which aren’t routable on public networks. To enable support networks that exist both in Azure and on-prem environments, we need to configure IP addressing for both networks. Public IP addresses allow resources on the internet to communicate with Azure, and also enable outbound communication for Azure resources to public-facing services on the internet. In Azure, we can create public IP addresses and assign them to specific resources. ...

Azure Virtual Networks (or VNETs) are the fundamental building block for private networks in Azure. We can built Azure VNETs that are similar to on-prem networks, with the benefit of Azure infrastructure. We can create VNETs with their own CIDR block, and link them to other Azure VNETs and on-prem networks (providing that there’s no overlap with CIDR blocks). We can also control DNS server settings, segmentation of VNETs into subnets, and more. ...

For one of my side projects, I use GitHub Actions to build and deploy my various microservices to Azure. In my workflows, I’ll often retrieve a value (such as getting the name of a container registry), and use the set-output command within my pipeline so that I can use the value of that output further down my pipeline. This is an example of what using the set-output command would look like in your GitHub Action workflow: ...