Azure Web App Deployment Logs Show Incorrect Link to Azure DevOps Pipeline

DO1 Yauhen Zdanovich 40

I’m experiencing an issue with the deployment logs in Azure Web Apps. The deployment itself works fine, but when I navigate to the Deployment Center in the Azure Portal and click on the link to the Azure DevOps pipeline (to review the build or deployment details), I get a 404 error.

Here are the details of the setup:

Deployment Type:

I’m using a single YAML pipeline in Azure DevOps for both build and release. The deployment tasks include building the app and deploying it directly to the Azure Web App.

Observations:

For apps where I use separate build and release pipelines, the link in the deployment logs works correctly and redirects to the appropriate pipeline. For apps where I deploy using a single YAML pipeline, the link in the deployment logs is incorrect and leads to a “Page not found” error in Azure DevOps.

Here’s a simplified version of the deployment step in my YAML pipeline:

parameters:
  path_to_project: ''  
  net_version: ''
  artifact_name: ''  
  azure_subscription: ''

steps:  

- task: UseDotNet@2
  condition: ne('${{ parameters.net_version }}', 'globalJson')
  inputs:
    version: '${{ parameters.net_version }}'

- task: NuGetAuthenticate@1
  displayName: 'Authenticate to NuGet'

- task: DotNetCoreCLI@2
  displayName: 'Build'
  inputs:
    command: 'build'
    projects: '${{ parameters.path_to_project }}'
    arguments: ''

- task: DotNetCoreCLI@2
  displayName: 'Publish'
  inputs:
    command: 'publish'
    projects: '${{ parameters.path_to_project }}'
    publishWebProjects: false
    arguments: '--output $(Build.ArtifactStagingDirectory)'

- task: PublishBuildArtifacts@1
  displayName: 'Publish Artifact'
  inputs:
    PathtoPublish: '$(Build.ArtifactStagingDirectory)'
    ArtifactName: '${{ parameters.artifact_name }}'

- task: DownloadBuildArtifacts@0
  displayName: 'Download Artifact'
  inputs:
    artifactName: ${{ parameters.artifact_name }}
    downloadPath: '$(System.ArtifactsDirectory)/${{ parameters.artifact_name }}'

- task: AzureWebApp@1
  inputs:
    azureSubscription: ${{ parameters.azure_subscription }} 
    appType: webApp
    appName: ${{ parameters.app_name }}
    package: '$(System.ArtifactsDirectory)/**/*.zip' 
    deploymentMethod: 'auto'

enter image description here

Shree Hima Bindu Maganti 3,130 Reputation points Microsoft Vendor

2025-02-11T16:42:30.9933333+00:00

Hi @DO1 Yauhen Zdanovich ,
Thanks for the question and using MS Q&A platform.
Following up to see if you have chance to check @Ruben Fontijn previous response and help us with requested information to check and assist you further on this.
DO1 Yauhen Zdanovich 40 Reputation points

2025-02-11T18:06:49.8966667+00:00

@Shree Hima Bindu Maganti
Thanks for following up. Yes, I’ve reviewed @Ruben Fontijn response, and it is correct. The provided information aligns with my findings.

1 answer

Ruben Fontijn 0 Reputation points

2025-02-04T18:03:06.1766667+00:00

Same here.
The link to the build is
https://pii-removed:******@dev.azure.com/[tenant]/[project]/_git/esb-incore/%7B1%7D/_build?buildId=16345&_a=summary

This page is not found and results in 404 page.

The build link should be:

https://dev.azure.com/[tenant]/[project]/_build/results?buildId=16345&view=results
Please sign in to rate this answer.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

DO1 Yauhen Zdanovich 40 Reputation points

2025-02-13T20:01:38.5233333+00:00

Hi,

You misunderstood my case. @Ruben Fontijn didn’t resolve my issue; he was able to reproduce this bug in his resources. This confirms that the issue is reproducible and likely related to the interaction between Azure DevOps pipelines and the Azure Deployment Center.

Since this appears to be a broader issue, I need support from the Azure team to investigate and provide a resolution. Could you please escalate this matter accordingly?

Thanks.

Shree Hima Bindu Maganti 3,130 Reputation points Microsoft Vendor

2025-02-14T02:25:57.5566667+00:00

Hi @DO1 Yauhen Zdanovich ,
Apology for my previous response.
This issue happens because we're using a single YAML pipeline for both build and release. Azure Deployment Center expects separate build and release pipelines, which messes up the links in the deployment logs.

Head over to Azure DevOps > Pipelines and find the right build or release.

Check the URL against the one in the Deployment Center.

Instead of deploying directly in the build pipeline,

Build Pipeline → Publishes the artifact.

Release Pipeline → Deploys the artifact to Azure Web Apps.

This matches what Azure Deployment Center expects.
Modify your YAML pipeline to associate deployment tracking correctly,

- task: AzureAppServiceSettings@1 displayName: 'Update Deployment Tracking' inputs: azureSubscription: '<your-azure-subscription>' appName: '<your-app-name>' resourceGroupName: '<your-resource-group>' appSettings: | [ { "name": "WEBSITE_RUN_FROM_PACKAGE", "value": "$(Build.ArtifactStagingDirectory)/<your-artifact-name>.zip" } ]

Replace placeholders with your actual values.

Verify Service Connection Permissions

Ensure the Azure DevOps service connection has access to both build and release pipelines and the Azure Web App.
ref:
Azure DevOps YAML Pipelines Best Practices

Azure Web App Deployment Troubleshooting
Let me know if you have any further assistances.

DO1 Yauhen Zdanovich 40 Reputation points

2025-02-16T09:48:19.6166667+00:00

Ok, but I wouldn't use release pipelines for several reasons:

It's more useful for me to keep all pipelines in the same place.

It scales better because release pipelines only support a GUI for creation and editing. I can't use templates, which means I have to edit each release manually.

A YAML pipeline can contain the same tasks for deploying code to a web application.

The release pipeline interface is very unuseful and ugly, making it frustrating to work with.

This means that a release pipeline is not the only correct way to deploy my application. In fact, it feels like a step backward.

It also seems strange that, instead of adding the same functionality to YAML pipelines as release pipelines (e.g., adding deployment status to work items or properly linking to the pipeline from the Deployment Center), you're suggesting I switch back to a "modern" GUI-based option for creating release pipelines.

Shree Hima Bindu Maganti 3,130 Reputation points Microsoft Vendor

2025-02-17T12:31:17.9133333+00:00

Hi @DO1 Yauhen Zdanovich ,
Thanks for your Response.
The problem with the wrong link to the Azure DevOps pipeline in the deployment logs is likely because of how the Azure Deployment Center expects the pipeline structure. When you use a single YAML pipeline for both build and release, the Deployment Center might have trouble tracking the deployment, causing a 404 error when you try to access the pipeline link.

try splitting the build and release processes,

Build Pipeline: This should handle artifact publication.

Release Pipeline: This should manage deploying the artifact to Azure Web Apps.

By setting up your pipelines like this, you'll meet the Azure Deployment Center's expectations, which should solve the issue with the deployment log links.

If you want to keep everything in a single YAML pipeline, you might need to manually track deployments or tweak the deployment task configuration. But, this might still cause the same problems you're seeing now.
Deploy to App Service using Azure Pipelines

Azure Web App service deployments related issues

Frequently asked questions
Let me know if you have any further assistances.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Web App Deployment Logs Show Incorrect Link to Azure DevOps Pipeline

1 answer

Your answer