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/references/cannot-connect-to-vm.md

Cannot Connect to VM

Router for Azure VM connectivity issues. Determine OS first: Windows usually means RDP/3389 and TermService; Linux means SSH/22 and sshd; other images usually use SSH but may need current docs.

Routing

| Signal | Category | Reference | | --- | --- | --- | | can't RDP, timeout, black screen, internal error | RDP | rdp-connectivity.md | | can't SSH, refused, permission denied, publickey | SSH | ssh-connectivity.md | | NSG, public IP, NIC, routes, effective rules | Network | network-connectivity.md | | Windows Firewall, iptables, firewalld, UFW | Guest firewall | firewall-blocking.md | | VM agent, Run Command timeout, Serial Console, boot diagnostics | VM agent/tools | vm-agent-not-responding.md | | password, credentials, access denied, CredSSP, account expired | Credential/auth | credential-auth-errors.md | | TermService, RDP disabled, changed port, TLS cert, NLA, licensing | RDP service/config | rdp-service-config.md |

Workflow

  1. Pick the symptom category and open the linked reference.
  2. Match the user's symptom to a solution row and fetch current docs for that row.
  3. Before extension-backed operations, run pre-flight checks.
  4. Return evidence, likely cause, safe next command, remediation, and escalation.

Pre-Flight Safety Checks

Run before az vm user update, az vm user reset-ssh, az vm user reset-remote-desktop, az vm run-command invoke, or any extension-backed operation.

az vm get-instance-view --name <vm> -g <rg> \
  --query "instanceView.{power:[statuses[?starts_with(code,'PowerState/')]][0][0].code,prov:[statuses[?starts_with(code,'ProvisioningState/')]][0][0].code,agent:vmAgent.statuses[0].displayStatus}" -o json
az vm extension list --vm-name <vm> -g <rg> \
  --query "[].{name:name,state:provisioningState}" -o table

| Check | Safe | Unsafe | | --- | --- | --- | | Power | PowerState/running | other, missing, or query error | | Provisioning | ProvisioningState/succeeded | creating/updating/deleting/failed, missing, or query error | | VM agent | Ready | not ready, null, missing, or query error | | Extensions | all Succeeded or none | creating/updating/deleting/failed |

If unsafe: stop, name the failed check, and use non-agent options such as Serial Console, offline repair VM, or Portal actions. If transient, wait and rerun checks only.

Escalation

Check Resource Health, then offer restart or redeploy only with user approval. For broad docs, use Windows RDP, Linux SSH, Windows VM hub, or Linux VM hub.