azure-resource-health-diagnose

Diagnose Azure resource failures using logs, metrics, and telemetry to produce prioritized remediation plans.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/serpro-workshop-fortaleza/datacorp-sifap-modernization-team-kit --skill azure-resource-health-diagnose-serpro-workshop-fortaleza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-resource-health-diagnose
Source: https://github.com/serpro-workshop-fortaleza/datacorp-sifap-modernization-team-kit/tree/main/.github/skills/azure-resource-health-diagnose
Command: npx skills add https://github.com/serpro-workshop-fortaleza/datacorp-sifap-modernization-team-kit --skill azure-resource-health-diagnose-serpro-workshop-fortaleza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an Azure resource fails, degrades, or gets throttled, finding the root cause across logs, metrics, and telemetry is slow and error-prone. This Skill guides a structured investigation of a specific deployed Azure resource and produces a prioritized remediation plan with concrete Azure CLI commands. ## Core Features & Use Cases - Resource discovery and health assessment: Locates the resource across subscriptions, detects its type (Web Apps, VMs, Cosmos DB, Storage, SQL, Functions, Key Vault, Service Bus), and checks provisioning state, availability, and utilization. - Log and telemetry analysis: Runs KQL diagnostic queries against Log Analytics and Application Insights to find error patterns, performance degradation, and dependency failures. - Severity classification and remediation plan: Classifies issues as Critical/High/Medium/Low, identifies root-cause categories, and generates a phased fix plan with CLI commands, validation steps, and rollback guidance. - Use Case: Your App Service starts returning HTTP 500 errors after a deployment. Ask the Skill to diagnose it; it queries the last 24 hours of logs, correlates errors with the deployment, and proposes immediate, short-term, and long-term fixes. ## Quick Start Ask the AI to diagnose why your named Azure resource is failing or degraded and to produce a remediation plan.

Frequently Asked Questions about azure-resource-health-diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why an Azure resource is failing?▼

Provide the resource name and optionally its resource group or subscription. The Skill locates the resource, checks its health status, runs KQL queries against Log Analytics and Application Insights, classifies issues by severity, and generates a phased remediation plan.

What Azure resource types can be troubleshooted with this workflow?▼

It covers Web Apps, Function Apps, Virtual Machines, Cosmos DB, Storage Accounts, SQL Database, Application Insights, Key Vault, and Service Bus. Each type has tailored diagnostics, such as throttling metrics for Cosmos DB or boot diagnostics for VMs.

Does Azure resource diagnosis require the Azure MCP server?▼

The Skill prefers Azure MCP server tools (azmcp-*) when available, but falls back to the Azure CLI (az) for resource discovery and log queries. Either way, the target resource must be deployed and emitting telemetry.

Why does the diagnosis report no logs for my Azure resource?▼

No logs appear when diagnostic settings are not enabled or the resource was recently deployed. The Skill suggests enabling diagnostic settings and waiting for data, or it provides a generic health assessment while noting the limitation.

Can the Skill apply remediation fixes automatically?▼

No. It presents a health assessment summary and asks for explicit confirmation before generating the detailed remediation plan. Fixes are provided as Azure CLI commands with validation and rollback steps for the user to execute.