
Azure resource health diagnose
Diagnoses an Azure resource from logs and telemetry and drafts a tiered remediation plan
- Scripts
- None
- Platforms
- Claude Code, Codex, Cursor
- GitHub stars
- 41.3K
- Last commit
- today
- License
- MIT
- Listing updated
- 1 day ago
Similar skills
About Azure resource health diagnose
Azure resource health diagnose is an open-source agent skill for cloud and infrastructure. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.
Given a named Azure resource, the workflow loads Azure best practices through the Azure MCP server, locates the resource across subscriptions and asks for a subscription or resource group when several match. It then picks diagnostics suited to the resource type, such as logs and dependency tracking for web and function apps, boot diagnostics for virtual machines, throttling for Cosmos DB, or dead-letter queues for Service Bus.
Telemetry comes from Log Analytics and Application Insights through KQL queries for recent errors, CPU pressure, failed requests and database connection failures. The agent looks for recurring patterns and correlates them with deployments or configuration changes. Issues are classified critical, high, medium or low and sorted into root-cause groups such as configuration, resource limits, network, application, external dependency and security.
The remediation plan is staged into immediate actions, short-term fixes and long-term improvements, each with Azure CLI commands, validation and rollback. The agent shows a health summary and waits for a yes before producing the full report. The resource must be deployed and generating logs, and diagnostic settings may need enabling if none exist.
When your agent uses it
Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.
From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.
What it can access
From a static check of its 1 file (11 KB) on GitHub on 19 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.
Check another skill before you install it.
Install
Copy the skill folder to ~/.claude/skills/azure-resource-health-diagnose to use it in all your projects:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/azure-resource-health-diagnose &&
cp -R "$tmp/skills/azure-resource-health-diagnose" ~/.claude/skills/azure-resource-health-diagnose &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/azure-resource-health-diagnose inside it instead.
Copy the skill folder to ~/.agents/skills/azure-resource-health-diagnose to use it in every repository:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/azure-resource-health-diagnose &&
cp -R "$tmp/skills/azure-resource-health-diagnose" ~/.agents/skills/azure-resource-health-diagnose &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/azure-resource-health-diagnose inside it instead.
Copy the skill folder to ~/.cursor/skills/azure-resource-health-diagnose to use it in every project:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/azure-resource-health-diagnose &&
cp -R "$tmp/skills/azure-resource-health-diagnose" ~/.cursor/skills/azure-resource-health-diagnose &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/azure-resource-health-diagnose inside it instead.
Run in a terminal (add --scope workspace to install it for the current workspace only):
gemini skills install https://github.com/github/awesome-copilot.git --path skills/azure-resource-health-diagnoseOr copy the folder to ~/.gemini/skills/azure-resource-health-diagnose yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/azure-resource-health-diagnose:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/azure-resource-health-diagnose &&
cp -R "$tmp/skills/azure-resource-health-diagnose" ~/.copilot/skills/azure-resource-health-diagnose &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/azure-resource-health-diagnose inside it instead.
Get the folder:
git clone --depth 1 https://github.com/github/awesome-copilot.gitThen copy awesome-copilot/skills/azure-resource-health-diagnose into your agent's skills folder as azure-resource-health-diagnose. Agents that support SKILL.md read one folder per skill.
What it does
- Resource lookup
- Finds the target resource across subscriptions and asks when there are multiple matches.
- Type-specific checks
- Adapts diagnostics to web apps, VMs, Cosmos DB, storage, SQL, Key Vault and Service Bus.
- KQL log analysis
- Runs queries for errors, performance trends, failed requests and connection failures.
- Root cause grouping
- Classifies issues by severity and by cause category.
- Staged remediation
- Plans fixes in three phases with CLI commands, validation and rollback.
Good for
- Find out why a web app is returning errors
- Check a Cosmos DB account for throttling
- Analyse a VM with high CPU over the past week
- Produce a health report for an incident review
Azure resource health diagnose FAQ
What must be set up first?
An authenticated Azure MCP server and an identified target resource that is deployed and producing logs.
What if no logs exist?
The skill suggests enabling diagnostic settings and waiting for data.
Does it fix things automatically?
It presents findings and a remediation plan and waits for confirmation before the detailed report.
How do I install Azure resource health diagnose in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/azure-resource-health-diagnose to use it in all your projects, or to .claude/skills/azure-resource-health-diagnose in one project.
Does Azure resource health diagnose run scripts?
No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.
Which AI agents can use Azure resource health diagnose?
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.
What are the best alternatives to Azure resource health diagnose?
The closest alternatives to Azure resource health diagnose are AWS resource health diagnose, Assess observability health, AWS cloudwatch investigation, Connect observability and Azure advisor actionability.
Where this comes from
- Description: from the skill's own SKILL.md.
More from github/awesome-copilot

A DevOps checklist for deploys, Docker, Kubernetes, CI/CD, rollback and mobile releases
- Open source
- 41.3K GitHub stars
- Cloud and infrastructure

Guides Qdrant scaling when data outgrows a node: tenants, time windows or sharding
- Open source
- 41.3K GitHub stars
- Knowledge and memory

Explains Qdrant's per-shard query subsampling for large limits across many auto-shards
- Open source
- 41.3K GitHub stars
- Knowledge and memory

Creates, exports and appends to Arize evaluation datasets using the ax command line
- Open source
- 41.3K GitHub stars
- AI models and LLM tooling

Creates Arize LLM-as-judge evaluators and runs them on traces or experiment results
- Open source
- 41.3K GitHub stars
- AI models and LLM tooling

Runs a model over an Arize dataset, saves the results as an experiment and compares runs
- Open source
- 41.3K GitHub stars
- AI models and LLM tooling


