EDIT: The solution was to set the startup command equal to the last command of my Docker file, which in my case was python app.py. This can be done either via the Azure Portal (go to your Azure Web App and then to Deployment Center), or by running:az webapp config show --name my-first-app --resource-group ... --startup-file="python app.py"
Using Azure Pipelines, I now have a Docker image in my Azure Container Registry. Let's say the registry is called myfirstregistry, the image is called myfirstimage, and the tag is "8" (which I determined by running az acr repository show-tags -n myfirstregistry --repository myfirstimage).
I then deployed an Azure Web App using this command: az webapp create --name my-first-app --resource-group ... --plan ... --deployment-container-image-name myfirstregistry.azurecr.io/myfirstimage:latest
When I go to my Azure Web App using the Azure Portal, under Overview -> Properties -> Web app -> Container Image it indeed says myfirstregistry.azurecr.io/myfirstimage:8.
But when I go to my web app, my-first-app.azurewebsites.net, it says "Your web app is running and waiting for your content". It seems as if the Docker image isn't running (yet). What am I missing here?



az webapp config set --name my-first-app --resource-group <your-resource-group> --startup-file "python app.py"and restart your Azure Web App to apply the changes.