When Azure Container Apps Make More Sense Than App Service
A rundown of what Container Apps actually does differently
By Shehryar Hassan, Microsoft 365 & Azure Consultant
Someone on my team asked last week why we'd spin up a Container App instead of just using App Service, since both end up giving you a URL and a running app. It's a fair question, and the honest answer is that most of the time either one will work fine. The difference shows up at the edges.
What Container Apps actually adds
App Service runs your code on a platform Microsoft manages for you, and it's built around one app per plan, with scaling rules tied to that app. Container Apps sits on top of Kubernetes (you never see the cluster, but it's there) and is built for running several small services that talk to each other. If you've split something into a few microservices, or you're running background workers alongside your API, Container Apps gives you built-in service discovery and traffic splitting between revisions without extra setup.
The other thing Container Apps does well is scaling to zero. App Service can scale down, but on most plans there's always at least one instance running, which you're paying for. Container Apps can genuinely drop to nothing when there's no traffic and spin back up on the next request. For a low-traffic internal tool or an API that only gets hit a few times a day, that's real savings.
Where App Service still wins
If you're deploying a single web app and you want the simplest possible path, App Service is still less to think about. Deployment slots, easy custom domain and SSL setup, and a huge amount of existing documentation make it the safer default for a straightforward .NET, Node, or Python web app. You don't need to know anything about containers to use it, and for a lot of business apps that matters more than any scaling feature.
Container Apps also expects you to actually build and manage a container image. If your team isn't already doing that, you're adding a step to your pipeline that App Service just doesn't require.
My rule of thumb: if it's one app with a database behind it, App Service. If you're running multiple services, need scale to zero, or you're already containerizing things for other reasons, Container Apps is worth the extra setup.
Get new posts by email
One note when there is something worth reading. No spam, unsubscribe anytime.
Related articles
Azure Traffic Manager, What It Does and How It's Different From Load Balancer
Traffic Manager and Load Balancer sound like they do the same thing. They don't. One works at the DNS level across regions, the other spreads traffic inside one region. Here's what each is actually for.
Azure Front Door, What It Does and When You'd Actually Use One
Azure Front Door routes visitors to the closest healthy copy of your site and can add a free SSL certificate along the way. Here's when it actually earns its keep.
What an Azure Managed Identity Actually Does (and Why You Want One)
Azure managed identities let an App Service, Function App, or VM authenticate to other Azure resources without you ever having to store or rotate a secret.