Cost Analysis

by microsoft354361d83247MITListed Oct 8, 2026Updated Oct 8, 2026

Analyze actual Azure spend, bill changes, and AKS or AI costs. WHEN: "Azure cost breakdown", "most expensive resources", "why did my bill increase", "cost spike", "unexpected charge", "Cosmos DB charges", "Foundry model costs", "AKS cluster cost", "namespace cost", "enable AKS cost analysis", "idle AKS capacity". DO NOT USE FOR: forecasts, pricing estimates, rightsizing, commitments, or budgets.

FeaturedInstructions onlyBusiness & FinanceData & Analytics
AI-generated overview

Analyzes actual Azure spend, bill changes, and AKS or AI service costs using cost query and Resource Graph tools.

What it does
Guides an agent through querying historical Azure spend, investigating bill spikes and unexpected charges, and allocating costs for AKS clusters and AI services. It routes each intent to a matching reference workflow and defines error handling for access, empty results, and multiple currencies. Outputs are cost breakdowns and explanations that separate measured cost from inferred causes.
When to use it
Use when someone asks for an Azure cost breakdown, the most expensive resources, a bill increase or cost spike, or AKS namespace and cluster costs. It is not intended for forecasts, pricing estimates, rightsizing, commitments, or budgets.
Requirements
Requires access to Azure cost query and Resource Graph MCP tools with appropriate scope and role permissions. Instructions only; no scripts are shipped.

Azure Cost Analysis

Quick Reference

IntentWorkflowPrimary tools
Query historical spendCost query [blocked]query_costs
Explain a spikeCost investigation [blocked]query_costs, Resource Graph
Analyze AKS spendAKS cost analysis [blocked]query_aks_costs, Resource Graph
Analyze AI service spendAI cost analysis [blocked]query_costs

When to Use This Skill

Use for spend, anomalies, and AKS or AI allocation.

MCP Tools

Use cost tools and Resource Graph first. If an operation is unavailable, follow fallback and safety [blocked].

Workflow

  1. Confirm scope, period, currency, and breakdown.
  2. Load only the matching workflow above.
  3. Never transform MCP results in a shell or interpreter; request tool-side totals, grouping, sorting, or bounded follow-up queries.
  4. Respect row limits and label incomplete data.
  5. Separate measured cost from inferred causes and recommendations.

Error Handling

ErrorAction
Access deniedName the required scope and role.
Empty resultDistinguish no data from unavailable data.
Multiple currenciesReport each currency separately.
Server errorRetry once; then stop with the trace ID.

Source and attribution

Source:microsoft/skillsin.github/plugins/azure-cost/skills/cost-analysisat commit354361d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal