Back to All Scenarios
PASSEDcloud / azure_front_door_routing_error
Azure Front Door Routing Error — Backend Pool Misconfiguration
An Azure Front Door configuration update introduces a routing rule error that sends 40% of production traffic to a staging backend pool. Users intermittently see staging data mixed with production data, causing data integrity concerns and customer confusion.
Pattern
AZURE_CLOUD
Severity
CRITICAL
Confidence
95%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AZURE_CLOUD | AZURE_CLOUD | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 18 linked | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Azure Front Door with 3 backend pools (prod, staging, dev). Configuration update via ARM template has typo in routing rule. 40% of traffic misrouted to staging. Staging database has stale data. No canary analysis configured.
Injected Error Messages (2)
azure front door routing anomaly — 40% of requests being directed to staging backend pool instead of production, routing rule 'prod-default' modified in last ARM template deployment now matching wildcard pattern incorrectly, users reporting inconsistent data between page loads, azure front door probe showing both prod and staging backends as healthy
azure front door configuration drift detected — backend pool association incorrect after latest deployment, production health endpoint returning mixed responses (production data on 60% of requests, stale staging data on 40%), customer reports of seeing test data and outdated pricing, azure front door logs showing traffic split across wrong backend pools
Neural Engine Root Cause Analysis
Azure Front Door routing rule 'prod-default' was misconfigured during the last ARM template deployment, causing it to match a wildcard pattern incorrectly. This resulted in 40% of production traffic being routed to the staging backend pool instead of the production backend pool. The issue is not with backend health (both pools show healthy) but with the Front Door routing logic that determines which backend pool receives incoming requests.
Remediation Plan
1. Immediately access Azure Front Door configuration via ARM template or Azure portal 2. Review and correct the routing rule 'prod-default' to ensure it properly matches production requests and routes to production backend pool only 3. Update the wildcard pattern matching logic to exclude staging traffic routing 4. Deploy the corrected ARM template or apply changes directly 5. Verify routing behavior by monitoring traffic distribution between backend pools 6. Confirm user reports of data consistency issues are resolved
Tested: 2026-03-30Monitors: 2 | Incidents: 2Test ID: cmnckcqpl08iqobqec4i6k3f2