[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KAYQZTHT59BCBDNX98FNW5":3,"skill-same:01M6KAYQZTHT59BCBDNX98FNW5":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6KAYQZTHT59BCBDNX98FNW5","azure-cloud-architect",null,"Design Azure architectures for startups and enterprises. Use when asked to design Azure infrastructure, create Bicep\u002FARM templates, optimize Azure costs, set up Azure DevOps pipelines, or migrate to Azure. Covers AKS, App Service, Azure Functions, Cosmos DB, and cost optimization.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fazure-cloud-architect\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"azure","cloud","cloud architect","architect","azure cloud architect","migrate","for","arm templates","architectures","app","db","startups","optimize","up","design","SET","aks","create","infrastructure","azure devops","2026-11-10 10:12:30",false,"---\nname: \"azure-cloud-architect\"\ndescription: \"Design Azure architectures for startups and enterprises. Use when asked to design Azure infrastructure, create Bicep\u002FARM templates, optimize Azure costs, set up Azure DevOps pipelines, or migrate to Azure. Covers AKS, App Service, Azure Functions, Cosmos DB, and cost optimization.\"\n---\n\n# Azure Cloud Architect\n\nDesign scalable, cost-effective Azure architectures for startups and enterprises with Bicep infrastructure-as-code templates.\n\n---\n\n## Workflow\n\n### Step 1: Gather Requirements\n\nCollect application specifications:\n\n```\n- Application type (web app, mobile backend, data pipeline, SaaS, microservices)\n- Expected users and requests per second\n- Budget constraints (monthly spend limit)\n- Team size and Azure experience level\n- Compliance requirements (GDPR, HIPAA, SOC 2, ISO 27001)\n- Availability requirements (SLA, RPO\u002FRTO)\n- Region preferences (data residency, latency)\n```\n\n### Step 2: Design Architecture\n\nRun the architecture designer to get pattern recommendations:\n\n```bash\npython scripts\u002Farchitecture_designer.py \\\n  --app-type web_app \\\n  --users 10000 \\\n  --requirements '{\"budget_monthly_usd\": 500, \"compliance\": [\"SOC2\"]}'\n```\n\n**Example output:**\n\n```json\n{\n  \"recommended_pattern\": \"app_service_web\",\n  \"service_stack\": [\"App Service\", \"Azure SQL\", \"Front Door\", \"Key Vault\", \"Entra ID\"],\n  \"estimated_monthly_cost_usd\": 280,\n  \"pros\": [\"Managed platform\", \"Built-in autoscale\", \"Deployment slots\"],\n  \"cons\": [\"Less control than VMs\", \"Platform constraints\", \"Cold start on consumption plans\"]\n}\n```\n\nSelect from recommended patterns:\n- **App Service Web**: Front Door + App Service + Azure SQL + Redis Cache\n- **Microservices on AKS**: AKS + Service Bus + Cosmos DB + API Management\n- **Serverless Event-Driven**: Functions + Event Grid + Service Bus + Cosmos DB\n- **Data Pipeline**: Data Factory + Synapse Analytics + Data Lake Storage + Event Hubs\n\nSee `references\u002Farchitecture_patterns.md` for detailed pattern specifications.\n\n**Validation checkpoint:** Confirm the recommended pattern matches the team's operational maturity and compliance requirements before proceeding to Step 3.\n\n### Step 3: Generate IaC Templates\n\nCreate infrastructure-as-code for the selected pattern:\n\n```bash\n# Web app stack (Bicep)\npython scripts\u002Fbicep_generator.py --arch-type web-app --output main.bicep\n```\n\n**Example Bicep output (core web app resources):**\n\n```bicep\n@description('The environment name')\nparam environment string = 'dev'\n\n@description('The Azure region for resources')\nparam location string = resourceGroup().location\n\n@description('The application name')\nparam appName string = 'myapp'\n\n\u002F\u002F App Service Plan\nresource appServicePlan 'Microsoft.Web\u002Fserverfarms@2023-01-01' = {\n  name: '${environment}-${appName}-plan'\n  location: location\n  sku: {\n    name: 'P1v3'\n    tier: 'PremiumV3'\n    capacity: 1\n  }\n  properties: {\n    reserved: true \u002F\u002F Linux\n  }\n}\n\n\u002F\u002F App Service\nresource appService 'Microsoft.Web\u002Fsites@2023-01-01' = {\n  name: '${environment}-${appName}-web'\n  location: location\n  properties: {\n    serverFarmId: appServicePlan.id\n    httpsOnly: true\n    siteConfig: {\n      linuxFxVersion: 'NODE|20-lts'\n      minTlsVersion: '1.2'\n      ftpsState: 'Disabled'\n      alwaysOn: true\n    }\n  }\n  identity: {\n    type: 'SystemAssigned'\n  }\n}\n\n\u002F\u002F Azure SQL Database\nresource sqlServer 'Microsoft.Sql\u002Fservers@2023-05-01-preview' = {\n  name: '${environment}-${appName}-sql'\n  location: location\n  properties: {\n    administrators: {\n      azureADOnlyAuthentication: true\n    }\n    minimalTlsVersion: '1.2'\n  }\n}\n\nresource sqlDatabase 'Microsoft.Sql\u002Fservers\u002Fdatabases@2023-05-01-preview' = {\n  parent: sqlServer\n  name: '${appName}-db'\n  location: location\n  sku: {\n    name: 'GP_S_Gen5_2'\n    tier: 'GeneralPurpose'\n  }\n  properties: {\n    autoPauseDelay: 60\n    minCapacity: json('0.5')\n  }\n}\n```\n\n> Full templates including Front Door, Key Vault, Managed Identity, and monitoring are generated by `bicep_generator.py` and also available in `references\u002Farchitecture_patterns.md`.\n\n**Bicep is the recommended IaC language for Azure.** Prefer Bicep over ARM JSON templates: Bicep compiles to ARM JSON, has cleaner syntax, supports modules, and is first-party supported by Microsoft.\n\n### Step 4: Review Costs\n\nAnalyze estimated costs and optimization opportunities:\n\n```bash\npython scripts\u002Fcost_optimizer.py \\\n  --config current_resources.json \\\n  --json\n```\n\n**Example output:**\n\n```json\n{\n  \"current_monthly_usd\": 2000,\n  \"recommendations\": [\n    { \"action\": \"Right-size SQL Database GP_S_Gen5_8 to GP_S_Gen5_2\", \"savings_usd\": 380, \"priority\": \"high\" },\n    { \"action\": \"Purchase 1-year Reserved Instances for AKS node pools\", \"savings_usd\": 290, \"priority\": \"high\" },\n    { \"action\": \"Move Blob Storage to Cool tier for objects >30 days old\", \"savings_usd\": 65, \"priority\": \"medium\" }\n  ],\n  \"total_potential_savings_usd\": 735\n}\n```\n\nOutput includes:\n- Monthly cost breakdown by service\n- Right-sizing recommendations\n- Reserved Instance and Savings Plan opportunities\n- Potential monthly savings\n\n### Step 5: Configure CI\u002FCD\n\nSet up Azure DevOps Pipelines or GitHub Actions with Azure:\n\n```yaml\n# GitHub Actions — deploy Bicep to Azure\nname: Deploy Infrastructure\non:\n  push:\n    branches: [main]\n\npermissions:\n  id-token: write\n  contents: read\n\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - uses: azure\u002Flogin@v2\n        with:\n          client-id: ${{ secrets.AZURE_CLIENT_ID }}\n          tenant-id: ${{ secrets.AZURE_TENANT_ID }}\n          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}\n\n      - uses: azure\u002Farm-deploy@v2\n        with:\n          resourceGroupName: rg-myapp-dev\n          template: .\u002Finfra\u002Fmain.bicep\n          parameters: environment=dev\n```\n\n```yaml\n# Azure DevOps Pipeline\ntrigger:\n  branches:\n    include:\n      - main\n\npool:\n  vmImage: 'ubuntu-latest'\n\nsteps:\n  - task: AzureCLI@2\n    inputs:\n      azureSubscription: 'MyServiceConnection'\n      scriptType: 'bash'\n      scriptLocation: 'inlineScript'\n      inlineScript: |\n        az deployment group create \\\n          --resource-group rg-myapp-dev \\\n          --template-file infra\u002Fmain.bicep \\\n          --parameters environment=dev\n```\n\n### Step 6: Security Review\n\nValidate security posture before production:\n\n- **Identity**: Entra ID (Azure AD) with RBAC, Managed Identity for service-to-service auth — never store credentials in code\n- **Secrets**: Key Vault for all secrets, certificates, and connection strings\n- **Network**: NSGs on all subnets, Private Endpoints for PaaS services, Application Gateway with WAF\n- **Encryption**: TLS 1.2+ in transit, Azure-managed or customer-managed keys at rest\n- **Monitoring**: Microsoft Defender for Cloud enabled, Azure Policy for guardrails\n- **Compliance**: Azure Policy assignments for SOC 2 \u002F HIPAA \u002F ISO 27001 initiatives\n\n**If deployment fails:**\n\n1. Check the deployment status:\n   ```bash\n   az deployment group show \\\n     --resource-group rg-myapp-dev \\\n     --name main \\\n     --query 'properties.error'\n   ```\n2. Review Activity Log for RBAC or policy errors.\n3. Validate the Bicep template before deploying:\n   ```bash\n   az bicep build --file main.bicep\n   az deployment group validate \\\n     --resource-group rg-myapp-dev \\\n     --template-file main.bicep\n   ```\n\n**Common failure causes:**\n- RBAC permission errors — verify the deploying principal has Contributor on the resource group\n- Resource provider not registered — run `az provider register --namespace Microsoft.Web`\n- Naming conflicts — Azure resource names are often globally unique (storage accounts, web apps)\n- Quota exceeded — request quota increase via Azure Portal > Subscriptions > Usage + quotas\n\n---\n\n## Tools\n\n### architecture_designer.py\n\nGenerates architecture pattern recommendations based on requirements.\n\n```bash\npython scripts\u002Farchitecture_designer.py \\\n  --app-type web_app \\\n  --users 50000 \\\n  --requirements '{\"budget_monthly_usd\": 1000, \"compliance\": [\"HIPAA\"]}' \\\n  --json\n```\n\n**Input:** Application type, expected users, JSON requirements\n**Output:** Recommended pattern, service stack, cost estimate, pros\u002Fcons\n\n### cost_optimizer.py\n\nAnalyzes Azure resource configurations for cost savings.\n\n```bash\npython scripts\u002Fcost_optimizer.py --config resources.json --json\n```\n\n**Input:** JSON file with current Azure resource inventory\n**Output:** Recommendations for:\n- Idle resource removal\n- VM and database right-sizing\n- Reserved Instance purchases\n- Storage tier transitions\n- Unused public IPs and load balancers\n\n### bicep_generator.py\n\nGenerates Bicep template scaffolds from architecture type.\n\n```bash\npython scripts\u002Fbicep_generator.py --arch-type microservices --output main.bicep\n```\n\n**Output:** Production-ready Bicep templates with:\n- Managed Identity (no passwords)\n- Key Vault integration\n- Diagnostic settings for Azure Monitor\n- Network security groups\n- Tags for cost allocation\n\n---\n\n## Quick Start\n\n### Web App Architecture (\u003C $100\u002Fmonth)\n\n```\nAsk: \"Design an Azure web app for a startup with 5000 users\"\n\nResult:\n- App Service (B1 Linux) for the application\n- Azure SQL Serverless for relational data\n- Azure Blob Storage for static assets\n- Front Door (free tier) for CDN and routing\n- Key Vault for secrets\n- Estimated: $40-80\u002Fmonth\n```\n\n### Microservices on AKS ($500-2000\u002Fmonth)\n\n```\nAsk: \"Design a microservices architecture on Azure for a SaaS platform with 50k users\"\n\nResult:\n- AKS cluster with 3 node pools (system, app, jobs)\n- API Management for gateway and rate limiting\n- Cosmos DB for multi-model data\n- Service Bus for async messaging\n- Azure Monitor + Application Insights for observability\n- Multi-zone deployment\n```\n\n### Serverless Event-Driven (\u003C $200\u002Fmonth)\n\n```\nAsk: \"Design an event-driven backend for processing orders\"\n\nResult:\n- Azure Functions (Consumption plan) for compute\n- Event Grid for event routing\n- Service Bus for reliable messaging\n- Cosmos DB for order data\n- Application Insights for monitoring\n- Estimated: $30-150\u002Fmonth depending on volume\n```\n\n### Data Pipeline ($300-1500\u002Fmonth)\n\n```\nAsk: \"Design a data pipeline for ingesting 10M events\u002Fday\"\n\nResult:\n- Event Hubs for ingestion\n- Stream Analytics or Functions for processing\n- Data Lake Storage Gen2 for raw data\n- Synapse Analytics for warehouse\n- Power BI for dashboards\n```\n\n---\n\n## Input Requirements\n\nProvide these details for architecture design:\n\n| Requirement | Description | Example |\n|-------------|-------------|---------|\n| Application type | What you're building | SaaS platform, mobile backend |\n| Expected scale | Users, requests\u002Fsec | 10k users, 100 RPS |\n| Budget | Monthly Azure limit | $500\u002Fmonth max |\n| Team context | Size, Azure experience | 3 devs, intermediate |\n| Compliance | Regulatory needs | HIPAA, GDPR, SOC 2 |\n| Availability | Uptime requirements | 99.9% SLA, 1hr RPO |\n\n**JSON Format:**\n\n```json\n{\n  \"application_type\": \"saas_platform\",\n  \"expected_users\": 10000,\n  \"requests_per_second\": 100,\n  \"budget_monthly_usd\": 500,\n  \"team_size\": 3,\n  \"azure_experience\": \"intermediate\",\n  \"compliance\": [\"SOC2\"],\n  \"availability_sla\": \"99.9%\"\n}\n```\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It Fails | Do This Instead |\n|---|---|---|\n| ARM JSON templates for new projects | Verbose, hard to read, no modules | Use Bicep — compiles to ARM, cleaner syntax |\n| Storing secrets in App Settings | Secrets visible in portal, no rotation | Use Key Vault references in App Settings |\n| Single large AKS node pool | Cannot optimize for different workloads | Use multiple node pools: system, app, jobs |\n| Public endpoints on PaaS services | Exposed attack surface | Use Private Endpoints + VNet integration |\n| Over-provisioning \"just in case\" | Wastes budget month one | Start small, use autoscale, right-size monthly |\n| Shared resource groups for everything | Blast radius, RBAC nightmares | One resource group per environment per workload |\n| No tagging strategy | Cannot track costs or ownership | Tag: environment, owner, cost-center, app-name |\n| Using classic resources | Deprecated, limited features | Use ARM\u002FBicep resources exclusively |\n\n---\n\n## Output Formats\n\n### Architecture Design\n\n- Pattern recommendation with rationale\n- Service stack diagram (ASCII)\n- Monthly cost estimate and trade-offs\n\n### IaC Templates\n\n- **Bicep**: Recommended — first-party, module support, clean syntax\n- **ARM JSON**: Generated from Bicep when needed\n- **Terraform HCL**: Multi-cloud compatible using azurerm provider\n\n### Cost Analysis\n\n- Current spend breakdown with optimization recommendations\n- Priority action list (high\u002Fmedium\u002Flow) and implementation checklist\n\n---\n\n## Cross-References\n\n| Skill | Relationship |\n|-------|-------------|\n| `engineering-team\u002Faws-solution-architect` | AWS equivalent — same 6-step workflow, different services |\n| `engineering-team\u002Fgcp-cloud-architect` | GCP equivalent — completes the cloud trifecta |\n| `engineering-team\u002Fsenior-devops` | Broader DevOps scope — pipelines, monitoring, containerization |\n| `engineering\u002Fterraform-patterns` | IaC implementation — use for Terraform modules targeting Azure |\n| `engineering\u002Fci-cd-pipeline-builder` | Pipeline construction — automates Azure DevOps and GitHub Actions |\n\n---\n\n## Reference Documentation\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Farchitecture_patterns.md` | 5 patterns: web app, microservices\u002FAKS, serverless, data pipeline, multi-region |\n| `references\u002Fservice_selection.md` | Decision matrices for compute, database, storage, messaging, networking |\n| `references\u002Fbest_practices.md` | Naming conventions, tagging, RBAC, network security, monitoring, DR |\n","# Azure Cloud Architect\n\nDesign scalable, cost-effective Azure architectures for startups and enterprises with Bicep infrastructure-as-code templates.\n\n---\n\n## Workflow\n\n### Step 1: Gather Requirements\n\nCollect application specifications:\n\n```\n- Application type (web app, mobile backend, data pipeline, SaaS, microservices)\n- Expected users and requests per second\n- Budget constraints (monthly spend limit)\n- Team size and Azure experience level\n- Compliance requirements (GDPR, HIPAA, SOC 2, ISO 27001)\n- Availability requirements (SLA, RPO\u002FRTO)\n- Region preferences (data residency, latency)\n```\n\n### Step 2: Design Architecture\n\nRun the architecture designer to get pattern recommendations:\n\n```bash\npython scripts\u002Farchitecture_designer.py \\\n  --app-type web_app \\\n  --users 10000 \\\n  --requirements '{\"budget_monthly_usd\": 500, \"compliance\": [\"SOC2\"]}'\n```\n\n**Example output:**\n\n```json\n{\n  \"recommended_pattern\": \"app_service_web\",\n  \"service_stack\": [\"App Service\", \"Azure SQL\", \"Front Door\", \"Key Vault\", \"Entra ID\"],\n  \"estimated_monthly_cost_usd\": 280,\n  \"pros\": [\"Managed platform\", \"Built-in autoscale\", \"Deployment slots\"],\n  \"cons\": [\"Less control than VMs\", \"Platform constraints\", \"Cold start on consumption plans\"]\n}\n```\n\nSelect from recommended patterns:\n- **App Service Web**: Front Door + App Service + Azure SQL + Redis Cache\n- **Microservices on AKS**: AKS + Service Bus + Cosmos DB + API Management\n- **Serverless Event-Driven**: Functions + Event Grid + Service Bus + Cosmos DB\n- **Data Pipeline**: Data Factory + Synapse Analytics + Data Lake Storage + Event Hubs\n\nSee `references\u002Farchitecture_patterns.md` for detailed pattern specifications.\n\n**Validation checkpoint:** Confirm the recommended pattern matches the team's operational maturity and compliance requirements before proceeding to Step 3.\n\n### Step 3: Generate IaC Templates\n\nCreate infrastructure-as-code for the selected pattern:\n\n```bash\n# Web app stack (Bicep)\npython scripts\u002Fbicep_generator.py --arch-type web-app --output main.bicep\n```\n\n**Example Bicep output (core web app resources):**\n\n```bicep\n@description('The environment name')\nparam environment string = 'dev'\n\n@description('The Azure region for resources')\nparam location string = resourceGroup().location\n\n@description('The application name')\nparam appName string = 'myapp'\n\n\u002F\u002F App Service Plan\nresource appServicePlan 'Microsoft.Web\u002Fserverfarms@2023-01-01' = {\n  name: '${environment}-${appName}-plan'\n  location: location\n  sku: {\n    name: 'P1v3'\n    tier: 'PremiumV3'\n    capacity: 1\n  }\n  properties: {\n    reserved: true \u002F\u002F Linux\n  }\n}\n\n\u002F\u002F App Service\nresource appService 'Microsoft.Web\u002Fsites@2023-01-01' = {\n  name: '${environment}-${appName}-web'\n  location: location\n  properties: {\n    serverFarmId: appServicePlan.id\n    httpsOnly: true\n    siteConfig: {\n      linuxFxVersion: 'NODE|20-lts'\n      minTlsVersion: '1.2'\n      ftpsState: 'Disabled'\n      alwaysOn: true\n    }\n  }\n  identity: {\n    type: 'SystemAssigned'\n  }\n}\n\n\u002F\u002F Azure SQL Database\nresource sqlServer 'Microsoft.Sql\u002Fservers@2023-05-01-preview' = {\n  name: '${environment}-${appName}-sql'\n  location: location\n  properties: {\n    administrators: {\n      azureADOnlyAuthentication: true\n    }\n    minimalTlsVersion: '1.2'\n  }\n}\n\nresource sqlDatabase 'Microsoft.Sql\u002Fservers\u002Fdatabases@2023-05-01-preview' = {\n  parent: sqlServer\n  name: '${appName}-db'\n  location: location\n  sku: {\n    name: 'GP_S_Gen5_2'\n    tier: 'GeneralPurpose'\n  }\n  properties: {\n    autoPauseDelay: 60\n    minCapacity: json('0.5')\n  }\n}\n```\n\n> Full templates including Front Door, Key Vault, Managed Identity, and monitoring are generated by `bicep_generator.py` and also available in `references\u002Farchitecture_patterns.md`.\n\n**Bicep is the recommended IaC language for Azure.** Prefer Bicep over ARM JSON templates: Bicep compiles to ARM JSON, has cleaner syntax, supports modules, and is first-party supported by Microsoft.\n\n### Step 4: Review Costs\n\nAnalyze estimated costs and optimization opportunities:\n\n```bash\npython scripts\u002Fcost_optimizer.py \\\n  --config current_resources.json \\\n  --json\n```\n\n**Example output:**\n\n```json\n{\n  \"current_monthly_usd\": 2000,\n  \"recommendations\": [\n    { \"action\": \"Right-size SQL Database GP_S_Gen5_8 to GP_S_Gen5_2\", \"savings_usd\": 380, \"priority\": \"high\" },\n    { \"action\": \"Purchase 1-year Reserved Instances for AKS node pools\", \"savings_usd\": 290, \"priority\": \"high\" },\n    { \"action\": \"Move Blob Storage to Cool tier for objects >30 days old\", \"savings_usd\": 65, \"priority\": \"medium\" }\n  ],\n  \"total_potential_savings_usd\": 735\n}\n```\n\nOutput includes:\n- Monthly cost breakdown by service\n- Right-sizing recommendations\n- Reserved Instance and Savings Plan opportunities\n- Potential monthly savings\n\n### Step 5: Configure CI\u002FCD\n\nSet up Azure DevOps Pipelines or GitHub Actions with Azure:\n\n```yaml\n# GitHub Actions — deploy Bicep to Azure\nname: Deploy Infrastructure\non:\n  push:\n    branches: [main]\n\npermissions:\n  id-token: write\n  contents: read\n\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - uses: azure\u002Flogin@v2\n        with:\n          client-id: ${{ secrets.AZURE_CLIENT_ID }}\n          tenant-id: ${{ secrets.AZURE_TENANT_ID }}\n          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}\n\n      - uses: azure\u002Farm-deploy@v2\n        with:\n          resourceGroupName: rg-myapp-dev\n          template: .\u002Finfra\u002Fmain.bicep\n          parameters: environment=dev\n```\n\n```yaml\n# Azure DevOps Pipeline\ntrigger:\n  branches:\n    include:\n      - main\n\npool:\n  vmImage: 'ubuntu-latest'\n\nsteps:\n  - task: AzureCLI@2\n    inputs:\n      azureSubscription: 'MyServiceConnection'\n      scriptType: 'bash'\n      scriptLocation: 'inlineScript'\n      inlineScript: |\n        az deployment group create \\\n          --resource-group rg-myapp-dev \\\n          --template-file infra\u002Fmain.bicep \\\n          --parameters environment=dev\n```\n\n### Step 6: Security Review\n\nValidate security posture before production:\n\n- **Identity**: Entra ID (Azure AD) with RBAC, Managed Identity for service-to-service auth — never store credentials in code\n- **Secrets**: Key Vault for all secrets, certificates, and connection strings\n- **Network**: NSGs on all subnets, Private Endpoints for PaaS services, Application Gateway with WAF\n- **Encryption**: TLS 1.2+ in transit, Azure-managed or customer-managed keys at rest\n- **Monitoring**: Microsoft Defender for Cloud enabled, Azure Policy for guardrails\n- **Compliance**: Azure Policy assignments for SOC 2 \u002F HIPAA \u002F ISO 27001 initiatives\n\n**If deployment fails:**\n\n1. Check the deployment status:\n   ```bash\n   az deployment group show \\\n     --resource-group rg-myapp-dev \\\n     --name main \\\n     --query 'properties.error'\n   ```\n2. Review Activity Log for RBAC or policy errors.\n3. Validate the Bicep template before deploying:\n   ```bash\n   az bicep build --file main.bicep\n   az deployment group validate \\\n     --resource-group rg-myapp-dev \\\n     --template-file main.bicep\n   ```\n\n**Common failure causes:**\n- RBAC permission errors — verify the deploying principal has Contributor on the resource group\n- Resource provider not registered — run `az provider register --namespace Microsoft.Web`\n- Naming conflicts — Azure resource names are often globally unique (storage accounts, web apps)\n- Quota exceeded — request quota increase via Azure Portal > Subscriptions > Usage + quotas\n\n---\n\n## Tools\n\n### architecture_designer.py\n\nGenerates architecture pattern recommendations based on requirements.\n\n```bash\npython scripts\u002Farchitecture_designer.py \\\n  --app-type web_app \\\n  --users 50000 \\\n  --requirements '{\"budget_monthly_usd\": 1000, \"compliance\": [\"HIPAA\"]}' \\\n  --json\n```\n\n**Input:** Application type, expected users, JSON requirements\n**Output:** Recommended pattern, service stack, cost estimate, pros\u002Fcons\n\n### cost_optimizer.py\n\nAnalyzes Azure resource configurations for cost savings.\n\n```bash\npython scripts\u002Fcost_optimizer.py --config resources.json --json\n```\n\n**Input:** JSON file with current Azure resource inventory\n**Output:** Recommendations for:\n- Idle resource removal\n- VM and database right-sizing\n- Reserved Instance purchases\n- Storage tier transitions\n- Unused public IPs and load balancers\n\n### bicep_generator.py\n\nGenerates Bicep template scaffolds from architecture type.\n\n```bash\npython scripts\u002Fbicep_generator.py --arch-type microservices --output main.bicep\n```\n\n**Output:** Production-ready Bicep templates with:\n- Managed Identity (no passwords)\n- Key Vault integration\n- Diagnostic settings for Azure Monitor\n- Network security groups\n- Tags for cost allocation\n\n---\n\n## Quick Start\n\n### Web App Architecture (\u003C $100\u002Fmonth)\n\n```\nAsk: \"Design an Azure web app for a startup with 5000 users\"\n\nResult:\n- App Service (B1 Linux) for the application\n- Azure SQL Serverless for relational data\n- Azure Blob Storage for static assets\n- Front Door (free tier) for CDN and routing\n- Key Vault for secrets\n- Estimated: $40-80\u002Fmonth\n```\n\n### Microservices on AKS ($500-2000\u002Fmonth)\n\n```\nAsk: \"Design a microservices architecture on Azure for a SaaS platform with 50k users\"\n\nResult:\n- AKS cluster with 3 node pools (system, app, jobs)\n- API Management for gateway and rate limiting\n- Cosmos DB for multi-model data\n- Service Bus for async messaging\n- Azure Monitor + Application Insights for observability\n- Multi-zone deployment\n```\n\n### Serverless Event-Driven (\u003C $200\u002Fmonth)\n\n```\nAsk: \"Design an event-driven backend for processing orders\"\n\nResult:\n- Azure Functions (Consumption plan) for compute\n- Event Grid for event routing\n- Service Bus for reliable messaging\n- Cosmos DB for order data\n- Application Insights for monitoring\n- Estimated: $30-150\u002Fmonth depending on volume\n```\n\n### Data Pipeline ($300-1500\u002Fmonth)\n\n```\nAsk: \"Design a data pipeline for ingesting 10M events\u002Fday\"\n\nResult:\n- Event Hubs for ingestion\n- Stream Analytics or Functions for processing\n- Data Lake Storage Gen2 for raw data\n- Synapse Analytics for warehouse\n- Power BI for dashboards\n```\n\n---\n\n## Input Requirements\n\nProvide these details for architecture design:\n\n| Requirement | Description | Example |\n|-------------|-------------|---------|\n| Application type | What you're building | SaaS platform, mobile backend |\n| Expected scale | Users, requests\u002Fsec | 10k users, 100 RPS |\n| Budget | Monthly Azure limit | $500\u002Fmonth max |\n| Team context | Size, Azure experience | 3 devs, intermediate |\n| Compliance | Regulatory needs | HIPAA, GDPR, SOC 2 |\n| Availability | Uptime requirements | 99.9% SLA, 1hr RPO |\n\n**JSON Format:**\n\n```json\n{\n  \"application_type\": \"saas_platform\",\n  \"expected_users\": 10000,\n  \"requests_per_second\": 100,\n  \"budget_monthly_usd\": 500,\n  \"team_size\": 3,\n  \"azure_experience\": \"intermediate\",\n  \"compliance\": [\"SOC2\"],\n  \"availability_sla\": \"99.9%\"\n}\n```\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It Fails | Do This Instead |\n|---|---|---|\n| ARM JSON templates for new projects | Verbose, hard to read, no modules | Use Bicep — compiles to ARM, cleaner syntax |\n| Storing secrets in App Settings | Secrets visible in portal, no rotation | Use Key Vault references in App Settings |\n| Single large AKS node pool | Cannot optimize for different workloads | Use multiple node pools: system, app, jobs |\n| Public endpoints on PaaS services | Exposed attack surface | Use Private Endpoints + VNet integration |\n| Over-provisioning \"just in case\" | Wastes budget month one | Start small, use autoscale, right-size monthly |\n| Shared resource groups for everything | Blast radius, RBAC nightmares | One resource group per environment per workload |\n| No tagging strategy | Cannot track costs or ownership | Tag: environment, owner, cost-center, app-name |\n| Using classic resources | Deprecated, limited features | Use ARM\u002FBicep resources exclusively |\n\n---\n\n## Output Formats\n\n### Architecture Design\n\n- Pattern recommendation with rationale\n- Service stack diagram (ASCII)\n- Monthly cost estimate and trade-offs\n\n### IaC Templates\n\n- **Bicep**: Recommended — first-party, module support, clean syntax\n- **ARM JSON**: Generated from Bicep when needed\n- **Terraform HCL**: Multi-cloud compatible using azurerm provider\n\n### Cost Analysis\n\n- Current spend breakdown with optimization recommendations\n- Priority action list (high\u002Fmedium\u002Flow) and implementation checklist\n\n---\n\n## Cross-References\n\n| Skill | Relationship |\n|-------|-------------|\n| `engineering-team\u002Faws-solution-architect` | AWS equivalent — same 6-step workflow, different services |\n| `engineering-team\u002Fgcp-cloud-architect` | GCP equivalent — completes the cloud trifecta |\n| `engineering-team\u002Fsenior-devops` | Broader DevOps scope — pipelines, monitoring, containerization |\n| `engineering\u002Fterraform-patterns` | IaC implementation — use for Terraform modules targeting Azure |\n| `engineering\u002Fci-cd-pipeline-builder` | Pipeline construction — automates Azure DevOps and GitHub Actions |\n\n---\n\n## Reference Documentation\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Farchitecture_patterns.md` | 5 patterns: web app, microservices\u002FAKS, serverless, data pipeline, multi-region |\n| `references\u002Fservice_selection.md` | Decision matrices for compute, database, storage, messaging, networking |\n| `references\u002Fbest_practices.md` | Naming conventions, tagging, RBAC, network security, monitoring, DR |\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering-team\u002Fazure-cloud-architect",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill azure-cloud-architect",{"tool":63,"command":64},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill azure-cloud-architect",{"tool":66,"command":67},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill azure-cloud-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fazure-cloud-architect\u002FSKILL.md",true,[71,77,81,85,91,95],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Farchitecture_patterns.md","REFERENCE","参考文档",17911,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fazure-cloud-architect\u002Freferences\u002Farchitecture_patterns.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fbest_practices.md",12257,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fazure-cloud-architect\u002Freferences\u002Fbest_practices.md",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fservice_selection.md",11119,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fazure-cloud-architect\u002Freferences\u002Fservice_selection.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Farchitecture_designer.py","SCRIPT","脚本",21966,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fazure-cloud-architect\u002Fscripts\u002Farchitecture_designer.py",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fbicep_generator.py",23663,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fazure-cloud-architect\u002Fscripts\u002Fbicep_generator.py",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fcost_optimizer.py",21203,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fazure-cloud-architect\u002Fscripts\u002Fcost_optimizer.py",[100,131,156,181,208,228],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":44},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,30],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":44},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[138,139,140,141,142,143,144,145,119,120,146,147,148,149,150,151,152,153,154,155],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":44},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[163,164,165,166,167,168,169,170,171,120,172,173,174,175,176,177,178,179,180,30],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":191,"publishedAt":44},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[187,188],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":189,"categoryName":190,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000032","设计师",[192,193,180,38,194,195,196,197,198,120,199,200,201,202,203,204,205,206,30,207],"quality manager qms iso13485","quality","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":44},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[214],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[216,193,180,217,218,219,220,221,112,222,198,223,164,224,225,226,147,203,30,227],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":241,"publishedAt":44},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[234,237,240],{"categoryNo":235,"categoryName":236,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":238,"categoryName":239,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[242,243,193,180,217,244,245,116,198,246,247,248,249,250,148,251,252,253,254,30],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]