azure-diagnostics
Debug Azure production issues using AppLens, Azure Monitor, resource health, and safe triage, including evidence-only diagnosis without live access. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, 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, lock renewal during long-running processing, service bus dead letter.
Target: Cloud, operations & security. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Azure Diagnostics
- Triggers
- Rules
- Quick Diagnosis Flow
- Troubleshooting Guides by Service
- Routing
- Quick Reference
- Common Diagnostic Commands
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. 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 er
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- microsoft/skills
- Source file
- .github/plugins/azure-skills/skills/azure-diagnostics/SKILL.md
- Fixed revision
- 18e05b845d43e869b5701d796abce6e9a49e57db
Requirements
- Only the author’s Skill metadata is included. Read the full instructions to check dependencies, licensing and conditions of use.
A small first task
先阅读原作者说明，再决定是否在自己的 AI 工具中使用。
Instructions for your AI tool
- Claude Desktop: resource-specific guide not available yet
- Claude Code: resource-specific guide not available yet
- Cursor: resource-specific guide not available yet
- Codex: resource-specific guide not available yet
Author documentation is not live verification by this site. Without evidence, we do not mark a resource as compatible, safe or free.
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: Microsoft Skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T00:00:24.685Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.