Agent Wealth HubFree public resources
中文 EN العربية

Back to catalog / Developer tools

Azure diagnostics: trace failures through health and logs

Check evidence and resource health first, then follow the service-specific Azure guide.

Skills

Identify the affected Azure service and symptom, and start with logs, metrics, and timelines supplied by the user. If live access is prohibited, do not call cloud query or mutation tools. When live triage is permitted, use AppLens when available and check Azure Resource Health before activity logs, App Insights/KQL, or service logs. Select the reference for Container Apps, App Service, Functions, AKS, VMs, or messaging. Tie diagnoses to evidence and record attempted steps. A remediation may restart an app or alter networking or resource configuration; explain its effect and obtain authorization before changing anything. Read-only troubleshooting access is not permission to modify resources.

Permissions

Prerequisites

Permissions

Limitations

Identify service and symptom, check resource health and supplied evidence first; AKS, VM connectivity, and messaging have focused guides.

Pinned upstream source

https://github.com/microsoft/skills/blob/fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb/.github/plugins/azure-skills/skills/azure-diagnostics/SKILL.md

Repository
microsoft/skills
File path
.github/plugins/azure-skills/skills/azure-diagnostics/SKILL.md
Pinned commit
fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb
Source checked
2026-10-14 · Reviewed against the pinned upstream source

Repository metrics

These values describe the upstream repository, not popularity or likes for an individual skill or playbook.

Stars
Not collected
Forks
Not collected
Observed at
Not collected

No metrics snapshot is available yet.

License: MIT

Compatible tools

Azure CLI · Azure Monitor / App Insights · Azure MCP AppLens · bundled diagnostic scripts

View skill directory

Main topic

Take a coding Agent change from context to verification

Related resources