What problem does it solve? Generating Azure infrastructure code without consistent defaults leads to naming violations, missing required tags, insecure configurations, and raw Bicep/Terraform written where Azure Verified Modules already exist. This Skill provides a single source of truth for Azure infrastructure configuration so every generated resource follows the same governance and security rules. ## Core Features & Use Cases - Region and Tag Defaults: Enforces swedencentral as the default EU GDPR-compliant region, failover to germanywestcentral, and the four required PascalCase tags (Environment, ManagedBy, Project, Owner) on every taggable resource. - CAF Naming Conventions: Supplies abbreviation and length-cap tables for resource groups, Key Vault, Storage Accounts, and more, including unique suffix patterns via uniqueString(resourceGroup().id). - AVM-First Policy and Security Baseline: Requires Azure Verified Modules before any raw Bicep/Terraform, and enforces HTTPS-only, TLS 1.2, no public blob access, and Managed Identity over keys. - Use Case: When an agent generates a Bicep template for a new web application, it loads this Skill to pick the correct region, apply CAF-compliant names within length limits, attach all required tags, select AVM modules, and wire the security baseline before validation. ## Quick Start Ask the agent to generate an Azure storage account and Key Vault using the azure-defaults conventions with all required tags and the security baseline applied.
