Microsoft 365 Impossible Travel Sign-ins Reported as Successful

Alerts on successful Microsoft 365 “Impossible travel activity” events in SecurityComplianceCenter telemetry.

FreeReviewedSigma · Medium · v4
Product
m365
Service
threat_management
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2020-07-06
Updated
2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags successful “Impossible travel activity” events reported in Microsoft Cloud App Security via SecurityComplianceCenter. Attackers may leverage compromised accounts and rapidly move between geographies, so impossible-travel detections can surface stealthy sign-in patterns that violate expected travel time. It relies on threat management telemetry from Microsoft 365 that records the event source, event name, and success status.

Related detections9 linkedT1078 — drag to rearrange
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious SSH Daemon Configuration Change Enabling Root Login
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Suspicious dMSA Object Access with Migration AccessMask
Malicious ESX Admins Group Added to Privileged Directory Group
Malicious ESX Admins Group Creation via WinRM Host
Suspicious BrightMetricAgent Remote Tool Execution Associated With Volt Typhoon
Suspicious SmarterMail Force Password Reset API Request Indicating Account Takeover
Suspicious Mailbox Forwarding Rule Creation Following AiTM Phishing
Microsoft 365 Impossible Travel Sign-ins Reported as Successful
Pivot detection · T1078 · 9 related

Changelog

v4
  1. v4
    Candidate ingested via manual entry.2026-07-31
  2. v3
    Candidate ingested via manual entry.2026-07-31
  3. v2
    Candidate ingested via manual entry.2026-07-31
  4. 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.