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/ssh-connectivity.md

Unable to SSH into the VM

Use for Linux VM SSH failures.

Symptoms -> Solutions

| Symptom | Action | Docs | | --- | --- | --- | | connection refused on 22 | Check sshd running/listening and port config | SSH overview | | connection timed out | Check power state, public IP, NSG, routes | SSH overview | | permission denied publickey/password | Verify user, key, password auth; reset key/password | SSH detail | | host key verification failed | Remove stale known_hosts entry | SSH detail | | server closed connection | Check disk, PAM, sshd config | SSH detail | | hangs with no response | Check firewall, routes, NIC | SSH overview | | Debian-specific failure | Check Debian networking/sshd doc | Debian | | Ubuntu: sshd unit not found, or ssh.service inactive | Expected on Ubuntu 24.04+ (socket-activated). Healthy = ssh.socket active and port 22 listening | Ubuntu SSH | | SELinux blocks sshd (RHEL family) | Fix SELinux policy or temporarily permissive | SELinux | | Entra ID SSH denied | Assign VM Admin/User Login role | SSH overview | | VM not booting/UEFI failure | Use boot diagnostics and repair VM | UEFI |

Quick Commands

Commands use VM agent/extensions. Run Pre-Flight Safety Checks first.

az vm user reset-ssh --name <vm> -g <rg>
az vm user update --name <vm> -g <rg> -u <user> --ssh-key-value "<ssh-public-key>"
az vm user update --name <vm> -g <rg> -u <user> -p '<new-password>'
# Listener + service state. Unit is `sshd` on RHEL/SLES/Azure Linux, `ssh` on Debian/Ubuntu.
az vm run-command invoke --name <vm> -g <rg> --command-id RunShellScript \
  --scripts 'ss -tlnp | grep ":22 "; for u in sshd ssh ssh.socket; do echo "$u: $(systemctl is-active $u)"; done'
# SELinux distros only. Ubuntu/Debian use AppArmor and have no getenforce/setenforce.
az vm run-command invoke --name <vm> -g <rg> --command-id RunShellScript \
  --scripts 'if command -v getenforce >/dev/null; then getenforce; else echo "SELinux not installed"; fi'
# Temporary permissive mode, SELinux distros only (reverts on reboot)
az vm run-command invoke --name <vm> -g <rg> --command-id RunShellScript \
  --scripts 'if command -v setenforce >/dev/null; then setenforce 0; else echo "SELinux not installed"; fi'