Name or service not known (dc.services.visualstudio.com:443)

Khandu Shinde 110 Reputation points
2024-07-16T13:52:26.1666667+00:00

I was performing build and deployment of Azure app service using Azure DevOps.

Build step is showing successful but publish artifact giving warning as follow. Also artifact is uploaded successfully.

User's image

Warning, ApplicationInsightsTelemetrySender failed to TrackEvent(PipelineArtifact.UploadAsync) System.Net.Http.HttpRequestException: Name or service not known (dc.services.visualstudio.com:443)

User's image

Can you please help me to solve this issue?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,556 questions
{count} votes

1 answer

Sort by: Most helpful
  1. ajkuma 25,396 Reputation points Microsoft Employee
    2024-07-19T12:24:00.8533333+00:00

    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.


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.