Azure Advisor Cost Optimization

Use existing Advisor tools only with category=Cost and sub-category=IdleResources. Never substitute billing, inventory or runtime KQL. Preserve selected scope, type and tenant; pass supplied identities unchanged.

Shared rules

Use only returned structured retail savings; MCP owns calculations. Never annualize, reconstruct amounts from dates, or fall back to legacy annualSavingsAmount/savingsAmount or raw pricing. Cost is accumulated Advisor cost, not monthly spend or yearly savings. Completed reports use Realized savings. Every monetary answer or proposal visibly shows Currency and Pricing basis: <basis> from the calculated measure or its documented source. Missing amounts are Unavailable, not zero; numeric zero stays zero. Preserve a known basis even when amounts are missing. Potential savings depend on validating and deleting eligible resources. Estimates do not establish inactivity or safe deletion and never authorize remediation.

Workflow

Before each flow, read its matching references below, including when using supplied results. Before scoped calls, read Scope resolution. Reuse already loaded references. If a required file is unavailable, report it and stop the affected flow.

Use the matching scenario guidance; Reference index.

Quick reference

Flow	Required reference
Discovery and type expansion	Workflow
Counts, savings field mapping and pricing-source interpretation	Output and savings
Tables and selected resources	Table format
Completed/historical reports	Lifecycle
State changes	State updates
Selection/remediation handoff	Selection
Explicit prevalidation/safety checks	Selection
Filters/errors	Tools and recovery
Routing examples	Examples

Response guidance

Use shared headings and column order across models, with documented scope/lifecycle variations. Visibly show results/proposals before dependent questions; reasoning, tool output or text inside ask_user does not count. Ask directly for missing input.