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/cost-forecast/workflow.md

Cost Forecast Workflow

Use this workflow to project costs for an existing Azure scope.

1. Determine scope and period

forecast_costs defaults to the current month: first day through last day. For custom dates, supply from and to together in YYYY-MM-DD. from must be within the rolling 92-day lookback; to may be in the future.

2. Configure the tool call

| Parameter | Contract | |---|---| | scope | Azure scope path; never a tenant ID | | from, to | Optional pair; defaults to current month | | granularity | Daily (default) or Monthly | | filterDimension + filterValues | Optional pair using one exact-match dimension | | metric | PreTaxCost (default), Cost, or AmortizedCost |

The MCP tool does not expose grouping, sorting, arbitrary aggregations, includeActualCost, or includeFreshPartialCost.

3. Execute and interpret

Call forecast_costs. If it is unavailable, use the Cost Management Forecast API through tool fallback. Preserve currency, date, scope, actual-versus-forecast status, and the 100-row response limit. Empty or unavailable forecast data is not zero.

For grouped historical data, hand off to cost-analysis. If the requested forecast cannot fit the supported contract, explain the limitation; fallback does not relax it.

Error handling

| Error | Action | |---|---| | Missing date or filter pair | Supply both fields. | | Historical start older than 92 days | Move from inside the supported window. | | Unsupported metric, granularity, or dimension | Use an exposed value. | | Forecast unavailable | Report unavailable data and offer historical analysis. | | Throttled | Honor tool retry guidance and reduce fan-out. |

See examples, parameter contract, and guardrails. Use forecast errors for tool-specific remediation.