Azure Diagnostics
OfficialFreeStreamline Azure production issue troubleshooting.
Free · Opens the source repo
What Azure Diagnostics does
Azure Diagnostics is a comprehensive skill designed to assist developers and IT professionals in diagnosing and troubleshooting production issues within Azure environments. This skill provides a systematic approach to resolving common Azure service problems, leveraging tools such as AppLens, Azure Monitor, and resource health checks. It is particularly useful for those managing applications hosted on Azure, including App Services, Azure Functions, and Kubernetes clusters (AKS). The skill guides users through a structured diagnosis flow, enabling them to identify symptoms, check resource health, review logs, analyze metrics, and investigate recent changes systematically.
The skill encompasses a variety of troubleshooting scenarios, including high CPU usage in App Services, deployment failures, invocation timeouts in Azure Functions, and connectivity issues with Azure VMs. It also addresses challenges specific to containerized applications and messaging services, such as image pull failures and AMQP connection errors. By following the provided troubleshooting guides, users can quickly pinpoint issues and apply the recommended remediation steps, reducing downtime and improving overall service reliability.
Developers and operations teams will find Azure Diagnostics particularly beneficial for maintaining the health and performance of their Azure-hosted applications. The skill not only helps in diagnosing issues but also encourages best practices in documentation and evidence gathering, which are essential for effective incident management. With its focus on systematic troubleshooting and clear guidance, Azure Diagnostics is an essential tool for anyone involved in managing Azure resources and services.
When to use it
Use this skill when you need to troubleshoot Azure services, analyze logs, or diagnose connectivity issues in production environments.
When not to use it
This skill may not be suitable for non-Azure environments or for issues unrelated to Azure services.
What you can build with it
Troubleshooting App Service High CPU
When an App Service experiences high CPU usage, use this skill to diagnose the issue by checking resource health and reviewing application logs.
Resolving Azure Function Invocation Failures
If Azure Functions are failing to invoke, this skill provides guidance on analyzing invocation logs and identifying missing app settings.
Diagnosing AKS Cluster Issues
For issues related to AKS clusters, such as pod failures or networking issues, follow the dedicated troubleshooting guides included in this skill.
How to install Azure Diagnostics
View source1. Install with the skills CLI
npx skills add microsoft/azure-skills/azure-diagnostics --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by microsoftAzure 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 |
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 VM RDP/SSH connectivity, NSG/firewall, credential reset, and VM agent troubleshooting to VM Connectivity 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 RESOURCE_ID
# View activity log
az monitor activity-log list -g RG --max-events 20
# Container Apps logs
az containerapp logs show --name APP -g RG --follow
# Function App logs (query App Insights traces)
az monitor app-insights query --apps APP-INSIGHTS -g RG \
--analytics-query "traces | where timestamp > ago(1h) | order by timestamp desc | take 50"
AppLens (MCP Tools)
For AI-powered diagnostics, use:
mcp_azure_mcp_applens
intent: "diagnose issues with <resource-name>"
command: "diagnose"
parameters:
resourceId: "<resource-id>"
Provides:
- Automated issue detection
- Root cause analysis
- Remediation recommendations
Azure Monitor (MCP Tools)
For querying logs and metrics:
mcp_azure_mcp_monitor
intent: "query logs for <resource-name>"
command: "logs_query"
parameters:
workspaceId: "<workspace-id>"
query: "<KQL-query>"
See kql-queries.md for common diagnostic queries.
Check Azure Resource Health
Using MCP
mcp_azure_mcp_resourcehealth
intent: "check health status of <resource-name>"
command: "get"
parameters:
resourceId: "<resource-id>"
Using CLI
# Check specific resource health
az resource show --ids RESOURCE_ID
# Check recent activity
az monitor activity-log list -g RG --max-events 20
References
Frequently asked questions about Azure Diagnostics
Similar skills
Agent Host Debug Logs
Analyze Agent Host debug logs for deeper insights.
Code OSS Dev - Launch + Debug
Launch and debug Code OSS with isolated profiles.
Phoenix CLI
Debug LLM applications with structured analysis tools.
Power Automate Debugging
Diagnose and fix Power Automate flow errors effectively.
Arize Trace
Inspect and export traces for LLM applications.
Runtime Behavior Probe
Investigate real runtime behavior with precision.