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/templates/recipes/README.md

App Service Template Recipes — REFERENCE ONLY

Composable IaC + source code modules that extend the Web API or Web App base template to support specific Azure service integrations.

Architecture

Base Template (per language/scenario, from AZD gallery)
       │
       ├── Source code (REST API or full-stack web app)
       ├── IaC (App Service Plan, App Service, App Insights, UAMI, RBAC)
       └── AZD config (azure.yaml, parameters)

       + Recipe (per integration)
       │
       ├── Source code delta (service client, middleware, config)
       ├── IaC delta (new resource + RBAC + networking modules)
       └── App settings delta
       │
       = Complete deployable project → `azd up`

Available Recipes

| Recipe | IaC Delta? | Source Delta? | Status | |--------|-----------|--------------|--------| | sql | ✅ SQL Server + DB + firewall + RBAC | ✅ EF Core (.NET), SQLAlchemy (Python), Prisma (Node.js) · ⏳ Spring Data JPA (Java): planned | ✅ Available | | cosmos | ✅ Cosmos account + DB + container + RBAC + PE | ✅ Cosmos SDK (.NET, Python, Node.js) · ⏳ Spring Data Cosmos (Java): planned | ✅ Available | | auth | ✅ App registration + Easy Auth config | ✅ MSAL / Identity middleware (.NET, Python, Node.js) · ⏳ Spring Security (Java): planned | ✅ Available | | redis | ✅ Redis cache + RBAC + PE | ✅ Distributed cache client (.NET, Python, Node.js) · ⏳ Spring Session (Java): planned | ✅ Available |

How It Works

Step 1: Fetch Base Template

# Pick template by language + scenario (see selection.md)
azd init -t <template> -e "$ENV_NAME" --no-prompt

Step 2: Apply Recipe

The skill reads the recipe's README.md for:

  • IaC module files to copy into infra/
  • App settings to add to web app configuration
  • RBAC roles with exact GUIDs (never generated by LLM)
  • Source code to add alongside existing application code
  • Networking to add private endpoints (conditional on VNET_ENABLED)

Step 3: Wire Into Base

Bicep: Add module reference in main.bicep, pass appServicePrincipalId Terraform: Copy .tf file into infra/, merge locals into web app settings

Step 4: Deploy

azd env set AZURE_LOCATION eastus2
azd provision --no-prompt
sleep 60
azd deploy --no-prompt

Design Principles

| Principle | Why | |-----------|-----| | Never synthesize base IaC | Always use proven AZD template repos | | Never modify base; only extend | Recipes are additive — no risk of breaking core | | Recipes own their RBAC | Exact role GUIDs, no LLM guessing | | Managed identity by default | No passwords or connection strings in app settings | | Health checks required | Every app must expose /health |