IN PLAIN ENGLISH
What it does—and when it fits
Azure Diagnostics is Microsoft's systematic production-triage workflow for moving from symptoms to resource health, logs, metrics, recent changes, and service-specific next steps. It uses AppLens or Azure Monitor where available and routes Container Apps, App Service, Functions, AKS, VMs, and messaging services to focused references.
This is aimed at Azure operators and site-reliability engineers. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.
- Frame the incidentCapture symptoms, scope, timing, affected resources, and resource-health signals before guessing a cause.
- Correlate evidenceQuery relevant logs and metrics, use KQL or AppLens where appropriate, and compare recent changes.
- Route service-specific diagnosisContinue with the reference tailored to the affected Azure compute or messaging service.
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to microsoft/azure-skills.
- Core uses, limitations, and risks are separated for pre-install review.
No verified review text is in the current dataset. Use the linked source for the latest discussion.
Read the source note ↗INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
npx skills add https://github.com/microsoft/azure-skills --skill azure-diagnostics --agent claude-codenpx skills add https://github.com/microsoft/azure-skills --skill azure-diagnostics --agent claude-code -gProject install stays with this repository for team sharing. Personal install adds -g and works across repositories.
View install paths
.claude/skills/azure-diagnostics/~/.claude/skills/azure-diagnostics/Claude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Frame the incident
Capture symptoms, scope, timing, affected resources, and resource-health signals before guessing a cause.
Correlate evidence
Query relevant logs and metrics, use KQL or AppLens where appropriate, and compare recent changes.
Route service-specific diagnosis
Continue with the reference tailored to the affected Azure compute or messaging service.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to microsoft/azure-skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- Useful diagnosis requires accurate Azure resource context, time windows, telemetry retention, and sufficient read permissions.
- The workflow structures investigation but cannot guarantee a root cause when telemetry is absent or symptoms span external systems.
BEST FIT
Who it is for
Azure operators and site-reliability engineers
Platform teams handling production incidents
BEFORE YOU USE IT
Risks to review before use
Production remediation without sufficient evidence
Diagnostic commands may expose sensitive telemetry, and premature remediation can worsen an outage. Separate read-only evidence collection from writes, redact shared output, and require approval for changes.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
COMMON QUESTIONS
Azure Diagnostics Skill FAQ
What is the Azure Diagnostics Skill?
Azure Diagnostics is Microsoft's systematic production-triage workflow for moving from symptoms to resource health, logs, metrics, recent changes, and service-specific next steps. It uses AppLens or Azure Monitor where available and routes Container Apps, App Service, Functions, AKS, VMs, and messaging services to focused references.
How do I install the Azure Diagnostics Skill?
Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed skills.sh page and upstream repository; verify the current SKILL.md.
Is the Azure Diagnostics Skill safe to use?
SkillSignal checked the source on 2026-08-20, but that is not a runtime test or security certification. Review the “Production remediation without sufficient evidence” risk first and begin with the least access required.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at microsoft/azure-skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.