Skip to content

Robertjam954/multimodal_rag_application / .claude/skills/azure-prepare

azure-prepare

Flagged

Prepare 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".

FileKindSize
SKILL.mdskill md13.1 KB
references/analyze.mdmarkdown4.3 KB
references/apim.mdmarkdown5.7 KB
references/architecture.mdmarkdown6.3 KB
references/aspire.mdmarkdown18.2 KB
references/auth-best-practices.mdmarkdown6.1 KB
references/azure-context.mdmarkdown5.7 KB
references/functional-verification.mdmarkdown3.2 KB
references/generate.mdmarkdown5.3 KB
references/global-rules.mdmarkdown2.0 KB
references/plan-template.mdmarkdown10.1 KB
references/recipe-selection.mdmarkdown3.2 KB
references/recipes/azcli/README.mdmarkdown1.8 KB
references/recipes/azcli/commands.mdmarkdown1.6 KB
references/recipes/azcli/scripts.mdmarkdown2.2 KB
references/recipes/azd/README.mdmarkdown3.8 KB
references/recipes/azd/aspire.mdmarkdown8.9 KB
references/recipes/azd/azure-yaml.mdmarkdown6.7 KB
references/recipes/azd/docker.mdmarkdown2.0 KB
references/recipes/azd/iac-rules.mdmarkdown5.8 KB
references/recipes/azd/terraform.mdmarkdown14.0 KB
references/recipes/bicep/README.mdmarkdown1.4 KB
references/recipes/bicep/patterns.mdmarkdown3.0 KB
references/recipes/terraform/README.mdmarkdown2.5 KB
references/recipes/terraform/patterns.mdmarkdown3.5 KB
references/region-availability.mdmarkdown1.7 KB
references/requirements.mdmarkdown2.5 KB
references/research.mdmarkdown8.8 KB
references/resources-limits-quotas.mdmarkdown13.0 KB
references/runtimes/nodejs.mdmarkdown5.9 KB
references/scan.mdmarkdown3.5 KB
references/sdk/azd-deployment.mdmarkdown792 B
references/sdk/azure-appconfiguration-java.mdmarkdown1.5 KB
references/sdk/azure-appconfiguration-py.mdmarkdown1.1 KB
references/sdk/azure-appconfiguration-ts.mdmarkdown1.2 KB
references/sdk/azure-identity-dotnet.mdmarkdown941 B
references/sdk/azure-identity-java.mdmarkdown1.2 KB
references/sdk/azure-identity-py.mdmarkdown1.1 KB
references/sdk/azure-identity-ts.mdmarkdown1.1 KB
references/security.mdmarkdown8.5 KB
references/services/aks/README.mdmarkdown1.0 KB
references/services/aks/addons.mdmarkdown957 B
references/services/aks/bicep.mdmarkdown1.6 KB
references/services/aks/manifests.mdmarkdown1.4 KB
references/services/app-insights/README.mdmarkdown848 B
references/services/app-service/README.mdmarkdown2.3 KB
references/services/app-service/bicep.mdmarkdown4.2 KB
references/services/app-service/custom-domains.mdmarkdown4.8 KB
references/services/app-service/deployment-slots.mdmarkdown4.5 KB
references/services/app-service/networking.mdmarkdown6.6 KB
references/services/app-service/scaling.mdmarkdown1.5 KB
references/services/app-service/sku-selection.mdmarkdown4.7 KB
references/services/app-service/templates/recipes/README.mdmarkdown2.8 KB
references/services/app-service/templates/recipes/auth/README.mdmarkdown3.1 KB
references/services/app-service/templates/recipes/auth/source/dotnet.mdmarkdown1.3 KB
references/services/app-service/templates/recipes/auth/source/nodejs.mdmarkdown2.5 KB
references/services/app-service/templates/recipes/auth/source/python.mdmarkdown2.2 KB
references/services/app-service/templates/recipes/composition.mdmarkdown4.8 KB
references/services/app-service/templates/recipes/cosmos/README.mdmarkdown3.6 KB
references/services/app-service/templates/recipes/cosmos/source/dotnet.mdmarkdown1.3 KB
references/services/app-service/templates/recipes/cosmos/source/nodejs.mdmarkdown1.2 KB
references/services/app-service/templates/recipes/cosmos/source/python.mdmarkdown1.1 KB
references/services/app-service/templates/recipes/redis/README.mdmarkdown3.3 KB
references/services/app-service/templates/recipes/redis/source/dotnet.mdmarkdown1.6 KB
references/services/app-service/templates/recipes/redis/source/nodejs.mdmarkdown2.2 KB
references/services/app-service/templates/recipes/redis/source/python.mdmarkdown2.9 KB
references/services/app-service/templates/recipes/sql/README.mdmarkdown3.5 KB
references/services/app-service/templates/recipes/sql/source/dotnet.mdmarkdown2.9 KB
references/services/app-service/templates/recipes/sql/source/nodejs.mdmarkdown3.0 KB
references/services/app-service/templates/recipes/sql/source/python.mdmarkdown4.4 KB
references/services/app-service/templates/selection.mdmarkdown2.8 KB
references/services/app-service/templates/web-api.mdmarkdown4.9 KB
references/services/app-service/templates/web-app.mdmarkdown4.9 KB
references/services/container-apps/README.mdmarkdown1.3 KB
references/services/container-apps/bicep.mdmarkdown4.8 KB
references/services/container-apps/day2-operations.mdmarkdown5.1 KB
references/services/container-apps/environment.mdmarkdown1.2 KB
references/services/container-apps/health-probes.mdmarkdown1.1 KB
references/services/container-apps/networking.mdmarkdown5.1 KB
references/services/container-apps/revisions.mdmarkdown4.9 KB
references/services/container-apps/scaling.mdmarkdown1.4 KB
references/services/container-apps/terraform.mdmarkdown6.1 KB
references/services/cosmos-db/README.mdmarkdown1.4 KB
references/services/cosmos-db/bicep.mdmarkdown1.8 KB
references/services/cosmos-db/partitioning.mdmarkdown1.1 KB
references/services/cosmos-db/sdk.mdmarkdown1.6 KB
references/services/durable-task-scheduler/README.mdmarkdown4.9 KB
references/services/durable-task-scheduler/bicep.mdmarkdown4.8 KB
references/services/durable-task-scheduler/dotnet.mdmarkdown6.1 KB
references/services/durable-task-scheduler/java.mdmarkdown7.7 KB
references/services/durable-task-scheduler/javascript.mdmarkdown5.6 KB
references/services/durable-task-scheduler/python.mdmarkdown6.4 KB
references/services/event-grid/README.mdmarkdown1.0 KB
references/services/event-grid/bicep.mdmarkdown1.7 KB
references/services/event-grid/subscriptions.mdmarkdown1.6 KB
references/services/foundry/README.mdmarkdown1.3 KB
references/services/foundry/region-availability.mdmarkdown826 B
references/services/functions/README.mdmarkdown3.8 KB
references/services/functions/aspire-containerapps.mdmarkdown3.3 KB
references/services/functions/bicep.mdmarkdown11.9 KB
references/services/functions/durable.mdmarkdown1.8 KB
references/services/functions/templates/README.mdmarkdown6.5 KB
references/services/functions/templates/base/eval/python.mdmarkdown762 B
references/services/functions/templates/base/eval/summary.mdmarkdown1.9 KB
references/services/functions/templates/base/eval/typescript.mdmarkdown1.1 KB
references/services/functions/templates/recipes/README.mdmarkdown1.1 KB
references/services/functions/templates/recipes/blob-eventgrid/README.mdmarkdown1.6 KB
references/services/functions/templates/recipes/blob-eventgrid/eval/python.mdmarkdown1.2 KB
references/services/functions/templates/recipes/blob-eventgrid/eval/summary.mdmarkdown2.6 KB
references/services/functions/templates/recipes/common/dotnet-entry-point.mdmarkdown2.0 KB
references/services/functions/templates/recipes/common/error-handling.mdmarkdown2.2 KB
references/services/functions/templates/recipes/common/health-check.mdmarkdown2.7 KB
references/services/functions/templates/recipes/common/nodejs-entry-point.mdmarkdown4.1 KB
references/services/functions/templates/recipes/composition.mdmarkdown11.1 KB
references/services/functions/templates/recipes/cosmosdb/README.mdmarkdown1.5 KB
references/services/functions/templates/recipes/cosmosdb/eval/python.mdmarkdown1.2 KB
references/services/functions/templates/recipes/cosmosdb/eval/summary.mdmarkdown1.8 KB
references/services/functions/templates/recipes/cosmosdb/eval/typescript.mdmarkdown1.3 KB
references/services/functions/templates/recipes/durable/README.mdmarkdown1.8 KB
references/services/functions/templates/recipes/durable/eval/python.mdmarkdown1.2 KB
references/services/functions/templates/recipes/durable/eval/summary.mdmarkdown1.6 KB
references/services/functions/templates/recipes/eventhubs/README.mdmarkdown1.2 KB
references/services/functions/templates/recipes/eventhubs/eval/python.mdmarkdown1.2 KB
references/services/functions/templates/recipes/eventhubs/eval/summary.mdmarkdown1.5 KB
references/services/functions/templates/recipes/mcp/README.mdmarkdown1.9 KB
references/services/functions/templates/recipes/mcp/eval/python.mdmarkdown1.2 KB
references/services/functions/templates/recipes/mcp/eval/summary.mdmarkdown1.5 KB
references/services/functions/templates/recipes/servicebus/README.mdmarkdown1.3 KB
references/services/functions/templates/recipes/servicebus/eval/python.mdmarkdown1.3 KB
references/services/functions/templates/recipes/servicebus/eval/summary.mdmarkdown1.8 KB
references/services/functions/templates/recipes/servicebus/eval/typescript.mdmarkdown1.4 KB
references/services/functions/templates/recipes/sql/README.mdmarkdown1.8 KB
references/services/functions/templates/recipes/sql/eval/python.mdmarkdown1.2 KB
references/services/functions/templates/recipes/sql/eval/summary.mdmarkdown2.8 KB
references/services/functions/templates/recipes/timer/README.mdmarkdown1.5 KB
references/services/functions/templates/recipes/timer/eval/python.mdmarkdown1.2 KB
references/services/functions/templates/recipes/timer/eval/summary.mdmarkdown1.5 KB
references/services/functions/templates/selection.mdmarkdown4.3 KB
references/services/functions/terraform.mdmarkdown13.3 KB
references/services/key-vault/README.mdmarkdown1.3 KB
references/services/key-vault/bicep.mdmarkdown1.7 KB
references/services/key-vault/sdk.mdmarkdown1.9 KB
references/services/logic-apps/README.mdmarkdown1.0 KB
references/services/logic-apps/bicep.mdmarkdown1.8 KB
references/services/logic-apps/triggers.mdmarkdown1.7 KB
references/services/service-bus/README.mdmarkdown1.4 KB
references/services/service-bus/bicep.mdmarkdown3.7 KB
references/services/service-bus/patterns.mdmarkdown4.2 KB
references/services/sql-database/README.mdmarkdown1.9 KB
references/services/sql-database/auth.mdmarkdown4.0 KB
references/services/sql-database/bicep.mdmarkdown7.8 KB
references/services/sql-database/scripts/grant-sql-access.ps1script3.5 KB
references/services/sql-database/scripts/grant-sql-access.shscript3.6 KB
references/services/sql-database/sdk.mdmarkdown1.8 KB
references/services/static-web-apps/README.mdmarkdown1.3 KB
references/services/static-web-apps/bicep.mdmarkdown1.0 KB
references/services/static-web-apps/deployment.mdmarkdown1.8 KB
references/services/static-web-apps/region-availability.mdmarkdown674 B
references/services/static-web-apps/routing.mdmarkdown1.2 KB
references/services/static-web-apps/terraform.mdmarkdown3.5 KB
references/services/storage/README.mdmarkdown1.4 KB
references/services/storage/access.mdmarkdown3.6 KB
references/services/storage/bicep.mdmarkdown1.7 KB
references/specialized-routing.mdmarkdown4.5 KB

