Azure App Service
What it is
Azure App Service is Azure’s managed web-hosting platform for web apps, APIs, and supported web workloads. You deploy application code or a supported container; Azure operates the underlying web platform and operating system. Your team still owns the application’s code, identity, configuration, data, monitoring, and secure use of the platform.
Why it exists
Hosting a website by hand means provisioning VMs, installing a web server, patching the OS, and scaling manually. App Service abstracts all of that: deploy (via Git, ZIP, DevOps, or CI/CD) and the platform keeps it running and scales it on a plan.
Key ideas
- A web app is the application you deploy. An App Service plan supplies the compute capacity, pricing tier, scale settings, and supported features. They are separate resources.
- Scaling up changes the plan’s capacity; scaling out adds plan instances. Apps that share a plan share its compute resources and scaling effects.
- App Service supports web-platform capabilities such as custom domains, TLS, authentication integration, managed identities, access restrictions, VNet integration, and deployment slots, subject to the plan and configuration.
- App Service removes guest-OS administration but does not make application security or availability automatic. The app still needs secure identity, data protection, observability, and an appropriate network and resiliency design.
Northwind example
Northwind hosts its ordering API in App Service rather than on a VM. Luis deploys the API and configures its managed identity to retrieve a payment secret from Key Vault. The API runs on an App Service plan, which determines the available capacity and scale behavior. Northwind adds Application Insights to see checkout failures and uses a deployment slot to validate a new version before production.
Common confusion
- App Service is the managed hosting service; an App Service plan is the underlying capacity and billing container.
- VNet integration is mainly an outbound-connectivity feature. A private inbound address normally requires a separate private-endpoint design.
- A successful deployment does not mean the app is safe, correctly configured, or able to survive a dependency failure.
How it fits (diagram)
Where it appears in the route
Compare VMs and App Service through cloud-computing, then read app-service-plan, deployment-slots, app-service-networking, and application-insights.
Related
app-service-plan · deployment-slots · app-service-networking · azure-functions · application-insights · managed-identity · northwind-traders-case-study
📘 Source: Microsoft Learn — App Service overview, checked 2026-09-16.