Access Private Url within Azure vNet with Azure Pipeline Microsoft Hosted Pipeline Agent via AKS pod in the vNet

If we are using Microsoft hosted agents for Azure pipelines to deploy Azure infrastucture and need to access vNet protected urls of services deployed, we can use a pod in AKS cluster within same vNet, as a jump host. This gives us access endpoints in vNet and ability to resolve DNS defined in private DNS zones of the vNet. Let's look at staep by step how to achive this goal, while using a Microsoft hosted agent in Azure pipelines.

The expectation is to access url such as 
http://es-search.sh.aks.ch-demo-dev-euw-002.net/demoindex001/_count  so AKS hosted elastic seach is accessed via a AKS pod and get the results to the pipeline agent as shown below. Since microsoft hosted agent is outside the vNET it cannot directly reach this elastc search (deployed in AKS) url.

TFS on Azure – 05. Set DNS in Virtual Network

To complete setting up the AD in Azure VM, next step is to setup the DNS for the Virtual Network. Setting up DNS is required to join other machine (TFS, RM server etc,) to the domain.
Go to the server manager of the AD server in Azure VM. Click on Toos—> DNS.


In the DNS Manager right click on Domain Controller and click on Properties.
 

In the Forwarded tab of the Properties window click on IP address and click Edit.


In Edit Forwarders select the IP and click Delete.


Then click OK.


Click Apply and close DNS Properties.


Now go to the Azure Management portal click on the Virtual Network and go to Configure tab.



In the dns servers provide Domain Controller name and the static internal IP assigned to it. Click on Save.


Click Yes for the below message.


This will update the Virtual Network





DNS setup done for the Virtual network.