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-service-config.md

RDP Service and Configuration Issues

VM is reachable but the RDP service itself is broken or misconfigured.

Symptoms → Solutions

| Symptom | Solution | Documentation | | -------------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | TermService not running | Start the service and set to Automatic | Reset RDP service | | RDP port changed from 3389 | Reset port or update NSG to allow the custom port | Detailed RDP troubleshooting | | RDP disabled (fDenyTSConnections = 1) | Reset RDP config via CLI or Portal | Reset RDP service | | TLS/SSL certificate expired or corrupt | Delete cert and restart TermService to regenerate | RDP internal error | | NLA/Security Layer mismatch | Temporarily disable NLA for recovery | RDP general error | | GPO overriding local RDP settings | Check HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services | Detailed RDP troubleshooting | | RDS licensing expired | Remove RDSH role or configure license server | Specific RDP errors |

Quick Commands

⚠️ Warning: Commands marked with ⚡ use the VM agent/extensions. Run Pre-Flight Safety Checks before using them.

# ⚡ Reset all RDP configuration to defaults
az vm user reset-remote-desktop --name <vm-name> -g <resource-group>

# ⚡ Check TermService status via Run Command
az vm run-command invoke --name <vm-name> -g <resource-group> \
  --command-id RunPowerShellScript --scripts "Get-Service TermService | Select-Object Status, StartType"

# Restart VM (if RDP service is unrecoverable — requires user approval)
az vm restart --name <vm-name> -g <resource-group>

# Redeploy VM (moves to new host — last resort, requires user approval)
az vm redeploy --name <vm-name> -g <resource-group>