Azure Diagnostics
MicrosoftOfficialCreated by Microsoft
- Skill
- Workflow
- Cloud and DevOps
- MIT
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Azure Diagnostics provides a structured, authoritative approach to investigating and resolving production issues across various Azure services. It emphasizes a systematic flow: identifying symptoms, checking resource health, reviewing logs, analyzing metrics, and investigating recent changes. The skill supports both live troubleshooting via Azure CLI and AppLens, as well as evidence-only analysis when live access is restricted. It includes specialized guidance for App Service, Container Apps, Azure Functions, AKS, VMs, and Messaging services, ensuring consistent root-cause analysis.
What it does
- Provides a standardized diagnostic workflow for Azure production environments.
- Integrates with AppLens and Azure Monitor for automated issue detection and log analysis.
- Offers service-specific troubleshooting paths for App Service, AKS, VMs, and more.
- Supports evidence-only diagnosis for secure, offline troubleshooting scenarios.
- Includes KQL query patterns for deep-dive log and resource health analysis.
- Facilitates the use of bundled diagnostic scripts for efficient data collection.
When to use it
- When investigating production incidents like high CPU, deployment failures, or service crashes.
- When troubleshooting connectivity issues such as RDP/SSH failures or network blocking.
- When diagnosing Kubernetes-specific issues like pod crashloops or image pull failures.
- When analyzing missing telemetry or messaging errors in Event Hubs and Service Bus.
- When performing root-cause analysis on unhealthy or degraded Azure resources.
Advantages
- Reduces mean time to resolution (MTTR) with a clear, step-by-step diagnostic process.
- Ensures consistent troubleshooting practices across different Azure service types.
- Supports secure workflows by allowing diagnosis without requiring live environment access.
- Leverages powerful built-in tools like AppLens and Azure Resource Graph for rapid insights.
- Provides actionable remediation steps based on identified symptoms.
Usage examples
- “Troubleshoot my App Service that is experiencing high CPU usage.”
- The agent will initiate the App Service diagnostic flow, run the appservice-diagnostics script, check metrics, and guide you through profiling via Kudu.
- “Why is my Azure VM unreachable via SSH?”
- The agent will follow the VM connectivity troubleshooting guide, checking NSG rules, firewall status, and VM agent health.
- “Analyze these logs to find why my Container App is failing to pull the image.”
- The agent will perform an evidence-only analysis of the provided logs to identify image pull errors or registry authentication issues.
- “Check the health of my AKS cluster and identify why pods are in a crashloop.”
- The agent will check resource health, query logs for the affected pods, and route to the AKS-specific troubleshooting documentation.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/microsoft/azure-diagnostics/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip azure-diagnostics.zip -d .agents/skills
Documentation by Microsoft
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)
Root-cause a symptom that looks like a healthy-runtime-but-wrong-destination problem (e.g., telemetry/messages stop flowing to the expected resource after a config change) — invoke this skill for the matrix even when MCP tools could answer the surface question alone
Rules
Start with systematic diagnosis flow
Use supplied evidence first. If the user requests evidence-only analysis or prohibits live Azure access, do not query or modify Azure. Diagnose from the supplied logs, metrics, and timeline; identify assumptions and provide optional verification steps.
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
Prefer bundled diagnostic scripts over ad hoc calls for permitted live collection when identifiers are known. If supplied evidence suffices or live access is prohibited, don't run them; otherwise run the applicable script first.
Route AKS incidents to the dedicated AKS troubleshooting document
Keep baseline AKS diagnostics available even when the optional
aks-skillsadd-on is absent, declined, or unsupported by the host
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 recommendationsAzure 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 20References
Files
- ATTRIBUTION.mdAdded by AutoGineer983 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md7.3 KiB
- references/app-service/README.md7.8 KiB
- references/azure-resource-graph.md2.8 KiB
- references/container-apps/README.md3.5 KiB
- references/functions/README.md3.9 KiB
- references/functions/durable.md7.6 KiB
- references/functions/triggers.md8.3 KiB
- references/kql-queries.md1.3 KiB
- scripts/aks-baseline.ps1Script7.4 KiB
- scripts/aks-baseline.shScript7.0 KiB
- scripts/appservice-diagnostics.ps1Script2.7 KiB
- scripts/appservice-diagnostics.shScript3.3 KiB
- scripts/containerapp-diagnostics.ps1Script2.5 KiB
- scripts/containerapp-diagnostics.shScript3.1 KiB
- scripts/pod-evidence.ps1Script6.6 KiB
- scripts/pod-evidence.shScript7.1 KiB
- scripts/run-ig.ps1Script5.6 KiB
- scripts/run-ig.shScript6.5 KiB
- scripts/test-messaging-connectivity.ps1Script6.3 KiB
- scripts/test-messaging-connectivity.shScript6.8 KiB
- troubleshooting/aks/aks-troubleshooting.md9.2 KiB
- troubleshooting/aks/general-diagnostics.md2.0 KiB
- troubleshooting/aks/load-balancer-and-ingress.md3.6 KiB
- troubleshooting/aks/network-policy.md832 B
- troubleshooting/aks/networking.md5.5 KiB
- troubleshooting/aks/node-issues.md4.7 KiB
- troubleshooting/aks/optional-aks-operations.md2.3 KiB
- troubleshooting/aks/pod-failures.md7.6 KiB
- troubleshooting/aks/references/aks-mcp.md2.3 KiB
- troubleshooting/aks/references/command-flows.md4.1 KiB
- troubleshooting/aks/references/inspektor-gadget.md7.6 KiB
- troubleshooting/aks/references/structured-input-modes.md1.5 KiB
- troubleshooting/aks/spot-and-zone-issues.md2.5 KiB
- troubleshooting/aks/upgrade-operations.md2.2 KiB
- troubleshooting/compute/references/cannot-connect-to-vm.md3.1 KiB
- troubleshooting/compute/references/credential-auth-errors.md2.3 KiB
- troubleshooting/compute/references/firewall-blocking.md2.3 KiB
- troubleshooting/compute/references/network-connectivity.md2.5 KiB
- troubleshooting/compute/references/rdp-connectivity.md2.7 KiB
- troubleshooting/compute/references/rdp-service-config.md3.2 KiB
- troubleshooting/compute/references/ssh-connectivity.md2.9 KiB
- troubleshooting/compute/references/vm-agent-not-responding.md3.6 KiB
- troubleshooting/compute/vm-troubleshooting.md3.3 KiB
- troubleshooting/messaging/README.md1.6 KiB
- troubleshooting/messaging/auth-best-practices.md6.1 KiB
- troubleshooting/messaging/azure-eventhubs-dotnet.md3.5 KiB
- troubleshooting/messaging/azure-eventhubs-java.md3.2 KiB
- troubleshooting/messaging/azure-eventhubs-js.md2.7 KiB
- troubleshooting/messaging/azure-eventhubs-py.md4.3 KiB
- troubleshooting/messaging/azure-servicebus-dotnet.md2.5 KiB
- troubleshooting/messaging/azure-servicebus-java.md2.2 KiB
- troubleshooting/messaging/azure-servicebus-js.md2.4 KiB
- troubleshooting/messaging/azure-servicebus-py.md2.3 KiB
- troubleshooting/messaging/service-troubleshooting.md5.1 KiB
scripts/pod-evidence.sh
#!/usr/bin/env bash
# pod-evidence.sh
# Collects the invariant, read-only AKS pod-failure evidence bundle for one or more
# pods and prints a single labeled digest. Works identically regardless of the pod
# symptom (CrashLoopBackOff, OOMKilled, Pending, probe failures, ImagePullBackOff).
#
# For each pod it gathers and summarizes:
# STATUS - READY / phase / restart count (kubectl get pod -o wide)
# STATE - exit code, reason, last-state snippet (jsonpath over containerStatuses)
# EVENTS - the Events section (kubectl describe pod)
# LOGS - current container logs (tailed) (kubectl logs)
# PREV LOGS - previous/crashed container logs (tailed)(kubectl logs --previous)
# RESOURCES - requests/limits vs live usage (jsonpath + kubectl top pod)
#
# This script only GATHERS and DIGESTS evidence. It never mutates cluster state.
# Interpreting the digest to pick a fix (exit-code / event / probe decision tables)
# stays with the caller.
#
# Usage:
# ./pod-evidence.sh <pod> -n <namespace> [--tail <n>]
# ./pod-evidence.sh --all-failing [-n <namespace>] [--tail <n>]
#
# Options:
# -n, --namespace <ns> Namespace of the pod. Required in single-pod mode.
# In --all-failing mode, limits the scan to this namespace.
# --all-failing Auto-select every pod not in Running/Succeeded phase
# (across all namespaces unless -n is given) and digest each.
# --tail <n> Number of log lines to show per stream (default 50).
# -h, --help Show this help.
#
# Examples:
# ./pod-evidence.sh my-api-7d9f-abcde -n prod
# ./pod-evidence.sh --all-failing
# ./pod-evidence.sh --all-failing -n prod --tail 100
set -euo pipefail
POD=""
NAMESPACE=""
ALL_FAILING=false
TAIL=50
usage() {
sed -n '2,40p' "$0" | sed 's/^# \{0,1\}//'
}
while [ $# -gt 0 ]; do
case "$1" in
-n|--namespace) NAMESPACE="${2:?--namespace requires a value}"; shift 2 ;;
--all-failing) ALL_FAILING=true; shift ;;
--tail) TAIL="${2:?--tail requires a value}"; shift 2 ;;
-h|--help) usage; exit 0 ;;
-*) echo "Unknown option: $1" >&2; usage; exit 2 ;;
*) POD="$1"; shift ;;
esac
done
if ! command -v kubectl >/dev/null 2>&1; then
echo "ERROR: kubectl not found on PATH." >&2
exit 1
fi
case "$TAIL" in
''|*[!0-9]*) echo "ERROR: --tail must be a positive integer (got '$TAIL')." >&2; exit 2 ;;
0) echo "ERROR: --tail must be a positive integer (got '$TAIL')." >&2; exit 2 ;;
esac
# Digest a single pod. Args: <namespace> <pod>
digest_pod() {
local ns="$1" pod="$2"
echo "=================================================================="
echo "POD: $pod NAMESPACE: $ns"
echo "=================================================================="
echo "--- STATUS (ready / phase / restarts) ---"
kubectl get pod "$pod" -n "$ns" -o wide 2>&1 || echo "(unable to get pod)"
echo ""
echo "--- STATE (exit code / reason / last state) ---"
kubectl get pod "$pod" -n "$ns" -o jsonpath='{range .status.containerStatuses[*]}container={.name}{"\n"} ready={.ready} restarts={.restartCount}{"\n"} current: waiting={.state.waiting.reason} running={.state.running.startedAt} terminated={.state.terminated.reason}(exit={.state.terminated.exitCode}){"\n"} lastState: terminated={.lastState.terminated.reason}(exit={.lastState.terminated.exitCode}) at {.lastState.terminated.finishedAt}{"\n"}{end}' 2>/dev/null \
|| echo "(no container status available)"
echo ""
echo "--- EVENTS ---"
if kubectl describe pod "$pod" -n "$ns" >/dev/null 2>&1; then
# Read the whole describe output in a single awk pass (no `head` in the pipe:
# an early-exiting `head` would SIGPIPE the upstream kubectl and, under
# `set -o pipefail`, abort the script). awk consumes all input and prints only
# the first 25 lines of the Events section.
kubectl describe pod "$pod" -n "$ns" 2>/dev/null | awk '/^Events:/{f=1} f && n<25 {print; n++}'
else
echo "(unable to describe pod)"
fi
echo ""
echo "--- LOGS (current, last $TAIL lines) ---"
kubectl logs "$pod" -n "$ns" --tail="$TAIL" 2>&1 || echo "(no current logs)"
echo ""
echo "--- PREV LOGS (previous instance, last $TAIL lines) ---"
if kubectl logs "$pod" -n "$ns" --previous --tail="$TAIL" 2>/dev/null; then
:
else
echo "(no previous-instance logs - pod has not restarted or they were rotated)"
fi
echo ""
echo "--- RESOURCES (requests/limits vs live usage) ---"
echo "requests/limits:"
kubectl get pod "$pod" -n "$ns" -o jsonpath='{range .spec.containers[*]} {.name}: requests={.resources.requests} limits={.resources.limits}{"\n"}{end}' 2>/dev/null \
|| echo " (unable to read resources)"
echo "live usage:"
kubectl top pod "$pod" -n "$ns" 2>&1 | sed 's/^/ /' || echo " (metrics-server unavailable)"
echo ""
}
if [ "$ALL_FAILING" = true ]; then
echo "pod-evidence: scanning for pods not in Running/Succeeded${NAMESPACE:+ in namespace '$NAMESPACE'}..."
# Portable, set -e-safe row collection: capture output + exit status via command
# substitution (not process substitution, whose failures don't propagate under set -e)
# so a failed scan is reported as an error instead of a misleading "no unhealthy pods".
# Avoids `mapfile`, which is unavailable in Bash 3.2 / macOS.
if [ -n "$NAMESPACE" ]; then
SCAN_ARGS=(-n "$NAMESPACE")
else
SCAN_ARGS=(-A)
fi
set +e
SCAN_OUT=$(kubectl get pods "${SCAN_ARGS[@]}" --field-selector=status.phase!=Running,status.phase!=Succeeded --no-headers -o custom-columns=NS:.metadata.namespace,NAME:.metadata.name 2>/dev/null)
SCAN_RC=$?
set -e
if [ "$SCAN_RC" -ne 0 ]; then
echo "ERROR: unable to list pods (kubectl exited $SCAN_RC). Check your cluster context and credentials." >&2
exit 1
fi
ROWS=()
while IFS= read -r line; do
[ -n "$line" ] && ROWS+=("$line")
done <<< "$SCAN_OUT"
if [ "${#ROWS[@]}" -eq 0 ]; then
echo "No unhealthy pods found (all pods are Running or Succeeded)."
exit 0
fi
echo "Found ${#ROWS[@]} unhealthy pod(s). Collecting evidence for each below."
echo ""
for row in "${ROWS[@]}"; do
[ -z "$row" ] && continue
ns="${row%% *}"
name="${row##* }"
digest_pod "$ns" "$name"
done
echo "pod-evidence: done. Reviewed ${#ROWS[@]} failing pod(s) - use the STATE/EVENTS/LOGS above to pick a fix."
else
if [ -z "$POD" ]; then
echo "ERROR: a pod name is required (or use --all-failing)." >&2
usage
exit 2
fi
if [ -z "$NAMESPACE" ]; then
echo "ERROR: -n/--namespace is required in single-pod mode." >&2
exit 2
fi
echo "pod-evidence: collecting the read-only evidence bundle for pod '$POD' in namespace '$NAMESPACE'."
echo ""
digest_pod "$NAMESPACE" "$POD"
echo "pod-evidence: done. Use the STATE/EVENTS/LOGS/RESOURCES digest above to pick a fix."
fi
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs a command-line tool
Security
What our scanner noticed· Low risk
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/skills · .github/plugins/azure-skills/skills/azure-diagnostics · commit 0696600
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- microsoft/azure-skills
AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-diagnostics.zip