Generated banner for Azure Diagnostics
Generated logo for Azure Diagnostics

Azure Diagnostics

MicrosoftOfficialCreated by Microsoft

  • Skill
  • Workflow
  • Cloud and DevOps
  • MIT
  • Low risk
  • Has scripts

From the author

Debug Azure production issues using AppLens, Azure Monitor, resource health, and safe triage, including evidence-only diagnosis without live access. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, 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, lock renewal during long-running processing, service bus dead letter.
— the description by Microsoft

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

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/microsoft/azure-diagnostics/download
  2. Unzip 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

  1. Start with systematic diagnosis flow

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

  3. Use AppLens (MCP) for AI-powered diagnostics when available

  4. Check resource health before deep-diving into logs

  5. Select appropriate troubleshooting guide based on service type

  6. Document findings and attempted remediation steps

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

  8. Route AKS incidents to the dedicated AKS troubleshooting document

  9. Keep baseline AKS diagnostics available even when the optional aks-skills add-on is absent, declined, or unsupported by the host


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

ServiceCommon IssuesReference
Container AppsImage pull failures, cold starts, health probes, port mismatchescontainer-apps/
App ServiceHigh CPU, deployment failures, crashes, slow responses, TLS/custom domainsapp-service/
Function AppsApp details, invocation failures, timeouts, binding errors, cold starts, missing app settingsfunctions/
AKSCluster access, nodes, kube-system, scheduling, crash loops, ingress, DNS, upgradesAKS Troubleshooting
ComputeVM RDP/SSH connectivity, NSG/firewall blocks, credential resets, VM agent/tooling issuesVM Connectivity Troubleshooting
MessagingEvent Hubs & Service Bus SDK errors, AMQP failures, message lock, connectivityMessaging 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

Files

scripts/pod-evidence.ps1

<#
.SYNOPSIS
    Collects the invariant, read-only AKS pod-failure evidence bundle and prints a
    single labeled digest.
.DESCRIPTION
    Gathers the same evidence bundle for one or more pods regardless of the symptom
    (CrashLoopBackOff, OOMKilled, Pending, probe failures, ImagePullBackOff). For each
    pod it collects 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 stays with the caller.
.PARAMETER Pod
    Pod name (single-pod mode). Omit when using -AllFailing.
.PARAMETER Namespace
    Namespace of the pod. Required in single-pod mode. In -AllFailing mode, limits the
    scan to this namespace.
.PARAMETER AllFailing
    Auto-select every pod not in Running/Succeeded phase (across all namespaces unless
    -Namespace is given) and digest each.
.PARAMETER Tail
    Number of log lines to show per stream. Default 50.
.EXAMPLE
    .\pod-evidence.ps1 my-api-7d9f-abcde -Namespace prod
.EXAMPLE
    .\pod-evidence.ps1 -AllFailing
.EXAMPLE
    .\pod-evidence.ps1 -AllFailing -Namespace prod -Tail 100
#>
param(
    [Parameter(Position = 0)][string]$Pod,
    [Alias("n")][string]$Namespace,
    [switch]$AllFailing,
    [int]$Tail = 50
)

# Best-effort: individual kubectl reads may fail (unreachable cluster, missing
# metrics-server, no previous logs). PowerShell's default $ErrorActionPreference is
# "Continue", so a single failed read is suppressed via 2>$null and the digest proceeds
# instead of aborting — no explicit assignment needed.

if (-not (Get-Command kubectl -ErrorAction SilentlyContinue)) {
    Write-Error "kubectl not found on PATH."
    exit 1
}

if ($Tail -le 0) {
    Write-Error "-Tail must be a positive integer (got '$Tail')."
    exit 2
}

