Azure Skills Plugin is an agent plugin that packages Azure-specific guidance with MCP server configurations for carrying out Azure work. Coding agents use it to plan, deploy, troubleshoot, monitor, govern, and optimize Azure applications and services. The catalogue entries are the plugin's skills, instructions, and execution integrations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add microsoft/azure-skills --skill azure-diagnosticsgit clone --depth 1 https://github.com/microsoft/azure-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/microsoft/azure-skills/azure-diagnostics)<a href="https://agentmods.dev/skills/microsoft/azure-skills/azure-diagnostics"><img src="https://agentmods.dev/badge/skills/microsoft/azure-skills/azure-diagnostics.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00160 | $0.01439 |
| Opus 5 | $0.00080 | $0.00720 |
| Sonnet 5 | $0.00032 | $0.00288 |
| Haiku 4.5 | $0.00016 | $0.00144 |
Grade A, and why
azure-diagnostics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to azure-diagnostics — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Diagnostics
AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
This document is the official source for debugging and troubleshooting Azure production issues. Follow these instructions to diagnose and resolve common Azure service problems systematically.
Triggers
Activate this skill when user wants to:
- Debug or troubleshoot production issues
- Diagnose errors in Azure services
- Analyze application logs or metrics
- Fix image pull, cold start, or health probe issues
- Investigate why Azure resources are failing
- Find root cause of application errors
- Troubleshoot App Service issues (high CPU, deployment failures, crashes, slow responses, TLS/custom domains)
- Respond to prompts like "troubleshoot app service", "app service high CPU", or "app service deployment failure"
- Troubleshoot Azure Function Apps (invocation failures, timeouts, binding errors)
- Find the App Insights or Log Analytics workspace linked to a Function App
- Troubleshoot AKS clusters, nodes, pods, ingress, or Kubernetes networking issues
- Troubleshoot Azure VM connectivity issues (RDP/SSH failures, port 3389/22 timeouts, NSG or firewall blocking, credential resets)
- Troubleshoot Azure Messaging SDK issues (Event Hubs, Service Bus connection failures, AMQP errors, message lock issues)
Rules
- Start with systematic diagnosis flow
- Use AppLens (MCP) for AI-powered diagnostics when available
- Check resource health before deep-diving into logs
- Select appropriate troubleshooting guide based on service type
- Document findings and attempted remediation steps
- Route AKS incidents to the dedicated AKS troubleshooting document
Quick Diagnosis Flow
- Identify symptoms - What's failing?
- Check resource health - Is Azure healthy?
- Review logs - What do logs show?
- Analyze metrics - Performance patterns?
- Investigate recent changes - What changed?
Troubleshooting Guides by Service
| Service | Common Issues | Reference |
|---|---|---|
| Container Apps | Image pull failures, cold starts, health probes, port mismatches | container-apps/ |
| App Service | High CPU, deployment failures, crashes, slow responses, TLS/custom domains | app-service/ |
| Function Apps | App details, invocation failures, timeouts, binding errors, cold starts, missing app settings | functions/ |
| AKS | Cluster access, nodes, kube-system, scheduling, crash loops, ingress, DNS, upgrades |
AKS Troubleshooting |
| Compute | VM RDP/SSH connectivity, NSG/firewall blocks, credential resets, VM agent/tooling issues | VM Connectivity Troubleshooting |
| Messaging | Event Hubs & Service Bus SDK errors, AMQP failures, message lock, connectivity | Messaging Troubleshooting |
What ships with it
50 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/app-service/README.md 7.2 KB
- references/azure-resource-graph.md 2.9 KB
- references/container-apps/README.md 2.9 KB
- references/functions/README.md 3.5 KB
- references/kql-queries.md 1.3 KB
- scripts/aks-baseline.ps1 7.0 KB runs code
- scripts/aks-baseline.sh 6.7 KB runs code
- scripts/appservice-diagnostics.ps1 2.3 KB runs code
- scripts/appservice-diagnostics.sh 2.9 KB runs code
- scripts/containerapp-diagnostics.ps1 2.1 KB runs code
- scripts/containerapp-diagnostics.sh 2.7 KB runs code
- scripts/pod-evidence.ps1 6.6 KB runs code
- scripts/pod-evidence.sh 7.1 KB runs code
- scripts/run-ig.ps1 5.6 KB runs code
- scripts/run-ig.sh 6.5 KB runs code
- scripts/test-messaging-connectivity.ps1 6.3 KB runs code
- scripts/test-messaging-connectivity.sh 6.8 KB runs code
- troubleshooting/aks/aks-troubleshooting.md 6.2 KB
- troubleshooting/aks/general-diagnostics.md 2.0 KB
- troubleshooting/aks/load-balancer-and-ingress.md 3.6 KB
- troubleshooting/aks/network-policy.md 832 B
- troubleshooting/aks/networking.md 5.5 KB
- troubleshooting/aks/node-issues.md 4.7 KB
- troubleshooting/aks/pod-failures.md 7.6 KB
- troubleshooting/aks/references/aks-mcp.md 1.5 KB
- troubleshooting/aks/references/command-flows.md 4.0 KB
- troubleshooting/aks/references/inspektor-gadget.md 7.6 KB
- troubleshooting/aks/references/structured-input-modes.md 1.5 KB
- troubleshooting/aks/spot-and-zone-issues.md 2.5 KB
- troubleshooting/aks/upgrade-operations.md 2.2 KB
- troubleshooting/compute/references/cannot-connect-to-vm.md 3.1 KB
- troubleshooting/compute/references/credential-auth-errors.md 2.3 KB
- troubleshooting/compute/references/firewall-blocking.md 2.3 KB
- troubleshooting/compute/references/network-connectivity.md 2.5 KB
- troubleshooting/compute/references/rdp-connectivity.md 2.7 KB
- troubleshooting/compute/references/rdp-service-config.md 3.2 KB
- troubleshooting/compute/references/ssh-connectivity.md 2.1 KB
- troubleshooting/compute/references/vm-agent-not-responding.md 3.6 KB
- troubleshooting/compute/vm-troubleshooting.md 3.3 KB
- troubleshooting/messaging/auth-best-practices.md 6.1 KB
- troubleshooting/messaging/azure-eventhubs-dotnet.md 3.5 KB
- troubleshooting/messaging/azure-eventhubs-java.md 3.2 KB
- troubleshooting/messaging/azure-eventhubs-js.md 2.7 KB
- troubleshooting/messaging/azure-eventhubs-py.md 4.3 KB
- troubleshooting/messaging/azure-servicebus-dotnet.md 2.5 KB
- troubleshooting/messaging/azure-servicebus-java.md 2.2 KB
- troubleshooting/messaging/azure-servicebus-js.md 2.4 KB
- troubleshooting/messaging/azure-servicebus-py.md 2.3 KB
- troubleshooting/messaging/README.md 1.6 KB
- troubleshooting/messaging/service-troubleshooting.md 5.1 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 156 lines · 160 tokens per session scan A 513f4aae9d13
azure-diagnostics is a skill published in the GitHub repository microsoft/azure-skills (1,459 stars, last pushed yesterday), licensed MIT. It adds 160 tokens to every session and 1,439 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to azure-diagnostics, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-handle-disruption-gpu-tpu
Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.