Suspicious Entra ID ROPC Authentication Bypassing MFA

PremiumReviewedSigma · Medium · v1
Product
azure
Service
signinlogs
Author
HuntRule
Published
2026-11-04
Updated
2026-11-04

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 detects Entra ID sign-ins using the resource owner password credentials flow which exchanges a username and password directly for tokens without browser consent thereby bypassing multi-factor authentication. Wiz observed attackers abusing first-party Microsoft apps that accept ROPC across tenants so successful ROPC authentications warrant investigation for credential compromise.

Related detections9 linkedT1528 — drag to rearrange
Suspicious Consent to Application Grant in Entra ID
Malicious Azure AD Application Consent Granted with Mail Permissions
Suspicious Device Code Authentication via Microsoft Authentication Broker
Suspicious Microsoft 365 OAuth Authorization to Visual Studio Code Client
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious Google Workspace OAuth Authorization for Chrome Web Store Scope via Token Audit
Suspicious OAuth Application Consent Grant via Azure Audit Logs
Suspicious OAuth Application Consent Granted High Privilege Mail Scopes (via m365)
Suspicious Token Request Using Microsoft Authentication Broker Client to Obtain Primary Refresh Token (via azure)
Suspicious Entra ID ROPC Authentication Bypassing MFA
Pivot detection · T1528 · 9 related

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