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

Network Connectivity Problems

Use when the VM is running but unreachable due to Azure network configuration: NSG, routing, NIC, public IP, or DNS.

Symptoms -> Solutions

| Symptom | OS | Action | Docs | | --- | --- | --- | --- | | no NSG allow for RDP/SSH | Any | Add inbound TCP 3389/22 from approved source | RDP NSG | | NIC and subnet NSGs conflict | Any | Traffic must pass both; inspect effective rules | Traffic filter | | UDR sends traffic to NVA | Any | Check effective routes and NVA forwarding | Routing | | no public IP | Any | Add public IP or use Bastion/private path | Public IP | | guest NIC disabled/down | Windows/Linux | Enable NIC via Run Command or Serial Console | RDP NIC / SSH overview | | static guest IP misconfig | Windows/Linux | Restore DHCP guest config | Reset NIC / SSH overview | | ghost NIC after disk swap/resize | Windows | Reset network interface | Reset NIC | | DNS failure | Any | Check DNS; Azure default is 168.63.129.16 | DHCP |

Quick Commands

az network nic list-effective-nsg --name <nic> -g <rg>
az network nic show-effective-route-table --name <nic> -g <rg> -o table
az vm list-ip-addresses --name <vm> -g <rg> -o table
az network watcher test-connectivity --source-resource <vm-resource-id> \
  --dest-address <ip> --dest-port <port> -g <rg>

Linux guest NIC commands use VM agent/extensions. Run Pre-Flight Safety Checks first.

az vm repair reset-nic --name <vm> -g <rg> --yes
az vm run-command invoke --name <vm> -g <rg> --command-id RunShellScript \
  --scripts "ip link show; ip addr show; ip link set eth0 up && dhclient eth0"