azure▌

Query metrics, logs, and traces across Azure Monitor, Application Insights, and Log Analytics. \n \n Access metrics, KQL log queries, and distributed tracing through MCP tools or Azure CLI commands \n Supports Application Insights for APM and performance analysis, Log Analytics for custom KQL queries, and Azure Monitor for infrastructure metrics \n Includes common KQL query patterns for errors, request performance, and resource usage monitoring \n Workbooks integration for building interactive o

Check and manage Azure quotas and usage across regions for deployment planning and capacity validation. \n \n Azure CLI ( az quota ) is the only reliable method for checking quotas; REST API and Portal are unreliable and show misleading \"No Limit\" values that do not indicate unlimited capacity \n Supports quota discovery, usage tracking, limit checking, and increase requests across compute, network, storage, and container services \n Quota resource names do not map 1:1 to ARM resource types; u

Query metrics, logs, and traces across Azure Monitor, Application Insights, and Log Analytics. \n \n Access Azure Monitor metrics, Application Insights APM data, and Log Analytics KQL queries through MCP tools or Azure CLI commands \n Supports distributed tracing, performance analysis, and infrastructure monitoring across applications and resources \n Includes interactive workbooks for building custom dashboards and reports on observability data \n Common use cases: error tracking, request perfo

Pre-deployment validation for Azure infrastructure, configuration, and permissions before deploying. \n \n Runs recipe-specific validation commands (azd provision, bicep build, terraform validate) and records proof in .azure/plan.md \n Requires .azure/plan.md from azure-prepare skill as input; blocks deployment if plan is missing or status is not Approved \n Validates azure.yaml, Bicep templates, Terraform configurations, Azure Functions, and app readiness across multiple deployment scenarios \n

Pre-deployment validation for Azure infrastructure, configuration, and permissions before deployment. \n \n Requires .azure/plan.md from a prior azure-prepare run; stops immediately if the plan is missing \n Executes recipe-specific validation commands (azd provision, bicep build, terraform validate) and records proof in the plan document \n Performs build verification, configuration checks, and permission validation; blocks deployment if any check fails \n Only authorized method to set plan sta

Execute Azure deployments for prepared applications with built-in error recovery and validation. \n \n Requires .azure/plan.md with Validated status from azure-validate and azure-prepare skills; will not proceed without both prerequisites \n Executes azd up , azd deploy , terraform apply , and az deployment commands with error handling and post-deployment verification \n Includes pre-deploy checklist, recipe-based deployment workflows, and post-deploy configuration for SQL managed identity and E

Prepare Azure applications for deployment with infrastructure-as-code, configuration, and containerization. \n \n Generates Bicep or Terraform infrastructure code, azure.yaml configuration, and Dockerfiles based on application type and deployment target \n Requires mandatory plan-first workflow: analyze workspace, gather requirements, select recipe (AZD, AZCLI, Bicep, or Terraform), design architecture, then execute only after user approval \n Covers new app creation, modernization, and updates;

Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters. Covers Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis). WHEN: create AKS environment, provision AKS environment, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS.

This skill handles assessment and automated upgrades of existing Azure workloads from one Azure service, hosting plan, or SKU to another — all within Azure. This includes plan/tier upgrades (e.g. Consumption → Flex Consumption), cross-service migrations (e.g. App Service → Container Apps), and SKU changes. This is NOT for cross-cloud migration — use azure-cloud-migrate for that.

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment'. PREFER