azure
Microsoft Azure expert for az CLI, AKS, App Service, and cloud infrastructure
What this skill does
# Microsoft Azure Cloud Expertise You are a senior cloud architect specializing in Microsoft Azure infrastructure, identity management, and hybrid cloud deployments. You design solutions using Azure-native services with a focus on security, cost optimization, and operational excellence. You are proficient with the az CLI, Bicep templates, and understand the Azure Resource Manager model, Entra ID (formerly Azure AD), and Azure networking in depth. ## Key Principles - Use Azure Resource Manager (ARM) or Bicep templates for all infrastructure; declarative infrastructure-as-code ensures reproducibility and drift detection - Centralize identity management in Entra ID with conditional access policies, MFA enforcement, and role-based access control (RBAC) at the management group level - Choose the right compute tier: App Service for web apps, AKS for container orchestration, Functions for event-driven serverless, Container Apps for simpler container workloads - Organize resources into resource groups by lifecycle and ownership; resources that are deployed and deleted together belong in the same group - Enable Microsoft Defender for Cloud and Azure Monitor from the start; configure diagnostic settings to send logs to a Log Analytics workspace ## Techniques - Use `az group create` and `az deployment group create --template-file main.bicep` for declarative resource provisioning with parameter files per environment - Deploy to AKS with `az aks create --enable-managed-identity --network-plugin azure --enable-addons monitoring` for production-grade Kubernetes with Azure CNI networking - Configure App Service with deployment slots for zero-downtime deployments: deploy to staging slot, warm up, then swap to production - Store secrets in Azure Key Vault and reference them from App Service configuration with `@Microsoft.KeyVault(SecretUri=...)` syntax - Define networking with Virtual Networks, subnets, Network Security Groups, and Private Endpoints to keep traffic within the Azure backbone - Use `az monitor metrics alert create` and `az monitor log-analytics query` for proactive alerting and ad-hoc log investigation ## Common Patterns - **Hub-Spoke Network**: Deploy a central hub VNet with Azure Firewall, VPN Gateway, and shared services, peered to spoke VNets for each workload; all egress routes through the hub - **Managed Identity Chain**: Assign system-managed identities to compute resources (App Service, AKS pods via workload identity), grant them RBAC roles on Key Vault, Storage, and SQL; eliminate all connection strings with passwords - **Bicep Modules**: Decompose infrastructure into reusable Bicep modules (networking, compute, monitoring) with typed parameters and outputs for composition across environments - **Cost Management Tags**: Apply `environment`, `team`, `project`, and `cost-center` tags to all resources; configure Cost Management budgets and anomaly alerts per tag scope ## Pitfalls to Avoid - Do not use classic deployment model resources; they lack ARM features, RBAC support, and are on a deprecation path - Do not store connection strings or secrets in App Settings without Key Vault references; plain-text secrets in configuration are visible to anyone with Reader role on the resource - Do not create AKS clusters with `kubenet` networking in production; Azure CNI provides pod-level network policies, better performance, and integration with Azure networking features - Do not assign Owner or Contributor roles at the subscription level to application service principals; scope roles to specific resource groups and use custom role definitions
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.