azure-diagnostics
microsoft/azure-skills
Debug Azure production issues using AppLens, Azure Monitor, resource health, and systematic triage.
What is azure-diagnostics?
Diagnose and resolve Azure service failures across App Service, Functions, Container Apps, AKS, VMs, and Messaging services. Use this skill when troubleshooting production outages, performance issues, connectivity problems, or application errors in Azure.
- Systematic diagnosis flow: identify symptoms, check resource health, review logs, analyze metrics, investigate changes
- AppLens integration for AI-powered automated issue detection and root cause analysis
- Resource health checks and activity log analysis via Azure CLI and MCP tools
- Troubleshooting guides for App Service (CPU, deployments, crashes), Function Apps (invocation, timeouts, bindings), and Container Apps (image pull, cold starts, health probes)
- VM connectivity troubleshooting: RDP/SSH failures, NSG/firewall blocking, credential resets
- Messaging diagnostics: Event Hubs and Service Bus SDK errors, AMQP failures, message lock issues, dead letter analysis
How to install azure-diagnostics
npx skills add https://github.com/microsoft/azure-skills --skill azure-diagnostics- Azure CLI installed and authenticated
- Access to Azure subscription and resource groups being diagnosed
- App Insights or Log Analytics workspace linked to the service (for log queries)
- kubectl installed (for AKS troubleshooting)
How to use azure-diagnostics
- 1.Identify the failing Azure service and symptoms (e.g., high CPU, deployment failure, connectivity issue)
- 2.Check resource health using `az resource show` or the resourcehealth MCP tool
- 3.Select the appropriate troubleshooting guide from the service table (App Service, Functions, Container Apps, AKS, VM, or Messaging)
- 4.Use AppLens MCP tool with the resource ID for automated diagnostics and root cause analysis
- 5.Query logs and metrics using Azure Monitor MCP tool with KQL queries from the reference library
- 6.Document findings and remediation steps taken
Use cases
- Diagnose why an App Service is consuming high CPU or failing to deploy
- Investigate Function App invocation failures, timeouts, or cold start issues
- Troubleshoot Container Apps image pull failures or health probe mismatches
- Debug AKS cluster access, node failures, pod crash loops, or DNS issues
- Resolve VM connectivity problems: RDP/SSH timeouts, NSG rules blocking traffic, password resets
- Azure platform engineers and SREs
- DevOps and cloud operations teams
- Application developers troubleshooting production issues
- Infrastructure teams managing VMs, AKS, and networking
azure-diagnostics FAQ
Use it when debugging production issues in Azure services: App Service, Functions, Container Apps, AKS, VMs, Event Hubs, or Service Bus. Activate on prompts like 'troubleshoot app service high CPU' or 'diagnose function app timeout'.
AppLens is an MCP tool for AI-powered diagnostics. Call it with a resource ID and intent (e.g., 'diagnose issues with my-app') to get automated issue detection and remediation recommendations.
Use the Azure Monitor MCP tool with a KQL query and your Log Analytics workspace ID. Common diagnostic queries are provided in the kql-queries.md reference.
Route to the dedicated AKS Troubleshooting guide for cluster access, node failures, pod scheduling, crash loops, ingress, DNS, and upgrade issues.
Use the VM Connectivity Troubleshooting guide for RDP/SSH failures, NSG/firewall blocking, credential resets, and VM agent issues.
Full instructions (SKILL.md)
Source of truth, from microsoft/azure-skills.
name: azure-diagnostics description: "Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, service bus dead letter." license: MIT metadata: author: Microsoft version: "1.2.6"
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 |
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
Related skills
More from microsoft/azure-skills and the wider catalog.
