AGENTIC MEMORY

Skills

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

← Back to Skills

azure-app-onboard

End-to-end orchestrator: from a business idea, app idea, or existing app to running Azure deployment with cost estimates and pre-deploy approval. Analyzes your app, auto-detects the right Azure services, scaffolds infrastructure code, and deploys — tailored to your app, not a template. Handles moving existing apps to Azure without rewriting or with minimal changes. WHEN: bring your app to Azure, plan my app, cost to run, is my code ready to deploy, deploy my app to the cloud, deploy all my services, what Azure services do I need, plan my Azure deployment, deploy my new app to Azure, one-click deploy, I have an app and want it on Azure, migrate my app to Azure, help me get started, build an app, no code yet, starter project. DO NOT USE FOR: use azd for deployment(use azure-deploy), optimizing existing costs (use cost-optimization), code readiness checks only (use azure-app-onboard-prereq).

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-app-onboard 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 · 11

references/pipeline-rules-runtime.md

Pipeline Rules — Runtime Reference

Known platform bugs and deploy timing. Read before deploy completion or on scaffold/deploy error.

For core pipeline rules (approval gates, phase lifecycle, session artifacts, security baseline), see pipeline-rules.md.

Known Platform Bugs

| Bug | Symptom | Workaround | |-----|---------|------------| | SWA CLI Windows path with spaces | StaticSitesClient.exe fails when workspace path contains spaces | Use a short, space-free temp path on FIRST attempt (e.g., C:\temp\swadeploy on Windows, /tmp/swa-deploy on macOS/Linux) — do NOT wait for retry. Copy app content to the temp path before running swa deploy. | | az deployment sub validate HTTP stream | "HTTP response stream consumed" error (Azure CLI bug, also affects create in CLI 2.75.0+) | validate: use az deployment sub what-if instead. create: use az rest --method PUT on deployment URI as fallback. | | az quota list extension error | PermissionError: [WinError 5] blocks extension commands | Use az rest instead (see sku-quota-validation.md) | | Managed identity sidecar OOM on free/basic-tier Linux | 503 Service Unavailable with Microsoft.Azure.WebSites.DataProtection or /msi/token timeout | Avoid managed identity on free/basic-tier Linux compute (F1, B1) — use connection strings or upgrade to S1+ | | Compress-Archive path flattening | PowerShell's Compress-Archive -Path $files.FullName uses absolute paths, flattening directory structure | Use System.IO.Compression.ZipFile with relative paths instead | | AADSTS530084 (Terraform) | Token protection conditional access policy breaks azurerm provider auth; regular az CLI commands work fine | Re-scaffold as Bicep | | Secret values with shell special chars | Passwords containing $, `, !, ', " break when passed as inline CLI args (--parameters key=val) | ALWAYS pass secrets via main.parameters.json or terraform.tfvars — never as inline --parameters args. For deploy-phase secret seeding (az keyvault secret set), use --file with a temp file or pipe from stdin to avoid shell interpolation. | | az acr task logs encoding crash | UnicodeEncodeError on Windows from Unicode chars in build logs | Use --no-format + strip non-ASCII, or REST API listLogSasUrl | | create tool nested path failure | "Parent directory does not exist" when creating files in .copilot-azure/sessions/{id}/ | Run New-Item -ItemType Directory -Path {parent} -Force before create. Platform tool limitation — agent always recovers. | | Windows PowerShell az rest 415 error | az rest --method put --body '{json}' returns 415 Unsupported Media Type on Windows PowerShell | Add --headers "Content-Type=application/json" to every az rest --method put call |

Deploy Timing

  • F1 App Service cold-start: After IaC creation, F1 plans need 30–120 seconds before the Kudu sidecar is ready. Deploying code immediately after az deployment group create returns causes 504 Gateway Timeout. Wait for sidecar readiness before code deployment.
  • Identity tag resolution: Resolve deployed-by once at session start via az ad signed-in-user show. Without this, resources may receive inconsistent tag values (display name, UPN, or hardcoded strings) across different runs.

Shell Rules

⛔ Shell variables do NOT persist between tool calls. Generate secrets inline within the command that consumes them — never store in $env: for later use. Use synchronous shells for all deploy-phase operations.