C✳CODEZ.WIN
🌐 English

Localized reading guide

cost-governancePurpose, usage and source

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.

Source retrieved:

Source repository
microsoft/skills
SKILL.md
.github/plugins/azure-cost/skills/cost-governance/SKILL.md
Repository stars
3,157
Repository updated
2026-10-31
Categories
Cloud
Last collected

License: License file needs review

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

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.

How the upstream workflow works

Workflow

Confirm scope and load the matching workflow. Never transform MCP results in a shell or interpreter; request tool-side filtering or bounded follow-up queries. Distinguish access failures from empty results. Report gaps without implying budgets cap spend.

Upstream passage · L30 ↗

When to Use This Skill

Use for budgets, alerts, tags, and policy.

Upstream passage · L20 ↗

MCP Tools

Use cost tools for budgets; Resource Graph for guardrails. Writes need confirmed scope, amount, thresholds, and recipients. Fallback: API mappings.

Upstream passage · L24 ↗

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
00d66a64919edca5bca2c673373444e36a4b5461
Source SHA-256
4241add12fefc5e51afc1a925426dd5f7d3494e642753fedb03273a3f2fcd30a
Back to the full Skill catalog