Back to All Scenarios
PASSEDcloud / azure_keyvault

Azure: Azure Key Vault Access Policy Removed — App Secrets Unavailable

An Azure Key Vault access policy was accidentally removed during a Terraform apply. Application cannot retrieve secrets.

Pattern
AZURE_CLOUD
Expected: AZURE_ACCESS_DENIED
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal

Test Results

MetricExpectedActualResult
Pattern RecognitionAZURE_ACCESS_DENIEDAZURE_CLOUD
Severity AssessmentCRITICALHIGH
Incident CorrelationN/ANone
Cascade EscalationN/ANo
RemediationAuto-Heal — Corax resolves autonomously

Scenario Conditions

Azure Key Vault 'prod-secrets'. Access policy for app identity removed by Terraform state drift. Application failing to read connection strings and API keys. All API calls returning 403.

Injected Error Messages (1)

Azure Key Vault access denied — app identity removed from access policy on vault 'prod-secrets', all secret/key/certificate read operations returning 403 Forbidden, Terraform state drift detected

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_ACCESS_DENIED)
  • Severity: HIGH (expected CRITICAL)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnr8vc09bqlig7dbx4fyfu