AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--cost-governance at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 5

references/tool-fallback.md

Governance Tool Fallback

Use ARM MCP first. If the required operation is unavailable, name the API and use an already authenticated Azure CLI, Azure PowerShell, or REST client.

| Workflow | Fallback API | |---|---| | Budget read or write | Cost Management Budgets API | | Cost alerts | Cost Management Alerts API | | Spend or forecast | Cost Management Query or Forecast API | | Tag and policy inventory | Azure Resource Graph Resources API | | Policy details | Azure Policy Assignments and Definitions APIs |

Prefer native commands when they expose the required fields; otherwise use az rest, Invoke-AzRestMethod, or authenticated REST. Preserve scope, currency, time grain, thresholds, contacts, filters, and pagination. State which fallback was used and never expose access tokens.

Do not invoke Bash, PowerShell, Python, or another local interpreter merely to parse or aggregate an MCP response. Request server-side grouping or filtering, or issue smaller bounded MCP queries. Use shell clients only for an approved API fallback when the required MCP operation is unavailable.

Do not fall back for denied access, invalid input, throttling, or empty data. Budget or policy writes still require an explicit preview and user confirmation.