Robertjam954/multimodal_rag_application / .claude/skills/azure-prepare
azure-prepare
FlaggedPrepare Azure apps for deployment (infra Bicep/Terraform, azure.yaml, Dockerfiles). Use for create/modernize or create+deploy; not cross-cloud migration (use azure-cloud-migrate). DO NOT USE FOR: copilot-sdk apps (use azure-hosted-copilot-sdk), or Python code-only App Service deploys (use python-appservice-deploy). WHEN: "create app", "build web app", "create API", "modernize application", "host on Azure", "deploy to Azure", "deploy to Azure using Terraform", "deploy to Azure App Service", "deploy to Azure App Service using Terraform", "deploy to Azure Container Apps", "generate Terraform", "generate Bicep", "function app", "timer trigger", "service bus trigger", "event-driven function", "managed identity".
references/azure-context.md
View on GitHub# Azure Context (Subscription & Location)
Detect and confirm Azure subscription and location before generating artifacts. Run region capacity check for customer selected location
---
## Step 1: Check for Existing AZD Environment
If the project already uses AZD, check for an existing environment with values already set:
```bash
azd env list
```
**If an environment is selected** (marked with `*`), check its values:
```bash
azd env get-values
```
If `AZURE_SUBSCRIPTION_ID` and `AZURE_LOCATION` are already set, use `ask_user` to confirm reuse:
```
Question: "I found an existing AZD environment with these settings. Would you like to continue with them?"
Environment: {env-name}
Subscription: {subscription-name} ({subscription-id})
Location: {location}
Choices: [
"Yes, use these settings (Recommended)",
"No, let me choose different settings"
]
```
If user confirms → skip to **Record in Plan**. Otherwise → continue to Step 2.
---
## Step 2: Detect Defaults
Check for user-configured defaults:
```bash
azd config get defaults
```
Returns JSON with any configured defaults:
```json
{
"subscription": "25fd0362-aa79-488b-b37b-d6e892009fdf",
"location": "eastus2"
}
```
Use these as **recommended** values if present.
If no defaults, fall back to az CLI:
```bash
az account show --query "{name:name, id:id}" -o json
```
## Step 3: Confirm Subscription with User
Use `ask_user` with the **actual subscription name and ID**:
✅ **Correct:**
```
Question: "Which Azure subscription would you like to deploy to?"
Choices: [
"Use current: jongdevdiv (25fd0362-aa79-488b-b37b-d6e892009fdf) (Recommended)",
"Let me specify a different subscription"
]
```
❌ **Wrong** (never do this):
```
Choices: [
"Use default subscription", // ← Does not show actual name
"Let me specify"
]
```
If user wants a different subscription:
```bash
az account list --output table
```
---
## Step 4: Confirm Location with User
1. Consult [Region Availability](region-availability.md) for services with limited availability
2. Present only regions that support ALL selected services
3. Use `ask_user`:
4. After customer selected region, do provisioning limit check, consult [Resource Limits and Quotas](resources-limits-quotas.md). For this also invoke azure-quotas
```
Question: "Which Azure region would you like to deploy to?"
Based on your architecture ({list services}), these regions support all services:
Choices: [
"eastus2 (Recommended)",
"westus2",
"westeurope"
]
```
⚠️ Do NOT include regions that don't support all services — deployment will fail.
---
## Step 5: Check Resource Provisioning Limits
1. **List resource types and quantities** that will be deployed from the planned architecture (e.g., 2x Standard D4s v3 VMs, 1x VNet, 3x Storage Accounts)
2. **Determine limits for each resource type** using the user-selected subscription and region:
- Reference [./resources-limits-quotas.md](./resources-limits-quotas.md) for documented limits
- Use **azure-quotas** skill to check current quotas and usage for the selected subscription and region
- If `az quota list` returns `BadRequest` error, the resource provider doesn't support quota API
3. **For resources that don't support quota API** (e.g., Microsoft.DocumentDB, or when you get `BadRequest` from `az quota list`):
- Invoke **azure-resource-lookup** skill to count existing deployments of that resource type in the selected subscription and region
- Use the count to calculate: `Total After Deployment = Current Count + Planned Deployment`
- Reference [Azure service limits documentation](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits) for the limit value
- Document in provisioning checklist as "Fetched from: azure-resource-lookup + Official docs"
4. **Validate deployment capacity**:
- Compare planned deployment quantities against available quota (limit - current usage)
- If **insufficient capacity** is found, notify the customer and return to **Step 4** to select a different region
- Use **azure-quotas** skill to compare capacity across multiple regions and recommend alternatives
## Record in Plan
After confirmation, record in `.azure/deployment-plan.md`:
```markdown
## Azure Context
- **Subscription**: jongdevdiv (25fd0362-aa79-488b-b37b-d6e892009fdf)
- **Location**: eastus2
```
---
## Step 6: Apply to AZD Environment
> **⛔ CRITICAL for Aspire and azd projects**: After user confirms subscription and location, you **MUST** set these values in the azd environment immediately after running `azd init` or `azd env new`. Always use `--no-prompt` with these commands to prevent interactive prompts from blocking execution.
>
> **DO NOT** wait until validation or deployment. The Azure CLI and azd maintain separate configuration contexts.
**For Aspire projects using `azd init --from-code`:**
```bash
# 1. Run azd init
azd init --from-code -e <environment-name> --no-prompt
# 2. IMMEDIATELY set the user-confirmed subscription
azd env set AZURE_SUBSCRIPTION_ID <subscription-id>
# 3. Set the location
azd env set AZURE_LOCATION <location>
# 4. Verify
azd env get-values
```
**For non-Aspire projects using `azd env new`:**
```bash
# 1. Create environment
azd env new <environment-name> --no-prompt
# 2. IMMEDIATELY set the user-confirmed subscription
azd env set AZURE_SUBSCRIPTION_ID <subscription-id>
# 3. Set the location
azd env set AZURE_LOCATION <location>
# 4. Verify
azd env get-values
```
**Why this is critical:**
- `az account show` returns the Azure CLI's default subscription
- `azd` maintains its own configuration with potentially different defaults
- If you don't set `AZURE_SUBSCRIPTION_ID` explicitly, azd will use its own default
- This can result in deploying to the wrong subscription despite user confirmation
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |