Edit: Updating the answer shared by :Khandu Shinde,
Yes, the endpoint connection with Azure monitor was removed mistakenly in the code. Now rectified and resolved the same.
--
Apologies for the delayed response.
To better assist you on this, just to clarify, have you provisioned Azure VNET? are you leveraging self-hosted Azure DevOps Agents? Have you configured any network proxy?
Based on my understanding of your issue, the error you’re encountering seems to be related to DNS resolution for dc.services.visualstudio.com:443
, which is used by Azure DevOps and Application Insights.
As outlined in this doc section Azure Monitor private links rely on your DNS
Because Azure Monitor uses some shared endpoints (meaning endpoints that aren't resource specific), setting up a private link even for a single resource changes the DNS configuration that affects traffic to all resources. In other words, traffic to all workspaces or components is affected by a single private link setup.
Please ensure that your pipeline is correctly configured and that you have the correct settings for your Azure app service deployment. You can try creating a new pipeline or modifying your existing pipeline to see if that resolves the issue.
For more info - Deploy app service with private endpoint enabled via Azure DevOps
Kindly let us know how it goes, I'll follow-up with you further.