Deploy a .NET App to Azure Container Apps
Go from an empty folder to a public HTTPS URL on Azure in six short parts. Build a small .NET 10 web app, containerize it with Docker, push it to Azure Container Registry and deploy it to Azure Container Apps, then read its logs, understand scaling and cost, and clean everything up.
Start with Part 1Build the App
Start a 6-part beginner series by building a small .NET 10 web app that reports its own host name, .NET version and uptime. Install the SDK, create the project, understand every line, and run it in your browser.
Containerize It with Docker
Package the .NET app into a Docker container with a multi-stage Dockerfile. Learn why multi-stage builds cut the image from 945 MB to 262 MB, why you run as a non-root user, and what a .dockerignore actually protects you from.
Resource Group and Container Registry
Create your first two Azure resources in the portal — a resource group and an Azure Container Registry. Every field explained, plus honest pricing and why leaving the admin user disabled is the right default.
Push Your Image to the Registry
Sign in to Azure Container Registry and push your image — and avoid the exec format error that catches every Apple Silicon user. Covers az acr login, docker buildx, platform targeting and why you should never deploy the latest tag.
Deploy to Azure Container Apps
Create an Azure Container Apps environment and deploy your image to a live public HTTPS URL. Covers every tab of the portal wizard, managed identity image pulls, target port 8080, right-sizing CPU and memory, and the free monthly grant.
Logs, Scaling, Cost and Cleanup
Finish the series by reading live logs, understanding revisions and scale-to-zero, working out what the app actually costs against the free monthly grant, running through a production checklist, and deleting everything cleanly.
