| name | azure-infrastructure |
| description | Azure infrastructure patterns and best practices |
When to Use
- Infrastructure planning and design
- Azure Verified Modules reference
- CAF naming convention guidance
- Resource provisioning patterns
Prerequisites
- Azure subscription access
- Terraform knowledge
- Understanding of Azure services
Reference Patterns
Resource Group Naming
rg-<project>-<environment>-<region>
Example: rg-myproject-prod-eastus2
AKS Cluster Naming
aks-<project>-<environment>-<region>
Example: aks-myproject-prod-eastus2
Key Vault Naming
kv-<project>-<environment>-<region>
Example: kv-myproject-prod-eus2
Storage Account Naming
st<project><environment><region>
Example: stmyprojectprodeus2
Required Tags
locals {
common_tags = {
Environment = var.environment
Project = var.project_name
Owner = var.owner
CostCenter = var.cost_center
ManagedBy = "terraform"
}
}
Security Patterns
- Use Workload Identity (not service principals)
- Enable private endpoints for PaaS services
- Configure NSGs with deny-all default
- Enable Azure Defender for Cloud
Best Practices
- Use Azure Verified Modules when available
- Follow CAF naming conventions
- Enable diagnostic settings
- Configure resource locks for production
- Use managed identities
Integration with Agents
Used by: @terraform, @security, @devops