AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-prepare

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-prepare at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 164

references/services/app-service/README.md

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-web

Required 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 |

References