julianobarbosa/claude-code-skills/azure-finops

AzureFinOps Skill

Azure cost optimization through reservation analysis, waste discovery, and stakeholder reporting.

Important

• All Azure operations are READ-ONLY — zero modifications to any resource
• Primary output language: Portuguese (BR) for stakeholder responses
• Python CLI fallback: uv run python -m azure_finops when MCP/CLI auth unavailable

Context Files

• AzureToolReference.md — MCP tools + CLI commands quick reference
• ReservationInventory.md — SKU matching and reservation interpretation SOP
• PricingComparison.md — PAYG vs RI pricing methodology and savings formulas

Workflow Routing

Examples

Example 1 — Cost Validation:

"Are these January costs reservations or pay-as-you-go?"

Routes to: Workflows/ValidateCosts.md

Example 2 — Waste Discovery:

"Find orphaned disks and wasted resources across all subscriptions"

Routes to: Workflows/FindWaste.md

Example 3 — Executive Response:

"Draft a response for Jean about the January billing anomalies"

Routes to: Workflows/DraftResponse.md

Gotchas

• Reservation matching: SKU naming differs between usage data and purchase data — Standard_D8s_v3 in usage vs D8sv3 in RI. A direct join misses 100%.
• Savings Plan vs Reservation can stack — calculators that pick one ignore the combined savings.
• PAYG vs RI pricing: Marketplace listings are excluded from RI — surprise unreserved charges show up for SQL Server BYOL, etc.
• Cost data lag is 24-48 hours — same-day analyses miss recent activity entirely.
• RI scope (shared vs single-subscription): wrong scope means the RI applies to unintended workloads — and you discover it months later in an audit.
• Currency conversion in EA reports: exchange rate is locked at month close; mid-month estimates use a different rate than the final invoice.