azure-diagnostics

Name: azure-diagnostics
Author: microsoft

Safely diagnose Azure production issues across apps, containers, and messaging services.

Stars

★ 232

Source

GitHub

Updated

2026-07-13

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 232

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "azure-diagnostics" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/GitHub-Copilot-for-Azure/main/plugin/skills/azure-diagnostics/SKILL.md
2. Save it as ~/.claude/skills/azure-diagnostics/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Troubleshoot App Service high CPU

Prompt

Help me troubleshoot consistently high CPU in an Azure App Service production environment. Provide safe triage steps using AppLens, Azure Monitor, and Resource Health first, and explain which metrics, logs, likely root causes, and narrowing steps to use.

Expected

A safe production troubleshooting workflow with key metrics, log query directions, common root causes, and next-step recommendations.

Troubleshoot AKS pod startup failure

Prompt

Help troubleshoot an AKS issue where pods stay Pending or enter CrashLoopBackOff. Consider kube-system or CoreDNS failures, NotReady nodes, image pull failures, and health probe failures, and provide prioritized investigation steps.

Expected

A prioritized AKS troubleshooting checklist covering kubectl checks, cluster component health, event logs, and possible remediation paths.

Troubleshoot Service Bus message issues

Prompt

Help analyze Azure Service Bus message processing failures, focusing on AMQP connection failures, message lock lost errors, dead-letter queue growth, and SDK exceptions. Include likely root causes, logs and metrics to inspect, and a troubleshooting order.

Expected

A structured messaging-service diagnosis with root-cause hypotheses, key monitoring signals, and troubleshooting steps for each symptom.

// docs

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

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
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 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