Veja em ação
Azure Advisor: scope, aggregate or list, and safe handoff
Complete original workflow and safety section. The host must expose the Azure Advisor MCP tools and the user must have access to the actual subscription or service group. Aggregate queries use summary, record queries use list, and state changes require confirmation. This is a workflow reference, not returned account data.
Entrada de exemplo
## Workflow
1. Identify subscription or service-group scope. Resource-group scope requires a subscription.
2. Reuse known scope and identifiers; ask only for missing values.
3. Use `summary` for aggregates and `list` for records. Never count a capped list.
4. Present only returned data, including truncation, access limitations, and errors.
Route requests to fix one recommendation to the `azure-advisor-actionability` skill. Otherwise choose the tool from the table, including `summary` or `list` for service retirements.
## Safety
Confirm before recommendation-state updates. The actionability skill owns remediation safeguards.Licença
Complete author Workflow section through end of document retained verbatim. Earlier header/quick-reference omitted; original full Skill document remains on the detail page. This is an authored workflow reference, not standalone executable code, live account data or an independently reproduced result. No source tool or instruction was executed.
MIT License
Copyright 2025 (c) Microsoft Corporation.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWAREComo usar
- Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
- Consulte no original as ferramentas, credenciais e ambientes necessários.
- Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/microsoft/azure-skills --skill azure-advisorAntes de começar
- A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
- Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.
Azure Advisor
Prefer Advisor MCP tools over Resource Graph or generic ARM calls. Reuse supplied scope and identifiers; ask only for missing input.
Quick reference
Prefer Azure Advisor MCP tools. Use their current schemas for parameters and limits; discover unfamiliar parameters rather than inventing them.
| Intent | Tool |
|---|---|
| Counts, totals, breakdowns, or distributions | advisor_recommendation_summary; non-prioritized, with the requested group-by |
| Broad priorities: top recommendations/actions, most important, critical, or fix-first advice | advisor_recommendation_summary; prioritized: true (automatically groups by recommendation type) |
| Individual recommendations or affected resources, including status-filtered records | advisor_recommendation_list; no prior summary required; for priority ordering within a known type, pass one recommendation-type-ids array entry and prioritized: true |
| Complete, dismiss, postpone, or reactivate | advisor_recommendation_update |
| Browse recommendation types | advisor_metadata_list |
| Get one type by ID | advisor_metadata_get |
| Fix or remediate a recommendation | azure-advisor-actionability skill; it owns remediation tool calls and safeguards |
Workflow
- For unused-resource discovery, including "what are we paying for that is no longer
being used", or combined category=Cost and sub-category=IdleResources, load azure-advisor-cost-optimization first. It owns scope, sequencing and response templates; broad discovery must not skip to resource details.
- Generic/prioritized Cost outside IdleResources, cross-category and other requests stay here.
Preserve requested filters; never silently add IdleResources.
- Before generic calls or reporting, read Workflow.
- For remediation, load
azure-advisor-actionability; it owns execution safeguards.
- Reuse known scope and identifiers. Pass the requested count as
top: groups for summary, records for list. "Critical" means priority, not animpactvalue. - For savings priorities, use
category: "Cost". Top retirements use prioritized summary, not list, withsub-category: "ServiceUpgradeAndRetirement"andretirement-date: "le:<yyyy-MM-dd>"for on-or-before cutoffs. - For drill-downs, preserve scope and filters; pass the selected recommendation-type group's actual GUID
keyas the sole entry in listrecommendation-type-ids. Retainprioritized: trueafter a prioritized summary and addcategory: "Cost"for a Cost type. Do not copy summarytopto list. - If broad priorities require
statusortracking-ids, explain that cross-type ranking is unavailable. Use filtered, non-prioritized list and explicitly label results unranked, not "top". Never silently drop unsupported constraints. - Present returned data in server ranking order; disclose errors and truncation. Never count a capped list or filter capped results to simulate a server-side date query.
"Top actions" and "what should I fix first?" ask for prioritization advice, not permission to remediate.
Safety
Ask for and wait for user confirmation before recommendation-state updates. The actionability skill owns remediation safeguards. On every model, visibly present results/proposals before dependent questions. Missing data stays Unavailable, not zero.