function Digest-Pod {
    param([string]$Ns, [string]$Name)

    Write-Host "=================================================================="
    Write-Host "POD: $Name   NAMESPACE: $Ns"
    Write-Host "=================================================================="

    Write-Host "--- STATUS (ready / phase / restarts) ---"
    $status = kubectl get pod $Name -n $Ns -o wide 2>&1
    if ($LASTEXITCODE -eq 0 -and $status) { $status | ForEach-Object { Write-Host "$_" } } else { Write-Host "(unable to get pod)" }
    Write-Host ""

    Write-Host "--- STATE (exit code / reason / last state) ---"
    $jp = '{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}'
    $state = kubectl get pod $Name -n $Ns -o jsonpath=$jp 2>$null
    if ($state) { Write-Host $state } else { Write-Host "(no container status available)" }
    Write-Host ""

    Write-Host "--- EVENTS ---"
    $desc = kubectl describe pod $Name -n $Ns 2>$null
    if ($desc) {
        $idx = ($desc | Select-String -Pattern '^Events:' | Select-Object -First 1).LineNumber
        if ($idx) {
            $desc | Select-Object -Skip ($idx - 1) | Select-Object -First 25 | ForEach-Object { Write-Host "$_" }
        } else {
            Write-Host "(no Events section)"
        }
    } else {
        Write-Host "(unable to describe pod)"
    }
    Write-Host ""

    Write-Host "--- LOGS (current, last $Tail lines) ---"
    $logs = kubectl logs $Name -n $Ns --tail=$Tail 2>&1
    if ($logs) { $logs | ForEach-Object { Write-Host "$_" } } else { Write-Host "(no current logs)" }
    Write-Host ""

    Write-Host "--- PREV LOGS (previous instance, last $Tail lines) ---"
    $prev = kubectl logs $Name -n $Ns --previous --tail=$Tail 2>$null
    if ($LASTEXITCODE -eq 0 -and $prev) {
        Write-Host $prev
    } else {
        Write-Host "(no previous-instance logs - pod has not restarted or they were rotated)"
    }
    Write-Host ""

    Write-Host "--- RESOURCES (requests/limits vs live usage) ---"
    Write-Host "requests/limits:"
    $res = kubectl get pod $Name -n $Ns -o jsonpath='{range .spec.containers[*]}  {.name}: requests={.resources.requests} limits={.resources.limits}{"`n"}{end}' 2>$null
    if ($res) { Write-Host $res } else { Write-Host "  (unable to read resources)" }
    Write-Host "live usage:"
    $top = kubectl top pod $Name -n $Ns 2>&1
    if ($top) { $top | ForEach-Object { Write-Host "  $_" } } else { Write-Host "  (metrics-server unavailable)" }
    Write-Host ""
}

if ($AllFailing) {
    $scope = if ($Namespace) { " in namespace '$Namespace'" } else { "" }
    Write-Host "pod-evidence: scanning for pods not in Running/Succeeded$scope..."

    $cols = "custom-columns=NS:.metadata.namespace,NAME:.metadata.name"
    if ($Namespace) {
        $rows = kubectl get pods -n $Namespace --field-selector=status.phase!=Running,status.phase!=Succeeded --no-headers -o $cols 2>$null
    } else {
        $rows = kubectl get pods -A --field-selector=status.phase!=Running,status.phase!=Succeeded --no-headers -o $cols 2>$null
    }

    $rows = @($rows | Where-Object { $_ -and $_.Trim() })
    if ($rows.Count -eq 0) {
        Write-Host "No unhealthy pods found (all pods are Running or Succeeded)."
        exit 0
    }

    Write-Host "Found $($rows.Count) unhealthy pod(s). Collecting evidence for each below."
    Write-Host ""
    foreach ($row in $rows) {
        $parts = ($row -split '\s+') | Where-Object { $_ }
        Digest-Pod -Ns $parts[0] -Name $parts[1]
    }
    Write-Host "pod-evidence: done. Reviewed $($rows.Count) failing pod(s) - use the STATE/EVENTS/LOGS above to pick a fix."
} else {
    if (-not $Pod) {
        Write-Error "A pod name is required (or use -AllFailing)."
        exit 2
    }
    if (-not $Namespace) {
        Write-Error "-Namespace is required in single-pod mode."
        exit 2
    }
    Write-Host "pod-evidence: collecting the read-only evidence bundle for pod '$Pod' in namespace '$Namespace'."
    Write-Host ""
    Digest-Pod -Ns $Namespace -Name $Pod
    Write-Host "pod-evidence: done. Use the STATE/EVENTS/LOGS/RESOURCES digest above to pick a fix."
}

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