Azure AD End-User Consent Blocked for Risk-Based Risky App Exceptions

Alerts when Azure end-user consent is blocked due to risk-based consent for risky apps.

FreeReviewedSigma · Medium · v5
Product
azure
Service
auditlogs
Author
Bailey Bercik '@baileybercik', Mark Morowczynski '@markmorow' (SigmaHQ), DRL 1.1
Published
2022-07-10
Updated
2026-07-31

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule matches Azure audit log events where end-user consent is blocked due to risk-based consent policy, specifically when the failure reason indicates consent was blocked for risky apps exceptions. Blocking consent is significant because it prevents potentially malicious or high-risk app access, while also providing attackers a visibility point into whether their attempted consent flows are being denied. Telemetry relied on is Azure audit log data, using the failure status reason value 'Microsoft.online.Security.userConsentBlockedForRiskyAppsExceptions'.

Related detections9 linkedT1528 — drag to rearrange
Malicious OAuth Application Granted Full Mailbox and EWS Permissions (via m365)
Suspicious GAM OAuth Token Enumeration via Process Creation
Suspicious Entra ID Device Code Flow Authentication
Suspicious Delegated Permission Grant to Entra Agent Access Scope via Azure Audit Logs
Suspicious OAuth Application Registration with Localhost Reply URL via Azure AD
Malicious PRT Token Forging via AADInternals (via ps_script)
Possible VMware Workspace ONE SSRF via instanceHealth hostName At-Injection (via webserver)
Suspicious Entra Device Code Authentication with Office Client and Automated User Agent
Suspicious Access to Kubernetes Service Account Token via Curl or Wget (via process_creation)
Azure AD End-User Consent Blocked for Risk-Based Risky App Exceptions
Pivot detection · T1528 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.