AGENTIC MEMORY

Skills

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

← Back to Skills

cost-estimation

Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet". DO NOT USE FOR: configured budget health or alerts, bill analysis, cost spikes, 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-estimation 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 · 8

references/tool-fallback.md

Estimation 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 | |---|---| | Existing-scope forecast | Cost Management Forecast API | | Public SKU or meter price | Azure Retail Prices API | | Negotiated rates | Cost Management Price Sheet API |

Prefer native commands when they expose the required fields; otherwise use az rest, Invoke-AzRestMethod, or authenticated REST. Preserve scope, period, filters, pagination, currency, price type, and meter disambiguation. State which fallback was used and never expose access tokens or pricesheet URLs.

Do not invoke Bash, PowerShell, Python, or another local interpreter merely to parse or aggregate an MCP response. Request server-side 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 invalid input, denied access, throttling, or empty data. Fallback does not relax the 92-day forecast guardrail or make retail prices customer-specific.