🎯

azure-diagnostics

🎯Skill

Helps you find and fix problems in apps running on Azure, such as crashes, slow responses, or connection failures. It checks things in a set order and can work only from logs you provide.

microsoft/azure-skills701,113 Installs445Last Updated Mar 20, 2026

Installation

$npx skills add microsoft/azure-skills --skill azure-diagnostics

Run it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).

Uses skills.sh · Node.js 22.20+

After installing

Ask for related work and the agent uses it on its own, or call it yourself.

Run it (Claude Code)/azure-diagnostics

Install by hand

Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.

Open the skill folder →

This project .claude/skills/azure-diagnostics/
All projects ~/.claude/skills/azure-diagnostics/

These paths are for Claude Code. For other tools, the command above puts it in the right place.

📦Same repositorymicrosoft/azure-skills (51 items)

What this skill does

Overview

azure-diagnostics guides the AI through Azure problems in five steps: identify the symptoms, check resource health, review logs, analyze metrics, and look at recent changes. It can use AppLens and Azure Monitor, which are Microsoft tools that analyze resources and search logs. If you do not allow live access to Azure, it diagnoses only from the logs, metrics, and timeline you give it.

Key Features

Follow step-by-step guides for Container Apps, App Service, Function Apps, AKS (Azure's Kubernetes service for running containers), virtual machines, and Event Hubs or Service Bus.
Check whether Azure reports a problem with your resource before you dig into logs.
Search logs with ready-made KQL queries (KQL is the query language for Azure logs) and common az commands.
Fix VM connection problems such as failed remote logins (RDP or SSH), blocked ports, or the need to reset a password.
Get a diagnosis without the AI touching Azure, along with optional steps to confirm it.

Who is this for?

It is for developers and operators whose Azure app has high CPU, keeps crashing, cannot pull its container image, or stopped sending telemetry (monitoring data) after a config change. It also helps when you only have logs from an incident and cannot give the AI access to the live system.

Summarized by AI from this skill's SKILL.md. Suggest a better one

SKILL.md

View on GitHub →

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.

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

More from this repository10

🎯

microsoft-foundry🎯Skill

Helps you build, deploy, test, and manage AI agents and models on Microsoft Foundry, Microsoft's Azure service for AI. It guides the AI through each task with fixed steps.

🎯

azure-prepare🎯Skill

azure-prepare gets a new or existing app ready to deploy to Azure with azd, Microsoft's command-line tool for Azure. It first writes a plan for your approval, then creates the setup files.

🎯

azure-deploy🎯Skill

azure-deploy puts your app on Azure after the azure-prepare and azure-validate skills have prepared and checked it. It runs the deployment, recovers from errors, and gives you the live web addresses.

🎯

azure-validate🎯Skill

azure-validate checks your Azure app before you deploy it, so you can catch setup and permission problems early. It runs after azure-prepare and before azure-deploy.

🎯

azure-resource-lookup🎯Skill

azure-resource-lookup finds and lists your Azure resources, such as web apps, virtual machines, and storage accounts, across your subscriptions. It only reads data and never changes anything.

🎯

azure-resource-visualizer🎯Skill

azure-resource-visualizer draws a diagram of an Azure resource group that shows how each resource connects to the others. It saves the diagram and notes in a markdown file.

🎯

azure-kusto🎯Skill

Lets Claude search and summarize large amounts of logs and app data stored in Azure Data Explorer. You ask what you want to know, and it writes and runs the queries for you.

🎯

azure-aigateway🎯Skill

Helps you send all requests to your AI models and tools through Azure API Management, so you can control cost, block harmful content and limit traffic. It includes Azure command-line steps for setup and testing.

🎯

azure-messaging🎯Skill

Helps you find and fix errors in apps that send and receive messages through Azure Event Hubs or Service Bus. It checks service health and Microsoft docs to suggest a fix.

🎯

azure-compute🎯Skill

A helper that sends your Azure virtual machine requests to the right step-by-step guide. It helps you choose, price, create and reserve cloud servers in Azure.