python-appservice-deploy

Create a Linux App Service Plan and a web app with the Python runtime, set SCM_DO_BUILD_DURING_DEPLOYMENT=true, then run az webapp deploy with a zip of your code. Flask and Django need no startup command because Oryx auto-detects them.

FastAPI requires an explicit startup command: python -m uvicorn main:app --host 0.0.0.0, set via az webapp config set --startup-file. The --host 0.0.0.0 flag is mandatory because uvicorn defaults to 127.0.0.1, which causes container ping timeouts.

This usually means a wrong or missing startup command, or the app binding to 127.0.0.1 instead of 0.0.0.0. Set a startup command that binds to 0.0.0.0 and verify your entry point module and callable names are correct.

Use az webapp deploy with --type zip; az webapp up is deprecated. The explicit flow is az webapp create with --runtime "PYTHON:3.14" followed by az webapp deploy, which gives you control over the plan, runtime, and build settings.

Use azd deploy when the workspace has an azure.yaml whose service host is appservice. If azure.yaml targets Container Apps or Functions, or no azure.yaml exists, use the az CLI path with az webapp deploy instead.

It covers code deployment only, not infrastructure concerns like VNet integration, Key Vault references, databases, or Bicep/Terraform-managed environments. Those scenarios should be handed off to a full infrastructure provisioning workflow such as azure-prepare.