Official agent skill

Azure Diagnostics

by microsoft in microsoft/GitHub-Copilot-for-Azure

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.

OfficialMITAuto-check passedDevOps & Cloud

Install Azure Diagnostics

skills CLI
$ npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-diagnostics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microsoft/GitHub-Copilot-for-Azure azure-diagnostics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microsoft/GitHub-Copilot-for-Azure.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/azure-skills/skills/azure-diagnostics .claude/skills/azure-diagnostics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
azure-diagnostics
GitHub stars
255
Used in
1 other repo
Token cost
~1.6k tokens
SKILL.md length
447 words
Files
58 (incl. scripts, references)
Skills in repo
56
Repo updated
First seen
Licence
MIT

At a glance

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.

  • Works in 6 steps: Start with systematic diagnosis flow → Use AppLens (MCP) for AI-powered… → Check resource health before deep-diving… → …
  • Tasks that involve Container orchestration
  • SKILL.md covers Triggers, Rules, Quick Diagnosis Flow and Troubleshooting Guides by…, plus 4 more sections
  • Runs PowerShell and Shell scripts from its folder; calls az

What it does

Azure Diagnostics is an agent skill from microsoft/GitHub-Copilot-for-Azure, published by the product's own GitHub organization. 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…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 62 other files, including scripts and reference files (for example `references/app-service/README.md`, `references/azure-resource-graph.md` and `references/container-apps/README.md`).

It sits in DevOps & Cloud, covering Container orchestration, Root cause analysis and Deployment. It works with Microsoft Azure, Azure Monitor, Azure Event Hubs and Kubernetes. The repository describes itself as: GitHub Copilot for Azure. The licence is MIT.

When your agent uses it

  • Tasks that involve Container orchestration
  • Tasks that involve Root cause analysis
  • Tasks that involve Deployment

Example prompts

  • “/azure-diagnostics”

Requirements

  • A Bash shell
  • PowerShell

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Start with systematic diagnosis flow
  2. Use AppLens (MCP) for AI-powered diagnostics when available
  3. Check resource health before deep-diving into logs
  4. Select appropriate troubleshooting guide based on service type
  5. Document findings and attempted remediation steps
  6. Route AKS incidents to the dedicated AKS troubleshooting document

What it can do on your machine

