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.
- 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 AccessRecon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
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'.
Reporting behind it
Changelog
v5- v5Candidate ingested via manual entry.2026-07-31
- v4Candidate ingested via manual entry.2026-07-31
- v3Candidate ingested via manual entry.2026-07-31
- v2Candidate ingested via manual entry.2026-07-31
- v1No 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.
title: Azure AD End-User Consent Blocked for Risk-Based Risky App Exceptions
id: 8f301b21-31c9-45b5-a8c9-18021752d3c0
status: test
description: 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'.
references:
- https://learn.microsoft.com/en-us/entra/architecture/security-operations-applications#end-user-stopped-due-to-risk-based-consent
- https://github.com/SigmaHQ/sigma/blob/master/rules/cloud/azure/audit_logs/azure_app_end_user_consent_blocked.yml
author: Bailey Bercik '@baileybercik', Mark Morowczynski '@markmorow', Huntrule Team
date: 2022-07-10
tags:
- attack.credential-access
- attack.t1528
logsource:
product: azure
service: auditlogs
detection:
selection:
failure_status_reason: Microsoft.online.Security.userConsentBlockedForRiskyAppsExceptions
condition: selection
falsepositives:
- Unknown
level: medium
license: DRL-1.1
related:
- id: 7091372f-623c-4293-bc37-20c32b3492be
type: derived