Back to All Scenarios
PASSEDcloud / azure_app_service
Azure App Service — 502 Bad Gateway After Deployment
An Azure App Service deployment broke the application. All requests returning 502. The deployment slot swap was not tested.
Pattern
AZURE_CLOUD
Expected: AZURE_APP_FAILURE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AZURE_APP_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 App Service 'company-api' (P2v3). Deployment via GitHub Actions. New deployment 15 min ago. Health check endpoint failing. 502 on all routes.
Injected Error Messages (1)
Azure App Service 502 — company-api returning Bad Gateway on all routes after deployment 15 min ago, health check failing, SCM site accessible, application crash in startup, EventLog: 'Application pool crashed'
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_APP_FAILURE)
- Severity: HIGH (expected CRITICAL)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnoopu001glig7g4310cud