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/pricing-estimate.md

Pricing Estimate

  1. Confirm service, SKU, region, OS, tier, usage quantity, and billing period. Ask only for missing details needed to disambiguate a meter.
  2. Call get_retail_prices. Compare options with separate calls when needed. Preserve productName, skuName, armSkuName, price type, unit, region, and currency so the selected row is auditable. The tool requests up to 5000 rows. If Count reaches that limit or NextPageLink is present, narrow the filters and disclose that the result set was truncated; do not invoke the returned URL directly.
  3. Exclude Spot, Dev/Test, Windows, Reservation, or Savings Plan meters unless they match the request. If multiple plausible meters remain, ask for the minimum missing detail or show a short candidate table containing productName, skuName, armSkuName, meter name, and price type. Never silently choose among multiple meter shapes.
  4. Show unit price x usage = estimated period cost and list every assumption. Reservation prices are term purchase totals; normalize one-year prices by 12 and three-year prices by 36. Savings Plan and consumption prices are hourly meter rates and may be multiplied by expected hours.
  5. For negotiated rates, confirm the Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA) billing scope. Call start_pricesheet_download, then poll get_pricesheet_status using its retry interval. Label retail and negotiated values separately. If a pricing operation is unavailable, use the mapped API from tool fallback.
  6. Pricesheet downloads return a short-lived ZIP URL. The MCP server does not download or parse it. Return the URL and ask the user to download and provide the file for comparison; do not claim a negotiated-price analysis before the file is available.

Retail estimates are not bills or realized savings. If the user provides an existing scope and wants current spend, hand off to cost-analysis.