Index of every page on this site: llms.txt
All skills
microsoft avatar

/azure-diagnostics

@147c081 official
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/microsoft/github-copilot-for-azure/azure-diagnostics

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈251 tokens for metadata: the name and description. ≈2k when used: this file. ≈40k more on demand in 42 files.

Description uses 12.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈1003 characters, or 12.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Azure Diagnostics

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.

Triggers

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 errors, message lock issues)
  • Root-cause a symptom that looks like a healthy-runtime-but-wrong-destination problem (e.g., telemetry/messages stop flowing to the expected resource after a config change) — invoke this skill for the matrix even when MCP tools could answer the surface question alone

Rules

  1. Start with systematic diagnosis flow
  2. Use supplied evidence first. If the user requests evidence-only analysis or prohibits live Azure access, do not query or modify Azure. Diagnose from the supplied logs, metrics, and timeline; identify assumptions and provide optional verification steps.
  3. Use AppLens (MCP) for AI-powered diagnostics when available
  4. Check resource health before deep-diving into logs
  5. Select appropriate troubleshooting guide based on service type
  6. Document findings and attempted remediation steps
  7. Prefer bundled diagnostic scripts over ad hoc calls for permitted live collection when identifiers are known. If supplied evidence suffices or live access is prohibited, don't run them; otherwise run the applicable script first.
  8. Route AKS incidents to the dedicated AKS troubleshooting document
  9. Keep baseline AKS diagnostics available even when the optional aks-skills add-on is absent, declined, or unsupported by the host

Quick Diagnosis Flow

  1. Identify symptoms - What's failing?
  2. Check resource health - Is Azure healthy?
  3. Review logs - What do logs show?
  4. Analyze metrics - Performance patterns?
  5. Investigate recent changes - What changed?

Troubleshooting Guides by Service

Service Common Issues Reference
Container Apps Image pull failures, cold starts, health probes, port mismatches container-apps/
App Service High CPU, deployment failures, crashes, slow responses, TLS/custom domains app-service/
Function Apps App details, invocation failures, timeouts, binding errors, cold starts, missing app settings functions/
AKS Cluster access, nodes, kube-system, scheduling, crash loops, ingress, DNS, upgrades AKS Troubleshooting
Compute VM RDP/SSH connectivity, NSG/firewall blocks, credential resets, VM agent/tooling issues VM Connectivity Troubleshooting
Messaging Event Hubs & Service Bus SDK errors, AMQP failures, message lock, connectivity Messaging Troubleshooting

Routing

  • Keep Container Apps and Function Apps diagnostics in this parent skill.
  • Route active AKS incidents, AKS-specific intake, evidence gathering, and remediation guidance to AKS Troubleshooting.
  • Route Azure VM RDP/SSH connectivity, NSG/firewall, credential reset, and VM agent troubleshooting to VM Connectivity Troubleshooting.
  • Route Azure Messaging SDK troubleshooting (Event Hubs, Service Bus) to Messaging Troubleshooting.
  • For Function App VNet, route-table, NSG, or private-endpoint failures, use the Flex networking guidance and report the observed topology, causal evidence, impact scope, smallest safe fix, and recovery verification.

Quick Reference

Common Diagnostic Commands

# Inspect resource configuration and provisioning metadata (not Resource Health)
az resource show --ids RESOURCE_ID
# View activity log
az monitor activity-log list -g RG --max-events 20
# Container Apps logs
az containerapp logs show --name APP -g RG --follow
# Function App logs (query App Insights traces)
az monitor app-insights query --apps APP-INSIGHTS -g RG \
  --analytics-query "traces | where timestamp > ago(1h) | order by timestamp desc | take 50"

AppLens (MCP Tools)

For AI-powered diagnostics, use:

mcp_azure_mcp_applens
  intent: "diagnose issues with <resource-name>"
  command: "diagnose"
  parameters:
    resourceId: "<resource-id>"

Provides:
- Automated issue detection
- Root cause analysis
- Remediation recommendations

Azure Monitor (MCP Tools)

For querying logs and metrics:

mcp_azure_mcp_monitor
  intent: "query logs for <resource-name>"
  command: "logs_query"
  parameters:
    workspaceId: "<workspace-id>"
    query: "<KQL-query>"

See kql-queries.md for common diagnostic queries.


Check Azure Resource Health

Using MCP

mcp_azure_mcp_resourcehealth
  intent: "check health status of <resource-name>"
  command: "get"
  parameters:
    resourceId: "<resource-id>"

Using CLI

# Query the current Azure Resource Health availability status
RESOURCE_ID="/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/<provider>/<resource-type>/<resource-name>"
az rest --method get \
  --url "${RESOURCE_ID}/providers/Microsoft.ResourceHealth/availabilityStatuses/current?api-version=2025-05-01"

# Check recent activity
az monitor activity-log list -g RG --max-events 20

az resource show returns resource configuration and provisioning metadata; it does not query Azure Resource Health and cannot by itself establish that a resource is healthy or Available.

The Resource Health request requires Azure authentication and the Microsoft.ResourceHealth/AvailabilityStatuses/current/read operation at the applicable scope. It applies only to resource types supported by Azure Resource Health. Interpret availabilityState as Azure platform availability evidence (Available, Unavailable, Degraded, or Unknown), not as application or workload health. Available does not prove the guest, application, dependencies, or user path are healthy, and Unknown must not be treated as healthy.

If the resource type is unsupported, the status is unavailable, permission is denied, or the health query fails, report that limitation and leave Resource Health availability unestablished; do not substitute provisioning success or invent a healthy result.


References

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings22d4 checks · Risk SAFE
  • Gen Agent Trust Hub22d

    This skill includes some security considerations such as the execution of powerful diagnostic scripts and the processing of external log data. While these warrant review, they are used within the skill's intended functionality for Azure production troubleshooting. See detailed analysis for context.

  • Socket22d

    No alerts

  • Snyk22d

    Risk: MEDIUM · 1 issue

  • Runlayer8mo

    2/5 files flagged

Signed by skilld at 147c081. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated yesterday
metadata
{
  "author": "Microsoft",
  "version": "0.0.0-placeholder"
}
  • azure
  • diagnostics
  • app-service
  • functions
  • container-apps
  • aks
  • monitoring
  • troubleshooting
  • kql
  • appinsights

README badge

README badge for microsoft/github-copilot-for-azure/azure-diagnostics

Diagnoses Azure production issues across App Service, Container Apps, Function Apps, AKS, and messaging services using AppLens, Azure Monitor, and resource health checks. Provides systematic triage flows, KQL queries, and routing to service-specific troubleshooting guides for high CPU, deployment failures, pod issues, AMQP errors, and cold starts.

Generated from the current SKILL.md.

Does this skill cover all Azure services?
No. The skill focuses on App Service, Container Apps, Function Apps, AKS, Event Hubs, and Service Bus. Other Azure services are not in scope.
What tools does this skill use for diagnostics?
The skill uses AppLens (MCP) for AI-powered diagnostics, Azure Monitor for log and metric queries, and the Azure CLI for resource health checks.
Does this skill handle AKS troubleshooting?
Yes, but AKS incidents are routed to a dedicated AKS troubleshooting document for full incident intake and remediation guidance.
Can I use this skill to query logs in Log Analytics?
Yes. The skill includes KQL query examples and references a KQL query library for common diagnostic queries against Log Analytics workspaces.

Generated from the current SKILL.md. These answers refresh after source changes.