Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 270/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 09:12 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Defender for Office 365: New records in Streaming API and Sentinel EmailEvents table

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, safely structured
Introduction To improve visibility and alignment across Microsoft Defender for Office 365 and Microsoft Sentinel, we’re updating how email verdict and location changes are handled in the EmailEvents table. This change ensures that Sentinel reflects both current and historical verdicts, enabling more accurate threat analysis and investigation. When this will happen: General Availability: Rollout begins in early October 2025 and is expected to complete by early November 2025. How this affects your organization:Who is affected: Admins using Microsoft Defender for Office 365, Streaming API, and the EmailEvents table in Microsoft Sentinel. What will happen:The Streaming API will begin streaming updated records when an email’s verdict or location changes. Microsoft Sentinel will store both the updated and previous records, rather than replacing them. You may see multiple rows for the same email if its verdict or location is updated. This update aligns the EmailEvents table in Microsoft Sentinel with the behavior of the Advanced Hunting EmailEvents table. What you can do to prepare:Review and update existing queries and dashboards that rely on the EmailEvents table. Use the following KQL pattern to retrieve the latest record per email: summarize arg_max(Timestamp, *) by NetworkMessageId, RecipientEmailAddress Example query for emails with a "Phish" verdict: EmailEvents | where ThreatTypes has "Phish" | summarize arg_max(Timestamp, *) by NetworkMessageId, RecipientEmailAddress Learn more about the arg_max function: KQL arg_max documentation Compliance considerations: No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 09:12 UTC · 270 of 272 readable · 269 fully read · documentation 469/469 current