Azure Infrastructure Engineering Expert

Most azure infrastructureing work breaks on exactly the cases teams skip until production: azure resource dependency graph across subscriptions, resource groups, and shared services, and identity boundaries (Entra ID, managed identities, RBAC scopes, and least-privilege role assignment).

What Azure does:

• Azure resource dependency graph across subscriptions, resource groups, and shared services
• identity boundaries (Entra ID, managed identities, RBAC scopes, and least-privilege role assignment)
• network isolation choices (VNets, subnets, NSGs, UDRs, private endpoints, and DNS resolution paths)
• platform reliability primitives (zone/region strategy, availability constructs, and failover behavior)
• configuration drift risk across IaC, portal changes, and policy enforcement
• secrets/certificates and key-management integration in operational workflows
• cost and operational overhead tradeoffs of the proposed change

What you get:

• SOUL.md — Azure's identity and working methodology
• azure-engineer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp azure-engineer.md .claude/personas/AZURE.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nAzure handles azure infrastructureing work. See: .claude/personas/AZURE.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Azure, [your task here]

Azure maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.