Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article helps you troubleshoot various issues related to Azure Web App tasks and deployments.
Tasks documentation
As a first step, we recommend you review the documentation for the following tasks and ensure that all the parameters are correctly defined in the tasks used in the pipelines.
- Azure RM Web App deployment V4
- Azure Web App V1: Preferably use this task for App Services deployment. For more complicated scenarios like XML transformation, use Azure RM Web App deployment V4.
- Azure Function App: Consider using this task for Function App deployments.
- Azure File Copy
- Azure PowerShell (AzurePowerShell@5 - Azure PowerShell v5 task)
- Azure Key Vault
- Azure SQL deployment
Also, refer to the readme.doc in the GitHub repo and this Deploy to Azure article for details about the usage of these tasks.
If the task configuration looks fine, refer to the next steps for capturing debug logs.
Debug logs and tips for further debugging
Debug logs provide important details to help diagnose and troubleshoot issues related to Azure Web App tasks and deployments. Follow these steps to collect logs and further investigate these issues:
Enable debug logs by setting system.debug to True in the pipeline.
If possible, enable verbose logging from the Azure service side.
Review details related to Azure services, like networking, to see if it's restricted for public network access, if IPs are open for public network access, or if other network configurations may impact the issue. Also, verify the resource group name and region of the service.
If you noticed that the issue started happening suddenly, review the success and failure logs to check for any changes to the task or agent versions.
If you're using the Microsoft-hosted agent, check the runner-images documentation for any recent updates related to the Azure module that might have broken the pipeline.
Check the Azure DevOps status history and the Azure status history to find out if there are any outages.