references/resources-limits-quotas.md

View on GitHub
# Azure Resource Limits and Quotas

Check Azure resource availability during azure-prepare workflow. Validate after customer selects region.

## Types

1. **Hard Limits** - Fixed constraints that cannot be changed
2. **Quotas** - Subscription limits that can be increased via support request

**CLI First:** Always use `az quota` CLI for quota checks. Provides better error handling and consistent output. "No Limit" in REST/Portal doesn't mean unlimited - verify with service docs.

## Hard Limits

Fixed service constraints (cannot be changed).

**Check via**: `azure__documentation` tool or azure-provisioning-limit skill

**Examples**: Cosmos DB item size (2 MB), Container Apps HTTP timeout (240s), App Service Free tier deployment slots (0)

**Process**:
1. Identify services and resource sizes needed
2. Look up limits in documentation
3. Compare plan vs limits
4. If exceeded: redesign or change tier

## Quotas

Subscription/regional limits that can be increased via support request.

**Check via**: `az quota` CLI (install: `az extension add --name quota`)

**Examples**: AKS clusters (5,000/region), Storage accounts (250/region), Container Apps environments (50/region)

**Key Concept**: No 1:1 mapping between ARM resource types and quota names.
- ARM: `Microsoft.App/managedEnvironments` → Quota: `ManagedEnvironmentCount`
- ARM: `Microsoft.Compute/virtualMachines` → Quota: `standardDSv3Family`, `cores`, `virtualMachines`

