Skip to main content

cost-governance

Govern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost guardrails". DO NOT USE FOR: planning-target forecasts, bill investigations, pricing, rightsizing, or commitments.

소스 정보

저장소
microsoft/skills
최근 소스 활동
2026년 9월 23일 11:05
감지된 SKILL.md 언어
영어
스타
3,101
포크
350

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
5 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
cost-governance
description
Govern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost guardrails". DO NOT USE FOR: planning-target forecasts, bill investigations, pricing, rightsizing, or commitments.
license
MIT
metadata
{"author":"Microsoft","version":"1.0.1"}
# Cost Governance ## Quick Reference | Intent | Workflow | Primary tools | |--------|----------|---------------| | Check budget status | [Budget health](references/budget-health.md) | `list_budgets`, `forecast_costs`, `query_costs`, `list_alerts` | | Configure a budget | [Budget setup](references/budget-setup.md) | Cost tools, `create_budget` | | Review guardrails | [Guardrails](references/guardrails.md) | Resource Graph, `list_budgets` | ## When to Use This Skill Use for budgets, alerts, tags, and policy. ## MCP Tools Use cost tools for budgets; Resource Graph for guardrails. Writes need confirmed scope, amount, thresholds, and recipients. Fallback: [API mappings](references/tool-fallback.md). ## Workflow 1. Confirm scope and load the matching workflow. 2. Never transform MCP results in a shell or interpreter; request tool-side filtering or bounded follow-up queries. 3. Distinguish access failures from empty results. 4. Report gaps without implying budgets cap spend. ## Error Handling | Error | Action | |-------|--------| | Access denied | Name missing permission. | | No budget or forecast | Report unavailable data, not zero. | | Multiple currencies | Never sum or compare across currencies. | | Write conflict | Preserve the budget. | | Server error | Retry once; then stop with the trace ID. |
GitHub에서 보기