Azure App Onboard
MicrosoftOfficialCreated by Microsoft
- Skill
- Workflow
- Cloud and DevOps
- MIT
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Azure App Onboard is a comprehensive workflow agent designed to take a business idea or an existing codebase and transition it to a running Azure deployment. It automates the entire lifecycle from initial discovery and architecture planning to infrastructure scaffolding and final deployment. The skill is built to be intelligent and tailored, analyzing the specific requirements of your application rather than relying on generic templates. It includes built-in approval gates for both the architecture plan and the final deployment, ensuring you maintain control over costs and resource configuration throughout the process.
What it does
- Analyzes your application code or business idea to determine the optimal Azure service stack.
- Generates custom infrastructure-as-code (IaC) files tailored to your specific application needs.
- Provides detailed cost estimates for the proposed Azure infrastructure before deployment.
- Executes the deployment of resources directly to your Azure subscription.
- Handles the migration of existing applications to Azure with minimal code changes.
- Provides a structured, step-by-step onboarding experience for developers of all experience levels.
When to use it
- When you have an application and want to deploy it to Azure but are unsure which services to use.
- When you need to migrate an existing application to the cloud without a complete rewrite.
- When you require a cost estimate for your infrastructure before committing to a deployment.
- When you need guided, end-to-end assistance for setting up a new Azure project.
- When you want to verify if your current codebase is ready for a cloud deployment.
Advantages
- Eliminates guesswork by auto-detecting the right Azure services for your specific stack.
- Reduces manual effort by automating the scaffolding of infrastructure-as-code.
- Ensures transparency with mandatory approval gates for architecture and deployment.
- Provides cost visibility early in the planning phase.
- Supports a wide range of scenarios from greenfield projects to existing app migrations.
Usage examples
- “I have a Python web app and want to deploy it to Azure. Can you help me get started?”
- The agent will initiate the discovery phase, scan your codebase, propose an architecture, and guide you through the deployment process.
- “I need to move my existing application to Azure, but I'm not sure what services I need. Can you plan this for me?”
- The agent will analyze your app's requirements, suggest the appropriate Azure services, and provide a cost estimate for your approval.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/microsoft/azure-app-onboard/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip azure-app-onboard.zip -d .agents/skills
Documentation by Microsoft
Azure App Onboard
⛔ Every repo goes through the full pipeline (Steps 1–10). No exceptions. Do not skip steps, refuse, or short-circuit based on what you recognize. Follow the Workflow table below sequentially — read each step's references before acting.
Quick Reference
| Property | Value |
|---|---|
| Best for | Developers who know what to build but not which Azure services to use |
| Inputs | Business idea or existing codebase, budget/scale preferences (optional) |
| Outputs | Architecture plan, cost estimate, IaC files, deployed Azure resources |
| Phases | Discover → Architect → Scaffold → Deploy (self-contained, no external skill calls) |
When to Use This Skill
Deploy existing code without knowing which Azure services to use
Check if your existing code is ready to deploy to Azure
Move an existing app to Azure without rewriting or with minimal changes
Get cost estimates before committing to infrastructure
Understand architecture decisions and rejected alternatives
Get answers to Azure architecture or service selection questions (e.g., "What database should I use?")
Get guided Azure onboarding without prior experience
When NOT to Use
| Scenario | Use Instead |
|---|---|
Run azd up or execute an existing deployment | azure-deploy |
| Optimize existing Azure spend | cost-optimization from the optional azure-cost plugin |
| Generate Bicep/Terraform for a known architecture | azure-prepare |
| Validate infrastructure or run preflight checks | azure-validate |
| Troubleshoot a running Azure deployment | azure-diagnostics |
| Deploy to or manage AKS/Kubernetes directly | azure-kubernetes |
| Look up or list existing Azure resources | azure-resource-lookup |
If cost-optimization is unavailable, explain that it is provided by the
optional azure-cost plugin and direct the user to their client's supported
plugin installation flow; do not imply the handoff completed.
Pipeline Rules
⛔ You MUST read
references/pipeline-rules.mdat the start of every AppOnboard session. It contains approval gates, phase lifecycle, session artifacts, deploy-as-is, and security baseline rules.
Workflow
⛔ Deploy recovery: After deploy gate approval OR before any
az deployment/az webapp deploy/az acr build— if you haven't readdeploy/PHASE.md, read.copilot-azure/sessions/{id}/deploy-checklist.mdfirst, thendeploy/PHASE.md. ⛔ NEVER invoke{"skill": "azure-deploy"}— that is a DIFFERENT skill for a DIFFERENT workflow.
⛔ Post-scaffold transition (MANDATORY): Immediately after
scaffold-manifest.jsonis written, YOUR NEXT ACTION MUST be Step 8 (Deploy Approval Gate) — NOT a summary report, NOT a "here are the generated files" message, NOT a completion signal. Confirmcontext.jsonhascompletedPhases: [...,"scaffold"]+currentPhase: "deploy"(update it yourself if the scaffold subagent didn't). Re-read approval-gates.md § Deploy Gate if evicted from context (scaffold reference loading is heavy), then present the exact prompt: "🚀 Ready to deploy? (Yes / Run manually / Edit plan / Cancel)". This gate is the LAST content in your response — wait for the user's reply.
| # | Step | Action | Reference |
|---|---|---|---|
| 1 | Session check + Azure login | Create/resume session, verify Azure CLI auth, resolve subscription + user identity | ⛔ You MUST read session-protocol.md |
| 2 | Scope triage | Check azd markers, triage question. Empty workspace or code-only (no infra) → Step 3 directly. | ⛔ Read intent-gathering.md § Scope Triage |
| 3 | Prereq scan | ⛔ Skip if completedPhases includes "prereq". Otherwise: invoke {"skill": "azure-app-onboard-prereq"}. Write prereq-output.json, update context.json. Halt if: overallHealth: "blocked" OR routeToSkill set. | |
| 4 | Gather intent | Present prereq results, confirm stack + Azure services, ask remaining questions. | ⛔ Read intent-gathering.md § After Prereq Returns |
| 5 | Plan architecture | Write prepare-plan.json. | ⛔ You MUST read prepare/PHASE.md |
| 6 | Scaffold approval gate | Display plan for user approval BEFORE generating any files. | ⛔ Read approval-gates.md § Scaffold Gate |
| 7 | Scaffold | Generate IaC, self-review. Write scaffold-manifest.json. Update context.json. | ⛔ You MUST read scaffold/PHASE.md |
| 8 | Deploy approval gate | Display validation summary. ⛔ After approval: FIRST read deploy-checklist.md → deploy/PHASE.md. NEVER {"skill": "azure-deploy"}. | ⛔ Read approval-gates.md § Deploy Gate |
| 9 | Deploy | Execute IaC, health-check. Write deploy-result.json. | ⛔ You MUST read deploy/PHASE.md |
| 10 | Handoff | Surface deployment identity, cleanup commands, next steps. | ⛔ You MUST read handoff-protocol.md |
Error Handling
| Error | Remediation |
|---|---|
| Phase fails | Halt, report phase + error. User decides: retry, skip, abort. |
| MCP server unavailable | Skip affected checks, add disclaimer to costEstimate.assumptions[] and every approval gate. |
| Missing RBAC | Report required role + az role assignment command. |
Shared references: MCP tools (cross-phase tool parameters) | IaC resources (Azure resource docs for troubleshooting)
Files
- ATTRIBUTION.mdAdded by AutoGineer983 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md6.6 KiB
- deploy/PHASE.md7.5 KiB
- deploy/references/approval-gate-template.md2.9 KiB
- deploy/references/blocked-patterns.md5.7 KiB
- deploy/references/code-deployment-appservice.md4.6 KiB
- deploy/references/code-deployment-container-apps.md8.4 KiB
- deploy/references/code-deployment-swa.md5.7 KiB
- deploy/references/database-post-deploy.md4.5 KiB
- deploy/references/deploy-checklist-template.md10.1 KiB
- deploy/references/deploy-safety.md4.5 KiB
- deploy/references/deploy-schemas.tsScript3.5 KiB
- deploy/references/error-classification.md3.6 KiB
- deploy/references/health-check-patterns.md5.5 KiB
- deploy/references/mcp-tools.md5.5 KiB
- deploy/references/portal-links.md3.1 KiB
- deploy/references/preflight-checks.md4.4 KiB
- deploy/references/subagent-preflight.md5.1 KiB
- prepare/PHASE.md6.4 KiB
- prepare/references/deploy-strategy.md6.8 KiB
- prepare/references/mcp-tools.md5.6 KiB
- prepare/references/naming-patterns.md4.6 KiB
- prepare/references/prepare-schemas.tsScript7.0 KiB
- prepare/references/pricing-guide-services.md8.4 KiB
- prepare/references/pricing-guide.md4.0 KiB
- prepare/references/service-mapping.md8.5 KiB
- prepare/references/sku-matrix.md3.2 KiB
- prepare/references/sku-quota-validation.md9.0 KiB
- prepare/references/subagent-pricing.md2.5 KiB
- prepare/references/subagent-quota.md3.5 KiB
- prepare/references/validation-rubric.md2.3 KiB
- references/approval-gates.md8.4 KiB
- references/azd-template-routing.md4.7 KiB
- references/handoff-protocol.md7.8 KiB
- references/iac-resources.md2.6 KiB
- references/intent-gathering.md2.2 KiB
- references/mcp-tool-reference.md3.7 KiB
- references/pipeline-rules-runtime.md3.5 KiB
- references/pipeline-rules.md6.3 KiB
- references/session-protocol.md8.0 KiB
- references/session-schemas.tsScript5.2 KiB
- references/subscription-resolution.md2.1 KiB
- scaffold/PHASE.md14.2 KiB
- scaffold/references/bicep-app-service.md5.4 KiB
- scaffold/references/bicep-container-apps.md9.3 KiB
- scaffold/references/bicep-patterns-data.md4.0 KiB
- scaffold/references/bicep-patterns-security.md7.8 KiB
- scaffold/references/bicep-patterns.md6.8 KiB
- scaffold/references/bicep-swa.md757 B
- scaffold/references/cicd-pipelines.md325 B
- scaffold/references/dockerfile-generation.md4.1 KiB
- scaffold/references/env-var-secrets.md4.1 KiB
- scaffold/references/error-handling.md1.5 KiB
- scaffold/references/iac-generation-rules.md6.6 KiB
- scaffold/references/mcp-tools.md7.0 KiB
- scaffold/references/rbac-roles.md3.8 KiB
- scaffold/references/scaffold-healing-rules.md3.3 KiB
- scaffold/references/scaffold-schemas.tsScript3.5 KiB
- scaffold/references/self-healing.md2.3 KiB
- scaffold/references/self-review-checklist.md9.0 KiB
- scaffold/references/self-review-procedure.md2.3 KiB
- scaffold/references/subagent-iac-gen.md9.5 KiB
- scaffold/references/subagent-review.md3.5 KiB
- scaffold/references/subagent-validate.md7.2 KiB
- scaffold/references/terraform-patterns.md6.9 KiB
- scaffold/references/validation-and-manifest.md5.1 KiB
- scaffold/references/waf-checklist.md2.3 KiB
- scaffold/scripts/scaffold-conformance.ps1Script12.8 KiB
- scaffold/scripts/scaffold-conformance.shScript13.8 KiB
scaffold/scripts/scaffold-conformance.sh
#!/usr/bin/env bash
# Scaffold -> Deploy conformance gate (bash twin of scaffold-conformance.ps1).
# Checks generated IaC against the plan for semantic defects `az bicep build` cannot catch.
#
# Usage: scaffold-conformance.sh <sessionPath> [infraPath]
# Output: JSON { passed, failures:[{id,detail,file}] } to stdout.
# Exit: 0 = pass, 1 = one or more BLOCK failures.
#
# Pure-text checks (tags, TLS, purge, deployer role, plaintext secret) always run.
# Plan-dependent checks (version, services-complete, db-name, warn-fixed) run only when `jq` is present.
set -u
SESSION_PATH="${1:?usage: scaffold-conformance.sh <sessionPath> [infraPath]}"
INFRA_PATH="${2:-infra}"
PLAN="$SESSION_PATH/prepare-plan.json"
MAIN="$INFRA_PATH/main.bicep"
PARAMS="$INFRA_PATH/main.parameters.json"
main_bicep="$( [ -f "$MAIN" ] && cat "$MAIN" || true )"
params_raw="$( [ -f "$PARAMS" ] && cat "$PARAMS" || true )"
iac="$( find "$INFRA_PATH" -name '*.bicep' -type f 2>/dev/null -exec cat {} + || true )"
HAVE_JQ=0; command -v jq >/dev/null 2>&1 && HAVE_JQ=1
# failures accumulator (JSON objects, newline-separated)
fails=""
add_fail() { # id detail file
local obj; obj="$(printf '{"id":"%s","detail":"%s","file":"%s"}' "$1" "$2" "$3")"
fails="${fails:+$fails,}$obj"
}
iac_has() { printf '%s' "$iac" | grep -qE "$1"; }
# 1. TAGS-NO-CAMEL
if printf '%s' "$main_bicep" | grep -qE 'appOnboard(Skill|SessionId)|createdAt:|deployedBy:'; then
add_fail "TAGS-NO-CAMEL" "camelCase tag keys found — use hyphenated ('app-onboard-skill' ...)" "infra/main.bicep"
fi
# 12. DIAG-GATED — we don't scaffold diagnostic-settings; if present it must be gated behind enableDiagnostics (default false) or removed. Unconditional wiring blocks the first deploy.
# Match an actual diagnostic module/resource declaration, not a prose comment mentioning 'diagnostic'.
if printf '%s' "$main_bicep" | grep -qE 'module[[:space:]]+[A-Za-z]*[Dd]iagnostic|Microsoft\.Insights/diagnosticSettings' && ! printf '%s' "$main_bicep" | grep -q 'enableDiagnostics'; then
add_fail "DIAG-GATED" "diagnostic-settings module wired without an enableDiagnostics gate — gate it (module ... = if (enableDiagnostics), default false) or remove it; unconditional wiring blocks the first deploy" "infra/main.bicep"
fi
# 2. NO-PLAINTEXT-SECRET (jq-free: awk over the params file so it runs on hosts without jq)
if [ -n "$params_raw" ]; then
bad_keys="$(printf '%s' "$params_raw" | awk '
{ line=tolower($0) }
line ~ /"[a-z0-9_]*(password|secret|connstring|connection)[a-z0-9_]*"[ \t]*:/ {
n=split($0, parts, "\"")
for (i=1;i<=n;i++) { if (tolower(parts[i]) ~ /(password|secret|connstring|connection)/) { pend=parts[i]; break } }
}
pend != "" && line ~ /"value"[ \t]*:[ \t]*"[^"]+"/ { print pend; pend="" }
/}/ { pend="" }
')"
if [ -n "$bad_keys" ]; then
while IFS= read -r k; do
[ -z "$k" ] && continue
add_fail "NO-PLAINTEXT-SECRET" "parameter '$k' has a literal value — must be @secure(), passed at deploy" "infra/main.parameters.json"
done <<< "$bad_keys"
fi
fi
# 2b. NO-BICEP-LITERAL-SECRET (pure-text) — secret values must be @secure() params, never quoted literals.
# Property name must end in 'password'/'connectionString' right before ':' (so 'secretName' etc. never match).
if [ -n "$iac" ]; then
if printf '%s' "$iac" | grep -qiE "[A-Za-z]*(password|connectionstring)[[:space:]]*:[[:space:]]*'[^']+'"; then
k="$(printf '%s' "$iac" | grep -oiE "[A-Za-z]*(password|connectionstring)[[:space:]]*:[[:space:]]*'[^']+'" | head -n1 | sed -E "s/[[:space:]]*:.*//")"
add_fail "NO-BICEP-LITERAL-SECRET" "property '$k' assigned a literal secret in Bicep — use an @secure() param passed at deploy" "infra/"
fi
if printf '%s' "$iac" | grep -qE ":[[:space:]]*'[^']*(Password=|AccountKey=|SharedAccessKey=|://[^:@/ ]+:[^:@/ ]+@)[^']*'"; then
add_fail "NO-BICEP-LITERAL-SECRET" "quoted literal contains an embedded credential (Password=/AccountKey=/user:pass@) in Bicep — use an @secure() param" "infra/"
fi
fi
# service-name -> resource-type map (longest keys first so 'container apps environment' wins)
declare -a MAP_KEYS=( "container apps environment" "container app" "container registry" "mysql" "postgres" \
"key vault" "log analytics" "application insights" "static web app" "app service" "functions" \
"sql" "cosmos" "redis" "storage" "service bus" "event hub" )
map_type() {
case "$1" in
*"container apps environment"*) echo 'Microsoft\.App/managedEnvironments';;
*"container app"*) echo 'Microsoft\.App/containerApps';;
*"container registry"*) echo 'Microsoft\.ContainerRegistry/registries';;
*mysql*) echo 'Microsoft\.DBforMySQL/flexibleServers';;
*postgres*) echo 'Microsoft\.DBforPostgreSQL/flexibleServers';;
*"key vault"*) echo 'Microsoft\.KeyVault/vaults';;
*"log analytics"*) echo 'Microsoft\.OperationalInsights/workspaces';;
*"application insights"*) echo 'Microsoft\.Insights/components';;
*"static web app"*) echo 'Microsoft\.Web/staticSites';;
*"app service"*|*functions*) echo 'Microsoft\.Web/sites';;
*sql*) echo 'Microsoft\.Sql/servers';;
*cosmos*) echo 'Microsoft\.DocumentDB/databaseAccounts';;
*redis*) echo 'Microsoft\.Cache/redis';;
*storage*) echo 'Microsoft\.Storage/storageAccounts';;
*"service bus"*) echo 'Microsoft\.ServiceBus/namespaces';;
*"event hub"*) echo 'Microsoft\.EventHub/namespaces';;
*) echo '';;
esac
}
svc_names=""; db_version=""; app_db_name=""; has_mysql=0; has_pg=0
if [ "$HAVE_JQ" = 1 ] && [ -f "$PLAN" ]; then
svc_names="$(jq -r '.services[].name' "$PLAN" 2>/dev/null)"
app_db_name="$(jq -r '.appDbName // empty' "$PLAN" 2>/dev/null)"
printf '%s' "$svc_names" | grep -qiE 'mysql' && has_mysql=1
printf '%s' "$svc_names" | grep -qiE 'postgres' && has_pg=1
# 3. SERVICES-COMPLETE
while IFS= read -r name; do
[ -z "$name" ] && continue
lc="$(printf '%s' "$name" | tr '[:upper:]' '[:lower:]')"
expected="$(map_type "$lc")"
if [ -n "$expected" ] && ! iac_has "$expected"; then
add_fail "SERVICES-COMPLETE" "planned service '$name' has no matching resource ($expected) in IaC" "infra/"
fi
done < <(printf '%s\n' "$svc_names")
else
# jq absent: fall back to grep for the DB-type presence (drives TLS/name checks below)
printf '%s' "$iac" | grep -qE 'Microsoft\.DBforMySQL/flexibleServers' && has_mysql=1
printf '%s' "$iac" | grep -qE 'Microsoft\.DBforPostgreSQL/flexibleServers' && has_pg=1
fi
# --- Managed database checks ---
if [ "$has_mysql" = 1 ] || [ "$has_pg" = 1 ]; then
# 4. DB-VERSION-MATCH — each server's version must equal its capabilities-verified plan value.
# Scope the match to the DB resource block so an unrelated 'version:' elsewhere isn't picked up.
if [ "$HAVE_JQ" = 1 ] && [ -f "$PLAN" ]; then
while IFS=$'\t' read -r dbkind dbver; do
[ -z "$dbver" ] && continue
case "$dbkind" in
*MySQL*) marker='Microsoft[.]DBforMySQL/flexibleServers';;
*) marker='Microsoft[.]DBforPostgreSQL/flexibleServers';;
esac
iac_ver="$(printf '%s\n' "$iac" | awk -v marker="$marker" '
$0 ~ marker { armed=1 }
armed==1 && match($0, /version:[ \t]*'"'"'[^'"'"']+'"'"'/) {
v=substr($0,RSTART,RLENGTH); sub(/version:[ \t]*'"'"'/,"",v); sub(/'"'"'.*/,"",v); print v; exit
}')"
if [ -n "$iac_ver" ] && [ "$iac_ver" != "$dbver" ]; then
add_fail "DB-VERSION-MATCH" "$dbkind IaC version '$iac_ver' != plan '$dbver'" "infra/modules"
fi
done < <(jq -r '.services[]? | select(.name|test("MySQL|PostgreSQL")) | [.name, (.version // "")] | @tsv' "$PLAN" 2>/dev/null)
fi
# 5. DB-TLS-ON (MySQL, pure-text)
if [ "$has_mysql" = 1 ] && ! iac_has 'require_secure_transport'; then
add_fail "DB-TLS-ON" "MySQL module missing require_secure_transport config" "infra/modules"
fi
# 6. DB-NAME-PRESENT (needs plan.appDbName from jq)
if [ -n "$app_db_name" ] && ! iac_has 'flexibleServers/databases'; then
add_fail "DB-NAME-PRESENT" "app DB '$app_db_name' declared but no flexibleServers/databases resource" "infra/modules"
fi
# 10. MYSQL-NO-NETWORK-BLOCK (MySQL, pure-text) — public flow must omit the network block;
# an empty delegatedSubnetResourceId is rejected by ARM (LinkedInvalidPropertyId).
if [ "$has_mysql" = 1 ] && iac_has 'delegatedSubnetResourceId|privateDnsZoneResourceId'; then
add_fail "MYSQL-NO-NETWORK-BLOCK" "MySQL module includes a network block (delegatedSubnetResourceId) — omit it for public access; an empty value is rejected by ARM" "infra/modules"
fi
# 11. DB-LOGIN-NOT-RESERVED (pure-text) — administratorLogin must not be an Azure-reserved name.
if iac_has "administratorLogin:[[:space:]]*'(root|admin|administrator|guest|public|sa|azure_superuser|azure_pg_admin)'"; then
resv="$(printf '%s' "$iac" | grep -oE "administratorLogin:[[:space:]]*'[^']+'" | grep -oiE "(root|admin|administrator|guest|public|sa|azure_superuser|azure_pg_admin)" | head -n1)"
add_fail "DB-LOGIN-NOT-RESERVED" "administratorLogin uses a reserved name ('${resv}') — derive a safe login (e.g. '{project}admin'), never a compose-sourced reserved name" "infra/modules"
fi
fi
# --- Key Vault checks (pure-text) ---
if iac_has 'Microsoft\.KeyVault/vaults'; then
# 7. KV-NO-PURGE
if iac_has 'enablePurgeProtection'; then
add_fail "KV-NO-PURGE" "enablePurgeProtection present — omit it (policy may reject false)" "infra/modules"
fi
# 8. KV-DEPLOYER-ROLE
has_officer=0; iac_has 'b86a8fe4-44ce-4948-aee5-eccb2c155cd7' && has_officer=1
has_param=0; { iac_has 'deployerObjectId' || printf '%s' "$params_raw" | grep -q 'deployerObjectId'; } && has_param=1
if [ "$has_officer" != 1 ] || [ "$has_param" != 1 ]; then
add_fail "KV-DEPLOYER-ROLE" "missing deployer Key Vault Secrets Officer role and/or deployerObjectId param" "infra/modules/role-assignments.bicep"
fi
fi
# --- Container Apps / ACR checks (deterministic ARM-failure invariants) ---
if [ -n "$iac" ]; then
has_ca=0; iac_has 'Microsoft\.App/containerApps' && has_ca=1
has_cae=0; iac_has 'Microsoft\.App/managedEnvironments' && has_cae=1
has_acr=0; iac_has 'Microsoft\.ContainerRegistry/registries' && has_acr=1
# 13. CAE-APPLOGS — managedEnvironments log config MUST nest under appLogsConfiguration; a bare
# top-level logAnalyticsConfiguration fails deploy with ManagedEnvironmentInvalidSchema.
if [ "$has_cae" = 1 ] && iac_has 'logAnalyticsConfiguration' && ! iac_has 'appLogsConfiguration'; then
add_fail "CAE-APPLOGS" "Container Apps Environment uses a bare logAnalyticsConfiguration — nest it under appLogsConfiguration.destination='log-analytics' (else ManagedEnvironmentInvalidSchema at deploy)" "infra/modules"
fi
# 14. CA-NO-REVISION-SUFFIX — a hardcoded revisionSuffix fails Phase 2 redeploy ('revision already exists').
if [ "$has_ca" = 1 ] && iac_has 'revisionSuffix[[:space:]]*:'; then
add_fail "CA-NO-REVISION-SUFFIX" "Container App sets revisionSuffix — omit it (ARM auto-generates); a hardcoded value fails Phase 2 redeploy" "infra/modules"
fi
# 15. CA-IMAGE-PARAM — two-phase deploy needs 'param containerImage' in main.bicep, else the Phase 2 override is silently ignored and the placeholder image persists.
if [ "$has_ca" = 1 ] && [ "$has_acr" = 1 ] && ! printf '%s' "$main_bicep" | grep -qE 'param[[:space:]]+containerImage'; then
add_fail "CA-IMAGE-PARAM" "main.bicep lacks 'param containerImage' — the Phase 2 image override is silently ignored and the placeholder persists (MANIFEST_UNKNOWN)" "infra/main.bicep"
fi
# 16. ACRPULL-GUID — near-miss detector: fixed AcrPull prefix present without the canonical full GUID = hallucinated last segment → RoleDefinitionDoesNotExist. Cannot false-positive.
if iac_has '7f951dda-4ed3-4680-a7ca-' && ! iac_has '7f951dda-4ed3-4680-a7ca-43fe172d538d'; then
add_fail "ACRPULL-GUID" "AcrPull role GUID is wrong — canonical value is 7f951dda-4ed3-4680-a7ca-43fe172d538d (RoleDefinitionDoesNotExist otherwise)" "infra/modules/role-assignments.bicep"
fi
# 17. ACR-NO-PREMIUM-POLICY — retention/trust/quarantine are Premium-only; on Basic/Standard ACR they fail SkuNotSupported. FP-safe: skipped if any 'Premium' SKU appears.
if [ "$has_acr" = 1 ] && iac_has '(retentionPolicy|trustPolicy|quarantinePolicy)[[:space:]]*:' && ! iac_has "'Premium'"; then
add_fail "ACR-NO-PREMIUM-POLICY" "ACR has a Premium-only policy (retention/trust/quarantine) but is not Premium — omit these for Basic/Standard (SkuNotSupported at deploy)" "infra/modules"
fi
fi
# 9. WARN-FIXED (needs jq to read prereq-output.json warnings[]) — prereq warnings flagged
# fixPhase:"scaffold" must land in the IaC. Only warnings with a provable signal are enforced;
# unverifiable ones are skipped (no false BLOCK). Extend the case map for new provable warning IDs.
PREREQ="$SESSION_PATH/prereq-output.json"
if [ "$HAVE_JQ" = 1 ] && [ -f "$PREREQ" ]; then
while IFS=$'\t' read -r wid wfix; do
[ -z "$wid" ] && continue
present=0
case "$wid" in
W-PG-SSL) printf '%s' "$iac" | grep -qiE 'PGSSLMODE|sslmode' && present=1 ;;
W-BUILDKIT) [ -n "$(find . -name 'Dockerfile.azure' -type f 2>/dev/null | head -n1)" ] && present=1 ;;
*) continue ;; # no deterministic signal — cannot verify, do not block
esac
if [ "$present" != 1 ]; then
add_fail "WARN-FIXED" "prereq warning '$wid' (fixPhase:scaffold) fix not found in IaC — $wfix" "infra/"
fi
done < <(jq -r '.warnings[]? | select(.fixPhase=="scaffold") | [.id, .fix] | @tsv' "$PREREQ" 2>/dev/null)
fi
if [ -z "$fails" ]; then
printf '{"passed":true,"failures":[]}\n'
exit 0
else
printf '{"passed":false,"failures":[%s]}\n' "$fails"
exit 1
fi
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs Node.js
Security
What our scanner noticed· Low risk
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/skills · .github/plugins/azure-skills/skills/azure-app-onboard · commit 0696600
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- microsoft/azure-skills
AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-app-onboard.zip