Forum Discussion

gokhantatar's avatar
gokhantatar
Occasional Reader
Jun 25, 2026

Need information on generating sample events for Threat Intelligence" (both duplicate posts)

Two things are tripping this up, and they're common mix-ups:

First — Attack Simulation Training doesn't generate Threat Intelligence events. If you used the built-in phishing simulator, its logs only show up under Email & collaboration → Attack simulation training → Simulations — they're intentionally excluded from real Threat Intelligence telemetry. That's likely why nothing's showing up even though you ran a campaign.

Second — your EICAR test should actually work, but check the right place: not the generic Office 365 Management Activity API's AuditLogRecordType page in isolation — go specifically to the RecordType values used for Defender for Office 365 threat events:

  • 28 = ThreatIntelligence (phishing/malware events)
  • 41 = ThreatIntelligenceUrl (Safe Links time-of-click/block events)
  • Plus ThreatIntelligenceAtpContent, ThreatFinder, MSTIC

To reliably generate one:

  1. Confirm Purview audit logging is enabled for the tenant first — if it isn't, nothing downstream gets logged regardless of what you trigger.
  2. From an external mailbox, send a test user the EICAR string as a .txt attachment (exact 68-byte string, see Microsoft's anti-malware testing doc). Defender for Office 365 should detect and quarantine it.
  3. Verify it landed first in the portal UI: Email & collaboration → Explorer → Malware tab — if it's there, the underlying ThreatIntelligence record exists and the Management API call should return it (allow a short delay; these aren't instant).
  4. For the Safe Links side, send a known-safe-but-flagged test URL (Microsoft publishes test URLs for this) to trigger ThreatIntelligenceUrl.

If it shows up in Explorer but still doesn't appear via the Management API, that's usually an API subscription/permission issue (you need an active subscription to the DLP.All or relevant Office 365 Management API content type, not just Graph permissions) — worth checking separately from the detection side.

No RepliesBe the first to reply