Azure Diagnostics
- 482k installs
- 1.3k repo stars
- Updated July 26, 2026
- microsoft/azure-skills
azure-diagnostics is an agent skill that systematically debugs and resolves production issues across Azure services using AppLens, Azure Monitor, and KQL.
About
azure-diagnostics is a Claude Code skill for debugging production issues on Microsoft Azure. It provides systematic triage across App Service, Container Apps, Azure Functions, AKS, Event Hubs, and Service Bus, using AppLens, Azure Monitor, resource-health checks, and KQL log analysis. It follows a fixed diagnosis flow (identify symptoms, check resource health, review logs, analyze metrics, investigate recent changes) and routes AKS and messaging incidents to dedicated troubleshooting guides. Developers reach for it when a live Azure workload fails and root cause must follow official Microsoft guidance instead of ad-hoc log grepping.
- Systematic diagnosis of live Azure production issues
- Covers App Service, Container Apps, Functions, AKS, messaging
- Uses AppLens, Azure Monitor, resource health, and KQL
- Routes AKS and messaging incidents to dedicated guides
Azure Diagnostics by the numbers
- 482,259 all-time installs (skills.sh)
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
azure-diagnostics capabilities & compatibility
Free skill; requires a paid Azure subscription and configured monitoring.
- Capabilities
- azure troubleshooting · log analysis · root cause analysis · resource health check · aks diagnostics
- Works with
- azure · kubernetes
- Use cases
- debugging · devops
- Runs
- Runs locally
- Pricing
- Bring your own API key
What azure-diagnostics says it does
Use AppLens (MCP) for AI-powered diagnostics when available
Check resource health before deep-diving into logs
npx skills add https://github.com/microsoft/azure-skills --skill azure-diagnosticsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 482k |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 26, 2026 |
| Repository | microsoft/azure-skills ↗ |
Why is my Azure resource failing in production and how do I find the root cause systematically?
debugging
Who is it for?
Developers troubleshooting failing Azure App Service, Container Apps, Functions, AKS, or messaging workloads in production.
Skip if: Deploying or preparing apps; it diagnoses running workloads, not deployments (use azure-deploy for shipping).
When should I use this skill?
Use to debug production issues, troubleshoot App Service high CPU, deployment failures, AKS pod crashes, cold starts, or Event Hubs/Service Bus errors.
What you get
A root-cause diagnosis with documented findings and remediation steps following official Microsoft guidance.
- root-cause diagnosis and documented remediation steps
By the numbers
- 5-step quick diagnosis flow
- Covers 5 service families (App Service, Container Apps, Functions, AKS, messaging)
Files
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 Messaging SDK issues (Event Hubs, Service Bus connection failures, AMQP errors, message lock issues)
Rules
1. Start with systematic diagnosis flow 2. Use AppLens (MCP) for AI-powered diagnostics when available 3. Check resource health before deep-diving into logs 4. Select appropriate troubleshooting guide based on service type 5. Document findings and attempted remediation steps 6. Route AKS incidents to the dedicated AKS troubleshooting document
---
Quick Diagnosis Flow
1. Identify symptoms - What's failing? 2. Check resource health - Is Azure healthy? 3. Review logs - What do logs show? 4. Analyze metrics - Performance patterns? 5. 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 |
| Messaging | Event Hubs & Service Bus SDK errors, AMQP failures, message lock, connectivity | Messaging Troubleshooting |
---
Routing
- Keep Container Apps and Function Apps diagnostics in this parent skill.
- Route active AKS incidents, AKS-specific intake, evidence gathering, and remediation guidance to AKS Troubleshooting.
- Route Azure Messaging SDK troubleshooting (Event Hubs, Service Bus) to Messaging Troubleshooting.
---
Quick Reference
Common Diagnostic Commands
# Check resource health
az resource show --ids RESOURGuides
- Azure Skills for Claude Code: The Complete Guide to microsoft/azure-skills
microsoft/azure-skills is Microsoft's official repo of 27 Azure skills for Claude Code, covering deploy, AKS, diagnostics, compliance, cost, and Azure AI Foundry. Combined they have 9,775,059 installs, with microsoft-foundry alone at 446,557 installs (skills.sh registry, July 2026). This guide maps every skill to the Azure job it does.
Related skills
Azure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.467k1.3k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k72
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.248k190k
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.202k262k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.176k512
Sentry CliCapture errors, upload source maps, manage releases, and query events directly from the terminal or CI without leaving their workflow.114kFAQ
Which Azure services does azure-diagnostics cover?
App Service, Container Apps, Azure Functions, AKS, and messaging (Event Hubs and Service Bus), each with a dedicated troubleshooting guide.
What tools does it use?
AppLens for AI-powered diagnostics, Azure Monitor and KQL for logs and metrics, and resource-health checks, preferring Azure MCP tools when available.
What is its diagnosis order?
Identify symptoms, check resource health, review logs, analyze metrics, then investigate recent changes.
Is Azure Diagnostics safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.