diagnosing-azure-deployment-failureslisted

# Diagnosing Azure Deployment Failures Lookup-first triage against documented gotchas. If the symptom doesn't match a known entry, escalate to Microsoft's [`azure-diagnostics`](https://github.com/microsoft/azure-skills) for live log/metric queries. ## How to use this skill 1. Get the failing symptom (error code, stack trace, observed behaviour) 2. Match against the table below 3. Apply the documented fix 4. If no match, see [references/gotchas.md](references/gotchas.md) for the full catalogue 5. If still no match, capture a new gotcha via [curating-azure-deployment-learnings](../curating-azure-deployment-learnings/SKILL.md) ## Quick symptom table | Symptom | Likely cause | Fix | |---------|-------------|-----| | `BCP258: sqlAdminPassword missing` | Using `.bicepparam` instead of `.parameters.json` | Keep params as `.parameters.json`; use `@` prefix | | `LocationNotAvailableForResourceType` for SWA | `australiaeast` not supported | Hard-code `swaLocation = 'eastasia'` | | `Multiple files found matching pattern *.sql` | `azure/sql-action` accepts only one file | Replace with `sqlcmd` bash loop | | `sqlcmd: command not found` (exit 127) | Not pre-installed on ubuntu-24.04 | Install `mssql-tools18` via Microsoft apt repo | | `gpg: cannot open /dev/tty` | `gpg --dearmor` without `--batch` in CI | Use `gpg --batch --yes --dearmor \| sudo tee` | | OIDC fails `AADSTS70021` | Federated credential subject mismatch | Must match `repo:owner/repo:ref:refs/heads/branch` exactly | | `A