azure-usage_skill

Overview

This skill lets you inspect and manage Azure resources through an MCP-backed interface. It exposes common resource operations like listing storage accounts, reading Key Vault secrets, querying Cosmos DB, and checking AKS clusters. The skill is optimized for interactive queries and scripted automation workflows.

How this skill works

The skill calls Azure MCP tool endpoints that map to resource operations (list, get, create, query). It authenticates via Azure Identity (az login, VS Code auth, or environment service principal) and routes requests to specific MCP commands such as storage_accounts_list, keyvault_secrets_get, cosmosdb_query, and aks_clusters_list. Results are returned as structured data for further processing or display.

When to use it

• You need an inventory of Azure resources across subscriptions or resource groups.
• You want to read or update Key Vault secrets securely via automation.
• You need to list or upload blobs, or examine storage account contents.
• You want to run ad-hoc queries against Cosmos DB or Log Analytics.
• You need to inspect AKS clusters and node pools before deployments.

Best practices

• Authenticate with az login or a managed identity to avoid secret sprawl.
• Prefer list/get/query commands rather than broad create/delete unless needed; follow least-privilege principles.
• Paginate large result sets and use filters to reduce API load and cost.
• Use Key Vault operations for secret management and avoid embedding secrets in code or chat logs.
• Validate results in a staging subscription or resource group before applying changes in production.

Example use cases

• List all storage accounts in a subscription and inspect attached containers and blobs.
• Retrieve a Key Vault secret value for a deployment pipeline or rotate a secret programmatically.
• Run a Cosmos DB SQL query to find documents matching a production issue.
• Query Log Analytics for recent errors using monitor_logs_query and export results for analysis.
• List AKS clusters and node pools to validate cluster capacity before scaling operations.