Azure App Service
Hosting patterns and best practices for Azure App Service.
When to Use
- Traditional web applications
- REST APIs without containerization
- .NET, Node.js, Python, Java, PHP applications
- When Docker is not required/desired
- When built-in deployment slots are needed
Service Type in azure.yaml
services:
my-web:
host: appservice
project: ./src/my-webRequired Supporting Resources
| Resource | Purpose |
|---|---|
| App Service Plan | Compute hosting |
| Application Insights | Monitoring |
| Key Vault | Secrets (optional) |
Runtime Stacks
💡 Tip: Prefer Linux App Service Plans for Node.js, Python, and Java. Use Windows only when explicitly required (e.g. .NET Framework). See Bicep Patterns for Linux vs Windows configuration.
Linux (recommended)
| Language | linuxFxVersion |
|---|---|
| Node.js 24 | NODE|24-lts |
| Node.js 22 | NODE|22-lts |
| Python 3.14 | PYTHON|3.14 |
| .NET 10 | DOTNETCORE|10.0 |
| Java 21 | JAVA|21-java21 |
Windows
| Language | Setting |
|---|---|
| Node.js | WEBSITE_NODE_DEFAULT_VERSION: '~24' (app setting) |
| .NET 10 | Built-in (no extra config) |
SKU Selection
| SKU | Use Case |
|---|---|
| F1/D1 | Development/testing (free/shared) |
| B1-B3 | Small production, basic features |
| S1-S3 | Production with auto-scale, slots |
| P1v3-P3v3 | High-performance production |
Health Checks
Always configure health check path:
siteConfig: {
healthCheckPath: '/health'
}Endpoint should return 200 OK when healthy.
Templates
For App Service templates with composable recipes (SQL, Cosmos DB, Auth, Redis), see Template Selection.
Common Data Backends
When pairing App Service with a data layer, load the corresponding service references:
| Data Service | Reference |
|---|---|
| Azure SQL | SQL Database |
| Cosmos DB | Cosmos DB |