**Process**:
1. Install extension: `az extension add --name quota`
2. Discover quota names: `az quota list --scope /subscriptions/{id}/providers/{Provider}/locations/{region}`
3. Check usage: `az quota usage show --resource-name {name} --scope ...`
4. Check limit: `az quota show --resource-name {name} --scope ...`
5. Calculate: Available = Limit - Current Usage
6. If exceeded: Request increase via `az quota update`

**Unsupported Providers** (BadRequest error):

Not all providers support quota API. If `az quota list` fails with BadRequest, use fallback:

1. Get current usage:
   ```bash
   # Option A: Azure Resource Graph (recommended)
   az extension add --name resource-graph
   az graph query -q "resources | where type == '{type}' and location == '{loc}' | count"
   
   # Option B: Resource list
   az resource list --subscription "{id}" --resource-type "{Type}" --location "{loc}" | jq 'length'
   ```
2. Get limit from [service documentation](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits)
3. Calculate: Available = Documented Limit - Current Usage

**Known Support Status**:
- ❌ Microsoft.DocumentDB (Cosmos DB)
- ✅ Microsoft.Compute, Microsoft.Network, Microsoft.App, Microsoft.Storage, Microsoft.MachineLearningServices

## Workflow

**Phase 1: Identify & Check Hard Limits**
1. Analyze app requirements and select Azure services
2. Determine resource counts, sizes, tiers, throughput
3. Check hard limits via azure-provisioning-limit skill or documentation
4. Validate plan against limits; redesign if needed

