Overview

After deploying a container, verify that the application starts and responds. Use the default hostname from Azure CLI, then open it in a browser or call it with curl. If startup fails, use the troubleshooting tools (log stream, filesystem logs, Kudu).

Short notes (exam revision)

Get hostname: az webapp show ... --query defaultHostName -o tsv
Smoke test: browser or curl https://<hostname>
Failure path: container logs / log stream / Kudu (troubleshooting module)

Get the app URL

Azure CLI

az webapp show \
  --resource-group myResourceGroup \
  --name myDocumentProcessor \
  --query defaultHostName \
  --output tsv

Open https://<defaultHostName> in a browser, or:

Azure CLI

curl "https://$(az webapp show \
  --resource-group myResourceGroup \
  --name myDocumentProcessor \
  --query defaultHostName -o tsv)"

If verification fails

Typical next steps:

Stream logs: az webapp log tail
Confirm filesystem logging is enabled
Check Kudu Environment and /home/LogFiles/
Revisit port (WEBSITES_PORT), bind address (0.0.0.0), image/auth

Use cases

Post-deploy gate in a pipeline: fail the job if curl doesn’t return HTTP 200
After image tag update to v2, confirm the new host still serves /health
Hand-off checklist: hostname works before closing the change window

Exam tips

Know az webapp show --query defaultHostName
Verification is separate from “deploy succeeded” — always test HTTP response
Tie failures back to the troubleshoot topics (logs, Kudu, common issues)

Verify the deployment