Newly added Web app service in Azure not showing up in Azure DevOps dropdowns

[brianmich]

Hello.  I created a new Azure web app service in a new resource group as I have done many times before.  I created a CI/CD pipeline in Azure DevOps to deploy some Python code to the new app service, but the app service is not showing up in the dropdown list in the task.  I read some other posts that this has been an issue for a long time and takes hours for it to show up.  Is that truly the case?  I noticed the other app services I created are showing up, but not the one I created earlier in the day.

Thanks for your help!

Brian

[#2]

@brianmich 

What kind of Web app? Linux Web app?

[#3]

Yes a Linux Web app so I can deploy a simple Python web page up there. Thank you!

[#4]

There should be another one in the list

[#5]

@brianmich 

Make sure filter 'Linux Web app'

[#6]

Hi @brianmich ,

You can try two possible solutions:

1. Please check with the Service Connection in Azure to have the required RBAC Roles for the newly created App Service. You can do this by navigating to the Resource Group > newly created App Service > IAM > Check access review for the attached Service Connection in Azure.
Hint: You can find the attached service connection in Azure by going to Azure DevOps service connection in Azure DevOps project settings. Click on "Manage Service Principle", It will bring you to the Azure portal app registration.

2. Optional, Sometimes the DevOps portal didn't refresh so it won't show the newly created resource name. You can try to manually type the name of the newly created resource.

[#7 · Accepted solution]

Thanks for the suggestions, but this was the same issue that has seemingly been reported many times before and proved to be the same issue I encountered. It took 8 hours before the new app service was available to Azure DevOps. It is showing in my dropdown now. I could not even add the app service manually in the dropdown. That step still failed not able to see the app service. I suspect this may have something to do with the free tier of the app service, but not 100% sure on that yet.

My immediate issue is resolved, but the underlying root cause has not been resolved. That is an issue with Microsoft. Hopefully someone from Microsoft will see this and respond or take action. I have read that this is a very random intermittent issue so they may look at this as low priority.

Thanks for the responses everyone! Hope this helps someone else down the road.