**Phase 2: Check Quotas After Region Selection**
1. Get customer subscription and region preference
2. For each service/region, check quota:
   - Use `az quota usage list` and `az quota show`
   - Calculate available capacity
3. If quota exceeded: request increase or choose different region

**Phase 3: Validate Region**
- Confirm sufficient quota in selected region
- Request increases if needed
- Only proceed after validation complete

## Limit Scopes

| Scope | Example |
|-------|---------|
| Subscription | 50 Cosmos DB accounts (any region) |
| Regional | 250 storage accounts per region |
| Resource | 500 apps per Container Apps environment |

## Service Patterns

| Service | Hard Limits (examples) | Quota Check | Notes |
|---------|------------------------|-------------|-------|
| **Cosmos DB** | Item: 2MB, Partition key: 2KB, Serverless storage: 50GB | ❌ Not supported. Use Resource Graph + [docs](https://learn.microsoft.com/en-us/azure/cosmos-db/concepts-limits). Default: 50 accounts/region | Query: `az graph query -q "resources \| where type == 'microsoft.documentdb/databaseaccounts' and location == 'eastus' \| count"` |
| **AKS** | Pods/node (Azure CNI): 250, Node pools/cluster: 100 | ✅ `az quota` supported | Provider: Microsoft.ContainerService |
| **Storage** | Block blob: 190.7 TiB, Page blob: 8 TiB | ✅ Quota: `StorageAccounts` (limit: 250/region) | Provider: Microsoft.Storage |
| **Container Apps** | Revisions/app: 100, HTTP timeout: 240s | ✅ Quota: `ManagedEnvironmentCount` (limit: 50/region) | Provider: Microsoft.App |
| **Functions** | Timeout (Consumption): 10 min, Queue msg: 64KB | ✅ Check function apps quota | Provider: Microsoft.Web |

## CLI Reference

**Prerequisites**: `az extension add --name quota`

**Discovery**: List quotas to find resource names
```bash
az quota list --scope /subscriptions/{id}/providers/{provider}/locations/{location}
```

**Check Usage**:
```bash
az quota usage show --resource-name {quota-name} --scope /subscriptions/{id}/providers/{provider}/locations/{location}
```

**Check Limit**:
```bash
az quota show --resource-name {quota-name} --scope /subscriptions/{id}/providers/{provider}/locations/{location}
```

**Request Increase**:
```bash
az quota update --resource-name {quota-name} --scope /subscriptions/{id}/providers/{provider}/locations/{location} --limit-object value={new-limit} --resource-type {type}
```

## azure-prepare Integration

**When to Check**:
1. After selecting services - Check hard limits
2. After customer selects region - Check quotas
3. Before generating infrastructure code - Validate availability

**Required Steps**:

**Phase 1 - Planning**:
- Select Azure services
- Check hard limits (service documentation)
- Create provisioning limit checklist (leave quota columns as "_TBD_")

**Phase 2 - Execution**:
- Get subscription and region preference
- **Must invoke azure-quotas skill** - Process ONE resource type at a time:
  a. Try `az quota list` first (required)
  b. If supported: Use `az quota usage show` and `az quota show`
  c. If NOT supported (BadRequest): Use Resource Graph + service docs
  d. Calculate available capacity
  e. Document in checklist (no "_TBD_" entries allowed)
  f. If insufficient: Request increase or change region

**Phase 3 - Generate Artifacts**:
- Only proceed after Phase 2 complete (all quotas validated)

## Error Messages

| Error | Type | Action |
|-------|------|--------|
| "Quota exceeded" | Quota | Use azure-quotas to request increase |
| "(BadRequest) Bad request" | Unsupported provider | Use [service limits docs](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits) |
| "Limit exceeded" | Hard Limit | Redesign or change tier |
| "Maximum size exceeded" | Hard Limit | Split data or use alternative storage |
| "Too many requests" | Rate Limit | Implement retry logic or increase tier |
| "Cannot exceed X" | Hard Limit | Stay within limit or use multiple resources |
| "Subscription limit reached" | Quota | Request quota increase using azure-quotas skill |
| "Regional capacity" | Quota | Choose different region or request increase |

## Best Practices

1. **MUST use Azure CLI quota API first**: `az quota` commands are MANDATORY as the primary method for checking quotas - only use fallback methods (REST API, Portal, docs) when quota API returns `BadRequest`
2. **Don't trust "No Limit" values**: If REST API or Portal shows "No Limit" or unlimited, verify with official service documentation - it likely means the quota API doesn't support that resource type, not that capacity is unlimited
3. **Always check after customer selects region**: Validates availability and allows time for quota requests
4. **Use the discovery workflow**: Never assume quota resource names - always run `az quota list` first to discover correct names
5. **Check both usage and limit**: Run `az quota usage show` AND `az quota show` to calculate available capacity
6. **Handle unsupported providers gracefully**: If you get `BadRequest` error, fall back to official documentation (Azure Resource Graph + docs)
7. **Request quota increases proactively**: If selected region lacks capacity, submit request before deployment
8. **Have alternative regions ready**: If quota increase denied, suggest backup regions
9. **Document capacity assumptions**: Note quota availability and source in `.azure/deployment-plan.md`
10. **Design for limits**: Architecture should account for both hard limits and quotas
11. **Monitor usage trends**: Regular quota checks help predict future needs
12. **Use lower environments wisely**: Dev/test environments count against quotas

## Quick Reference Limits

For complete quota checking workflow and commands, invoke the **azure-quotas** skill.

> **Note:** These are typical default limits. Always verify actual quotas using `az quota show` for your specific subscription and region.

Common quotas to check:

### Subscription Level
- Cosmos DB accounts: 50 per region (check via docs - quota API not supported)
- SQL logical servers: 250 per region
- Service Bus namespaces: 100-1,000 (tier dependent)

### Regional Level  
- Storage accounts: 250 per region (quota resource name: `StorageAccounts`)
- AKS clusters: 5,000 per region (quota resource name: varies by configuration)
- Container Apps environments: 50 per region (quota resource name: `ManagedEnvironmentCount`)
- Function apps: 200 per region (Consumption)

### Resource Level
- Cosmos DB containers per account: Unlimited (subject to storage)
- Apps per Container Apps environment: 500
- Databases per SQL server: 500
- Queues/topics per Service Bus namespace: 10,000

## Related Documentation

- **azure-quotas skill** - Complete quota checking workflow and CLI commands (invoke the **azure-quotas** skill)
- [Azure subscription limits](https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits) - Official Microsoft documentation
- [Azure Quotas Overview](https://learn.microsoft.com/en-us/azure/quotas/quotas-overview) - Understanding quotas and limits
- [azure-context.md](azure-context.md) - How to confirm subscription and region
- [architecture.md](architecture.md) - Architecture planning workflow

## Example: Complete Check Workflow

```bash
# Scenario: Deploying app with Cosmos DB, Storage, and Container Apps
# Customer selected region: East US

# 1. Check Hard Limits (from azure-provisioning-limit skill)
# Cosmos DB: Item size max 2 MB ✓
# Storage: Blob size max 190.7 TiB ✓
# Container Apps: Timeout 240 sec ✓

# 2. Get Customer's Region Preference
# Customer: "I prefer East US"

# 3. Check Quotas for Customer's Selected Region (East US)

# 3a. Cosmos DB - NOT SUPPORTED by quota API
az quota list \
  --scope /subscriptions/abc-123/providers/Microsoft.DocumentDB/locations/eastus
# Error: (BadRequest) Bad request

# Fallback: Get current usage with Azure Resource Graph
# Install extension first (if needed)
az extension add --name resource-graph

az graph query -q "resources | where type == 'microsoft.documentdb/databaseaccounts' and location == 'eastus' | count"
# Result: 3 database accounts currently deployed

# Or use Azure CLI resource list
az resource list \
  --subscription "abc-123" \
  --resource-type "Microsoft.DocumentDB/databaseAccounts" \
  --location "eastus" | jq 'length'
# Result: 3

# Get limit from documentation: 50 database accounts per region
# Calculate: Available = 50 - 3 = 47 ✓
# Document as: "Fetched from: Azure Resource Graph + Official docs"

# 3b. Storage Accounts
# Step 1: Discover resource name
az quota list \
  --scope /subscriptions/abc-123/providers/Microsoft.Storage/locations/eastus

# Step 2: Check usage (use discovered name "StorageAccounts")
az quota usage show \
  --resource-name StorageAccounts \
  --scope /subscriptions/abc-123/providers/Microsoft.Storage/locations/eastus
# Current: 180

# Step 3: Check limit
az quota show \
  --resource-name StorageAccounts \
  --scope /subscriptions/abc-123/providers/Microsoft.Storage/locations/eastus
# Limit: 250
# Available: 250 - 180 = 70 ✓

# 3c. Container Apps
# Step 1: Discover resource name
az quota list \
  --scope /subscriptions/abc-123/providers/Microsoft.App/locations/eastus
# Shows: "ManagedEnvironmentCount"

# Step 2: Check usage
az quota usage show \
  --resource-name ManagedEnvironmentCount \
  --scope /subscriptions/abc-123/providers/Microsoft.App/locations/eastus
# Current: 8

# Step 3: Check limit
az quota show \
  --resource-name ManagedEnvironmentCount \
  --scope /subscriptions/abc-123/providers/Microsoft.App/locations/eastus
# Limit: 50
# Available: 50 - 8 = 42 ✓

# 4. Validate Availability
# ✅ All services have sufficient quota in East US
# ✅ Proceed with deployment

# Alternative: If quotas were insufficient
# ❌ Container Apps: 49/50 (only 1 available, need 3)
# Action: Request quota increase
# 
# az quota update \
#   --resource-name ManagedEnvironmentCount \
#   --scope /subscriptions/abc-123/providers/Microsoft.App/locations/eastus \
#   --limit-object value=100 \
#   --resource-type Microsoft.App/managedEnvironments
```

---

> **Remember**: Checking limits and quotas early prevents deployment failures and ensures smooth infrastructure provisioning.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall