azure-patterns

Implements production Azure infrastructure patterns using Bicep modules, AKS Workload Identity, and Azure DevOps pipelines.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/HermeticOrmus/LibreDevOps-Claude-Code --skill azure-patterns-hermeticormus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-patterns
Source: https://github.com/HermeticOrmus/LibreDevOps-Claude-Code/tree/main/plugins/azure-infrastructure/skills/azure-patterns
Command: npx skills add https://github.com/HermeticOrmus/LibreDevOps-Claude-Code --skill azure-patterns-hermeticormus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams deploying to Azure often struggle with scattered Bicep templates, secrets leaking into pod environment variables, and inconsistent governance across environments. This Skill provides proven infrastructure patterns that eliminate these common pitfalls. ## Core Features & Use Cases - Bicep Module Structure: Organize infrastructure as composable modules for network, compute, data, and security with per-environment parameter files. - AKS Workload Identity: Configure OIDC issuers, federated credentials, and managed identities so pods access Azure resources without stored secrets. - Governance & Networking: Apply private endpoints with DNS zones for PaaS services and enforce tagging policies at management group scope. - Use Case: When provisioning a new AKS-based application, use these patterns to wire up Workload Identity, Key Vault references in App Service, and an Azure DevOps pipeline that builds to ACR and deploys with environment approvals. ## Quick Start Ask the AI to generate a Bicep template for an AKS cluster with Workload Identity enabled and a federated credential for a Kubernetes ServiceAccount.

Frequently Asked Questions about azure-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up AKS Workload Identity with Bicep?▼

Enable the OIDC issuer and workload identity security profile on the AKS cluster, create a user-assigned managed identity, then add a federated identity credential bound to the Kubernetes ServiceAccount subject. Annotate the ServiceAccount with the identity client ID and label pods with azure.workload.identity/use.

How to structure Bicep modules for multiple environments?▼

Use a root main.bicep that orchestrates modules for network, compute, data, and security, with separate .bicepparam files per environment such as dev and prod. Modules pass values through outputs, like subnet IDs consumed by the AKS module.

Can App Service read Key Vault secrets without storing them?▼

Yes, use Key Vault references in app settings with the @Microsoft.KeyVault(SecretUri=...) syntax and a system-assigned managed identity. Grant the identity the Key Vault Secrets User role so secrets never appear in the App Service configuration plane.

Does Azure DevOps support deployment approvals for AKS?▼

Yes, deployment jobs target an environment resource where approvals and gates are configured in the Azure DevOps UI. The pipeline can build images to ACR in one stage and deploy to AKS with kubectl set image in a gated production stage.

Why use private endpoints for Azure SQL instead of firewall rules?▼

Private endpoints give the PaaS service a private IP inside your VNet, removing public internet exposure entirely. Pair them with a private DNS zone like privatelink.database.windows.net so name resolution stays inside the network.