Skip to content

Commit b508030

Browse files
authored
Update submissions-result-definitions.md
1 parent 218ca4d commit b508030

File tree

1 file changed

+19
-7
lines changed

1 file changed

+19
-7
lines changed

defender-office-365/submissions-result-definitions.md

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.collection:
1616
- tier1
1717
description: Admins and end-users can learn about the results of submitting entities to Microsoft for analysis.
1818
ms.service: defender-office-365
19-
ms.date: 07/26/2024
19+
ms.date: 06/13/2025
2020
appliesto:
2121
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Exchange Online Protection</a>
2222
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 1 and Plan 2</a>
@@ -37,16 +37,28 @@ When admins or users submit items to Microsoft for analysis, we do the following
3737
[Learn more how submissions are processed behind-the-scenes to generate the result](https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/how-your-submissions-to-defender-for-office-365-are-processed-behind-the-scenes/4231551).
3838

3939
> [!NOTE]
40-
> In U.S. Government organizations (Microsoft 365 GCC, GCC High, and DoD), admins can submit items to Microsoft for analysis, but the items are analyzed for email authentication and policy hits only. Payload reputation, detonation, and grader analysis aren't done for compliance reasons (data isn't allowed to leave the organization boundary).
40+
>
41+
> - In U.S. Government organizations (Microsoft 365 GCC, GCC High, and DoD), admins can submit items to Microsoft for analysis, but the items are analyzed for email authentication and policy hits only. Payload reputation, detonation, and grader analysis aren't done for compliance reasons (data isn't allowed to leave the organization boundary).
42+
> - AI-powered Submissions Response capability introduces generative AI explanations for email submissions to Microsoft. These explanations aim to provide enterprise admins with clear, detailed, human-readable explanations for why messages were classified. Currently, this feature is scoped to email submissions only, and AI-generated explanations aren't used for the following types of submissions:
43+
> - Files
44+
> - URLs
45+
> - Microsoft Teams messages
46+
> - User submissions
47+
>
48+
> AI-generated explanations are available for the following verdicts:
49+
>
50+
> - Spam
51+
> - Bulk
52+
> - Threats found
53+
> - No threats found
54+
> - Unknown
55+
>
56+
> If the AI-generated explanation is unavailable, the system falls back to the existing explanation as described in the following table.
4157
4258
The following table describes the results of submissions to Microsoft:
4359

4460
- **Status** indicates whether the previously described checks have been completed.
45-
- **Result** indicates the details that were generated during the analysis using the previously described checks
46-
47-
> [!NOTE]
48-
> The new AI-powered Submissions Response capability introduces generative AI explanations for email submissions in Microsoft Defender. These explanations aim to provide enterprise administrators with clear, detailed, human-readable rationales for why a message was classified as spam, phishing, or clean. This feature is scoped specifically to email submissions. Submissions involving files, Teams messages, or URLs are currently out of scope. Also user submissions are currently out of scope as well.
49-
> For the result types like Spam, Bulk, Threats found, No Threats found and Uknowns, you will see the LLM-based response. However, if for any reason the AI-generated explanation is unavailable, the system will fall back to the existing explanation as captured in the following table.
61+
- **Result** indicates the details that were generated during the analysis using the previously described checks.
5062

5163
|Status|Result|Description|
5264
|---|---|---|

0 commit comments

Comments
 (0)