AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-diagnostics at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 42

troubleshooting/compute/vm-troubleshooting.md

Azure VM Connectivity Troubleshooting

Primary compute troubleshooting guide for incidents routed from ../../SKILL.md. Use for Azure VM RDP/SSH failures, NSG/firewall blocks, credential resets, and VM agent/tooling issues.

Quick Reference

| Property | Details | | --- | --- | | Best for | RDP/SSH failures, port 3389/22 timeouts, black screen, credential reset, VM agent issues | | Primary tools | mcp_azure_mcp_compute, mcp_azure_mcp_resourcehealth, mcp_azure_mcp_monitor, CLI fallback | | Router | references/cannot-connect-to-vm.md |

MCP Tools

| Tool | Purpose | | --- | --- | | mcp_azure_mcp_compute | VM state, instance view, VM agent, extension, NIC evidence | | mcp_azure_mcp_resourcehealth | Platform health before deeper diagnosis | | mcp_azure_mcp_monitor | Logs/metrics when workspace or resource scope is known | | mcp_azure_mcp_documentation | Current Microsoft Learn guidance for the matched symptom |

When to Use

  • "can't connect to my VM", "can't RDP", "can't SSH"
  • RDP/SSH timeout, refused, black screen, internal error, session drop
  • reset VM password, wrong credentials, access denied
  • NSG, guest firewall, port 3389/22, public IP, NIC, Serial Console, Run Command, VM agent

Guardrails

  • Default to read-only diagnostics; quote evidence before concluding root cause.
  • Do not run extension-backed commands (az vm user update, az vm user reset-ssh, az vm user reset-remote-desktop, az vm run-command invoke) until Pre-Flight Safety Checks pass.
  • Do not restart, redeploy, deallocate, or delete unless the user explicitly approves remediation.
  • If multiple issues appear, fix network-layer blockers before agent-dependent fixes.

Evidence Order

  1. VM state: power, provisioning, VM agent, extension states.
  2. Network layer: public IP, NIC/subnet NSGs, effective routes, IP flow.
  3. Guest OS: services and firewall via Run Command only when agent checks are safe.

Workflow

  1. Classify intent. If unclear, ask whether the user uses RDP or SSH and what error appears.
  2. Open references/cannot-connect-to-vm.md, choose the matching symptom category, then open that reference.
  3. If a command uses the VM agent/extensions, run pre-flight checks first and stop on any unsafe result.
  4. Use mcp_azure_mcp_documentation to fetch current docs for the selected URL or symptom.
  5. Respond with evidence, likely cause, safe diagnostic/fix commands, and escalation path.
mcp_azure_mcp_documentation
  intent: "find current Azure VM RDP SSH troubleshooting docs for <symptom>"
  parameters:
    query: "<documentation URL or user's symptom>"

Error Handling

| Error | Action | | --- | --- | | Docs lookup empty | Use the reference quick commands and tell user the doc URL may have changed | | VM name/resource group wrong | Ask user to verify resource identity | | Run Command timeout or VMAgentStatusCommunicationError | Do not run extension commands; use Serial Console/offline repair | | Serial Console unavailable | Enable Boot Diagnostics first | | Password reset fails | Check VMAccess alternatives in the credential and VM agent references | | Extension stuck updating | Do not add extensions; use Portal/Serial Console/offline repair |