Normalization Schema Email
In brief
The normalized email schema now lists `EmailInteraction` alongside `EmailDelivery` and `EmailInspection` as allowed `EventType` values.
What Defender admins need to know
Review validation, parsing, and downstream processing that rely on the documented EventType enumeration.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
| Field | Class | Type | Description |
|---|---|---|---|
| EventType | Mandatory | Enumerated | Describes the normalized email activity. Allowed values are EmailDelivery, EmailInspection, and . |
| EventSubType | Optional | Enumerated | Provides more detail about the email activity. Allowed values are EmailSent and EmailReceived. |
| EventSchema | Mandatory | Enumerated | The schema name is EmailEvent. |
| EventSchemaVersion | Mandatory | SchemaVersion (String) | The version of the schema. The version documented here is 1.0.0. |
@@ -124,7 +124,7 @@ Fields common to all schemas are described in detail in [ASIM common fields](nor
| Field | Class | Type | Description |
| --- | --- | --- | --- |
-| **EventType** | Mandatory | Enumerated | Describes the normalized email activity. Allowed values are `EmailDelivery` and `EmailInspection`. |
+| **EventType** | Mandatory | Enumerated | Describes the normalized email activity. Allowed values are `EmailDelivery`, `EmailInspection`, and `EmailInteraction`. |
| **EventSubType** | Optional | Enumerated | Provides more detail about the email activity. Allowed values are `EmailSent` and `EmailReceived`. |
| **EventSchema** | Mandatory | Enumerated | The schema name is `EmailEvent`. |
| **EventSchemaVersion** | Mandatory | SchemaVersion (String) | The version of the schema. The version documented here is `1.0.0`. |
