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

Unable to RDP into the VM

Use for Windows VM RDP timeouts, refused connections, black screen, or RDP error dialogs.

Symptoms -> Solutions

| Symptom | Action | Docs | | --- | --- | --- | | timeout/no response | Check power state, public IP, NSG allow for 3389 | RDP NSG | | timeout with NSG OK | Check guest firewall | Guest firewall | | credentials failed | Reset password or username format | RDP errors | | internal/security/authentication error | Check TLS, NLA, CredSSP, certificate, clock skew | Internal / General | | black screen after login | Check Explorer, GPU driver, GPO, session state | Detailed | | license server unavailable | Fix or remove RDS licensing role | RDP errors | | cannot find computer | Check public IP, DNS, and VM allocation | RDP errors | | connects then disconnects | Check session limits, idle timeout, resources | RDP overview | | works from some IPs | Check NSG source restriction | RDP NSG | | Event IDs in logs | Match event ID to documented cause | Event IDs | | guest NIC disabled | Enable NIC via safe command path | RDP NIC |

Quick Commands

Commands marked by reset/update use VM agent/extensions. Run Pre-Flight Safety Checks first.

az vm get-instance-view --name <vm> -g <rg> --query "instanceView.statuses" -o table
az network nsg rule list --nsg-name <nsg> -g <rg> -o table
az network watcher test-ip-flow --direction Inbound --protocol TCP \
  --local <vm-private-ip>:3389 --remote <your-public-ip>:* --vm <vm> -g <rg>
az vm user reset-remote-desktop --name <vm> -g <rg>
az vm user update --name <vm> -g <rg> -u <user> -p '<new-password>'