references/commitments.md
Commitment Analysis
Resolve Scope and Terms
- Require an accessible billing scope for portfolio utilization. If the user
supplies only a subscription, resolve or ask for its billing account and
billing profile before calling
list_benefit_utilization. - Keep Reservations and Savings Plans separate. Report commitment name, term, scope, region or service constraints, quantity or hourly commitment, utilization period, currency, and expiration when available.
- Distinguish:
- utilization: how much purchased commitment was consumed;
- coverage: how much eligible usage received commitment pricing;
- savings: tool-reported benefit for its stated period. High utilization can coexist with low coverage, and low utilization does not prove that a new purchase is needed.
- When the target usage includes AKS, check the host skill inventory and
invoke
aks-cost-optimizationfor its commitment-demand handoff when available. Reuse its time-aligned SKU or compatible compute group, region and zone, Spot/on-demand capacity type, observed hours and node counts, lookback coverage, exact resource mapping, planned changes, CRG impact, variability, and evidence gaps. If representative compute history is missing, report stable demand as unverified and do not validate an AKS commitment recommendation. Do not install the optional plugin without user consent.
Analyze Current Commitments
- Report utilization per commitment. Treat less than 90% as an investigation signal, not an automatic exchange or refund recommendation.
- Call
query_costswithAmortizedCost, grouped byPricingModel, for the same period. Report committed and eligible on-demand spend per currency. Compare actual and amortized views when a recent purchase distorts cash cost. - For low utilization, inspect
list_reservation_transactionsover the supported lookback and correlate purchases, refunds, or exchanges with scope, region, family, and resource-inventory changes. Missing history is inconclusive.
Evaluate New Recommendations
- Call
get_benefit_recommendations. Preserve lookback, term, scope, savings amount and percentage, coverage, and expected utilization. Do not relabel period savings as monthly savings or combine currencies. - Check whether rightsizing, shutdowns, migrations, expiring commitments, or policy restrictions would invalidate the recommendation. Present exchange, scope adjustment, workload alignment, expiration planning, or a new purchase as distinct options with evidence and tradeoffs.
Report and Safety
Present utilization and coverage separately, eligible on-demand spend, current commitment risks, new recommendations, confidence, and the next review date. Never purchase, exchange, or refund without explicit approval.
If a benefit or reservation tool is unavailable, use the API mapped in tool fallback. Preserve its period and scope semantics.