[Managed DevOps Pools] Pipeline is not getting its agent (vnet with custom DNS)

Pierrick NEYME 0 Reputation points
2025-02-19T08:25:02.16+00:00

Hello,

We are trying to use a Managed DevOps Pool to implement CI/CD for an ADF resource within an Azure virtual network. The pool is created, but the Azure DevOps pipeline is never getting its agent, with nothing more information beside the “CustomScriptError” errorCode in Azure Metrics.

We set up a Standard_D2ads_v5 agent in West Europe region, the virtual network has no firewall and an empty NSG. Delegation in the subnet is fine (DevOpsInfrastructure).

I think we found out the cause : there is a custom DNS in the virtual network, if we switch to the Default one (Azure-provided), the agent is provisioned.

Can you tell us what should we configure to make it work with the custom DNS ?

Many thanks,

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
729 questions
Not Monitored
Not Monitored
Tag not monitored by Microsoft.
42,143 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.