PASSEDcloud / azure_vm

Azure VM Unresponsive — Guest Agent Not Running

An Azure VM is running but unresponsive. The Azure Guest Agent stopped, preventing Azure from communicating with the VM. RDP and SSH connections timing out.

Pattern

AZURE_CLOUD

Expected: AZURE_VM_FAILURE

Severity

HIGH

Confidence

68%

Remediation

Auto-Heal

Test Results

Metric	Expected	Actual
Pattern Recognition	AZURE_VM_FAILURE	AZURE_CLOUD
Severity Assessment	CRITICAL	HIGH
Incident Correlation	N/A	None
Cascade Escalation	N/A	No
Remediation	—	Auto-Heal — Corax resolves autonomously

Scenario Conditions

Azure VM 'prod-web-01' (Standard_D4s_v3). VM status: Running. Guest Agent: Not Ready. Boot diagnostics show OS booted. RDP/SSH timeout.

Injected Error Messages (1)

Azure VM unresponsive — prod-web-01 running but Guest Agent not ready, RDP timeout, SSH timeout, boot diagnostics show OS booted normally, possible OS-level hang

Neural Engine Root Cause Analysis

Azure cloud infrastructure event detected — an Azure resource may be failing, an App Service is unhealthy, Azure AD authentication is disrupted, or a Service Bus queue is backed up. Azure outages can cascade across dependent services and affect both cloud-hosted applications and hybrid on-premises integrations relying on Azure AD.

Remediation Plan

1. Check Azure Service Health (status.azure.com) for any active incidents in your region. 2. Review Azure Monitor alerts and resource health for the affected service. 3. For App Service issues, check the Kudu console for application logs and restart the app if needed. 4. For Azure AD issues, verify conditional access policies and check the Azure AD sign-in logs for failure reasons. 5. For Service Bus, check dead-letter queues and verify the sending/receiving applications are connected and processing messages.

Improvements Applied

Pattern classified as AZURE_CLOUD (expected AZURE_VM_FAILURE)
Severity: HIGH (expected CRITICAL)

Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnoopu001flig7qbw1kssd