Read from SKILL.md and the folder at commit d8f4f4e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 10 files in scripts/ (PowerShell and Shell, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • az

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use az, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Azure Diagnostics loads about 1.6k tokens when it runs, and up to ~6.1k if it reads all its reference files. Until then it costs about 197 tokens; SKILL.md has 447 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~197
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from microsoft/GitHub-Copilot-for-Azure at commit d8f4f4e, republished under its MIT licence (© microsoft). 447 words, ~1,596 tokens.

Download SKILL.mdSave it as .claude/skills/azure-diagnostics/SKILL.md (or your agent's skills folder). This skill also uses 57 other files; get the full folder from GitHub.
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
metadata.version
0.0.0-placeholder

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

  1. Start with systematic diagnosis flow
  2. Use AppLens (MCP) for AI-powered diagnostics when available
  3. Check resource health before deep-diving into logs
  4. Select appropriate troubleshooting guide based on service type
  5. Document findings and attempted remediation steps
  6. Route AKS incidents to the dedicated AKS troubleshooting document

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?

Show full SKILL.md (196 more words)Show less

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
bash
# 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
bash
# Check specific resource health
az resource show --ids RESOURCE_ID

# Check recent activity
az monitor activity-log list -g RG --max-events 20

References

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 57 other files (scripts, references) in plugins/azure-skills/skills/azure-diagnostics of microsoft/GitHub-Copilot-for-Azure.

  • SKILL.md
  • references/app-service/README.md
  • references/azure-resource-graph.md
  • references/container-apps/README.md
  • references/functions/README.md
  • references/kql-queries.md
  • scripts/aks-baseline.ps1
  • scripts/aks-baseline.sh
  • scripts/appservice-diagnostics.ps1
  • scripts/appservice-diagnostics.sh
  • scripts/containerapp-diagnostics.ps1
  • scripts/containerapp-diagnostics.sh
  • scripts/pod-evidence.ps1
  • scripts/pod-evidence.sh
  • scripts/run-ig.ps1
  • scripts/run-ig.sh
  • … and 42 more

Open the folder on GitHubat commit d8f4f4e

Used in 3 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in microsoft/GitHub-Copilot-for-Azure, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Azure Diagnostics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Azure Diagnostics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azure Diagnostics this skillmicrosoft/GitHub-Copilot-for-Azure2551 repos~1.6kAutomated safety check: PassMIT
Openbkn Deployopenbkn-ai/bkn-foundry629—~1.9kAutomated safety check: NotesCustom licence
Aspire MonitoringCommunityToolkit/Aspire629—~3.5kAutomated safety check: PassMIT
Kcli Cluster Deploymentkarmab/kcli653—~1.5kAutomated safety check: PassApache-2.0
Apex Azure Diagnosticsjonathan-vella/apex217—~2.1kAutomated safety check: PassMIT
Aks Deployment Skilltimothywarner/chatgptclass143—~916Automated safety check: PassCustom licence

Similar skills

  • Openbkn Deploy

    openbkn-ai/bkn-foundry

    Deploy or upgrade OpenBKN on a customer-authorized Linux server through the repository's deploy scripts, with preflight checks, explicit confirmation, secret handling, and post-deployment…

    629 GitHub stars~1.9k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Aspire Monitoring

    CommunityToolkit/Aspire

    ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard.

    629 GitHub stars~3.5k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Guides deployment and management of Kubernetes clusters with kcli.

    653 GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Apex Azure Diagnostics

    jonathan-vella/apex

    WORKFLOW SKILL — Debug Azure production issues: Container Apps, Functions, App Service, AKS, VMs and messaging, with KQL log analysis.

    217 GitHub stars~2.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Aks Deployment Skill

    timothywarner/chatgptclass

    Deploy and operate workloads on Azure Kubernetes Service (AKS) the safe way.

    143 GitHub stars~916 tokensUpdated 18 days ago
    DevOps & CloudAuto-check passed
  • Ama Logs Update Charts Release Notes

    microsoft/Docker-Provider

    Official

    Prepare an ama-logs release PR: bump the image tag (X.Y.Z) across Helm charts, manifests, and Dockerfiles, and add a formatted ReleaseNotes.md entry.

    173 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed

More from microsoft/GitHub-Copilot-for-Azure

All 56 skills in this repo
  • Capacity

    microsoft/GitHub-Copilot-for-Azure

    Official

    Discovers available Azure OpenAI model capacity across regions and projects.

    255 GitHub starsUsed in 2 repos~1.7k tokens
    Auto-check passed
  • Deploy Model

    microsoft/GitHub-Copilot-for-Azure

    Official

    Unified Azure OpenAI model deployment skill with intelligent intent-based routing.

    255 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Entra Agent Id

    microsoft/GitHub-Copilot-for-Azure

    Official

    Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant)…

    255 GitHub starsUsed in 3 repos~4k tokens
    Auto-check passed
  • Microsoft Foundry

    microsoft/GitHub-Copilot-for-Azure

    Official

    Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end.

    255 GitHub starsUsed in 1 repo~6.7k tokens
    Auto-check passed
  • Azure Storage

    microsoft/GitHub-Copilot-for-Azure

    Official

    Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake.

    255 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • Azure Quotas

    microsoft/GitHub-Copilot-for-Azure

    Official

    Check/manage Azure quotas and usage across providers. An agent skill from microsoft/GitHub-Copilot-for-Azure.

    255 GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed

Categories

Questions about Azure Diagnostics

What does Azure Diagnostics do?

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. Azure Diagnostics is an agent skill from microsoft/GitHub-Copilot-for-Azure, published by the product's own GitHub organization. Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.

When should I use Azure Diagnostics?

Azure Diagnostics fits situations like: tasks that involve Container orchestration; tasks that involve Root cause analysis; tasks that involve Deployment.

How do I install Azure Diagnostics in Claude Code?

Run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-diagnostics -a claude-code`. Or copy the skill folder (plugins/azure-skills/skills/azure-diagnostics in microsoft/GitHub-Copilot-for-Azure) into .claude/skills/azure-diagnostics in your project. Claude Code loads it when a task matches its description.

How do I install Azure Diagnostics in Codex?

Run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-diagnostics -a codex`. Or copy the skill folder (plugins/azure-skills/skills/azure-diagnostics in microsoft/GitHub-Copilot-for-Azure) into .agents/skills/azure-diagnostics in your project. Codex loads it when a task matches its description.

Can I use Azure Diagnostics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-diagnostics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-diagnostics, .gemini/skills/azure-diagnostics, .github/skills/azure-diagnostics and .opencode/skills/azure-diagnostics in your project.

What does Azure Diagnostics need to run?

Going by SKILL.md and its folder, Azure Diagnostics needs PowerShell and a shell for the scripts in its folder and the command-line tools its instructions call (az). Our summary lists: A Bash shell; PowerShell.

Does Azure Diagnostics access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Azure Diagnostics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Azure Diagnostics use?

Azure Diagnostics is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Azure Diagnostics use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.

What are the alternatives to Azure Diagnostics?

Skills that share tags, products or a category with Azure Diagnostics: Openbkn Deploy (openbkn-ai/bkn-foundry, 629 stars), Aspire Monitoring (CommunityToolkit/Aspire, 629 stars), Kcli Cluster Deployment (karmab/kcli, 653 stars) and Apex Azure Diagnostics (jonathan-vella/apex, 217 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azure Diagnostics?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/GitHub-Copilot-for-Azure, which has 255 GitHub stars. The repository holds 56 skills in this directory. The repository was last updated on October 7, 2026.

Source: microsoft/GitHub-Copilot-for-Azure on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.