1# Azure Cost Skill Reference
2 
3## MCP Tools
4 
5| Tool | Description | Parameters | When to Use |
6|------|-------------|------------|-------------|
7| `azure__documentation` | Search Azure documentation | `query` (Required): search terms | Research Cost Management API parameters and options |
8| `azure__extension_cli_generate` | Generate Azure CLI commands | `intent` (Required): task description, `cli-type` (Required): `"az"` | Construct `az rest` commands for cost queries |
9| `azure__get_azure_bestpractices` | Get Azure best practices | `intent` (Required): optimization context | Inform query design with cost management best practices |
10| `azure__extension_azqr` | Run Azure Quick Review compliance scan | `subscription` (Required): subscription ID, `resource-group` (Optional): resource group name | Find orphaned resources and cost optimization opportunities |
11| `azure__aks` | Azure Kubernetes Service operations | varies by sub-command | AKS cost analysis: list clusters, get node pools, inspect configuration |
12 
13> Prefer MCP tools over direct CLI commands. Use `az rest` only when MCP tools don't cover the specific operation.
14 
15## Data Classification
16 
17- **ACTUAL DATA** = Retrieved from Azure Cost Management API
18- **ACTUAL METRICS** = Retrieved from Azure Monitor
19- **VALIDATED PRICING** = Retrieved from official Azure pricing pages
20- **ESTIMATED SAVINGS** = Calculated based on actual data and validated pricing
21 
22## Best Practices
23 
24- Always query actual costs first, never estimate or assume
25- Always present the total bill alongside optimization recommendations
26- Validate pricing from official sources, account for free tiers
27- Use REST API for cost queries (more reliable than `az costmanagement query`)
28- Always include the `ClientType: GitHubCopilotForAzure` header on all Cost Management API requests (`--headers "ClientType=GitHubCopilotForAzure"` in `az rest`)
29- Save audit trail with all queries and responses
30- Include Azure Portal links for all resources
31- For costs < $10/month, emphasize operational improvements over financial savings
32- Never execute destructive operations without explicit approval
33- On 429 responses, check all `x-ms-ratelimit-microsoft.costmanagement-*-retry-after` headers (`qpu-retry-after`, `entity-retry-after`, `tenant-retry-after`), wait for the longest value, and don't retry until that duration has elapsed. The per-scope limit (4 requests/minute) is the most restrictive.
34 
35## Common Pitfalls
36 
37- **Assuming costs**: Always query actual data from Cost Management API
38- **Ignoring free tiers**: Many services have generous allowances
39- **Using wrong date ranges**: 30 days for costs, 14 days for utilization
40- **Not showing the bill**: Always present cost breakdown alongside optimization recommendations
41- **Cost query failures**: Use `az rest` with JSON body, not `az costmanagement query`
42 
43## Safety Requirements
44 
45- Get approval before deleting resources
46- Test changes in non-production first
47- Provide dry-run commands for validation
48- Include rollback procedures
49