Agent skill · software engineering · sickn33
azd-deployment
Prepare and verify authorized Azure Container Apps deployments with azd. Use for azure.yaml, Bicep, remote builds, managed identity and post-deploy checks.
Why this skill is useful
Adds executable scripts for deploying containerized applications to Azure Container Apps using Azure Developer CLI, which are not commonly documented.
What it needs
Requires azd installed locally. Requires azure account access. About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Azure Developer CLI (azd) Container Apps Deployment Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure. Authorization and preparation Inspect existing project files and the active tenant, subscription and environment first. Provisioning, deployment, role assignments and hook execution change cloud resources and may incur costs. Prepare the exact diff, target, estimated impact and rollback plan; execute only when the user explicitly authorizes that deployment. Do not print environment values or credentials into shared logs. Quick Start Core File Structure azure.yaml Configuration Minimal Configuration Full Configuration with Hooks Key azure.yaml Options Option Description -------- ------------- remoteBuild: true Build images in Azure Container Registry (recommended) context: . Docker build context relative to project path host: containerapp Deploy to Azure Container Apps infra.provider: bicep Use Bicep for infrastructure Environment Variables Flow Three-Level Configuration 1. Local .env - For local development only 2. .azure/<env>/.env - azd-managed, auto-populated from Bicep outputs 3. main.parameters.json - Maps env vars to Bicep parameters Parameter Injection Pattern Syntax: ${VARNAME} or ${VARNAME=defaultvalue} Setting Environment Variables Bicep Output → Environment Variable Deployment Repeatability Reconciliation and revision changes 1. Bicep is declarative - Resources reconcile to desired state 2. Remote builds tag uniquely - Image tags include deployment timestamp 3. ACR reuses layers - Only changed layers upload Preserve unmanaged changes deliberately Inventory custom domains, ingress, role assignments and other Portal-managed settings before preparing a deployment. Move desired settings into reviewed infrastructure code or prepare a specific restoration plan. Setting a property to null is not a general guarantee that Azure will preserve an out-of-band edit. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/azd-deployment--750e60