Merge pull request #4223 from MicrosoftDocs/main

[AutoPublish] main to live - 06/13 10:30 PDT | 06/13 23:00 IST

Author: m365-skilling-repo-management[bot]

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

@@ -16,7 +16,7 @@ ms.collection:
  - tier1
 description: Admins and end-users can learn about the results of submitting entities to Microsoft for analysis.
 ms.service: defender-office-365
-ms.date: 07/26/2024
+ms.date: 06/13/2025
 appliesto:
  - ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Exchange Online Protection</a>
  - ✅ <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,12 +37,28 @@ When admins or users submit items to Microsoft for analysis, we do the following
 [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). 
 
 > [!NOTE]
-> 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).
+> 
+> - 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).
+> - 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:
+>   - Files
+>   - URLs
+>   - Microsoft Teams messages
+>   - User submissions
+>
+>   AI-generated explanations are available for the following verdicts:
+>
+>   - Spam
+>   - Bulk
+>   - Threats found
+>   - No threats found
+>   - Unknown
+>
+>   If the AI-generated explanation is unavailable, the system falls back to the existing explanation as described in the following table.
 
 The following table describes the results of submissions to Microsoft:
 
 - **Status** indicates whether the previously described checks have been completed.
-- **Result** indicates the details that were generated during the analysis using the previously described checks
+- **Result** indicates the details that were generated during the analysis using the previously described checks.
 
 |Status|Result|Description|
 |---|---|---|

defender-office-365/user-tags-about.md

@@ -5,7 +5,7 @@ f1.keywords:
 ms.author: chrisda
 author: chrisda
 manager: deniseb
-ms.date: 06/09/2025
+ms.date: 06/13/2025
 audience: ITPro
 ms.topic: how-to
 ms.localizationpriority: medium
@@ -31,14 +31,12 @@ _User tags_ are identifiers for specific groups of users in [Microsoft Defender
 - **System tags**: Currently, [Priority account](/microsoft-365/admin/setup/priority-accounts) is the only type of system tag.
 - **Custom tags**: You create these types of tags.
 
-If your organization has Defender for Office 365 (included in your subscription or as an add-on), you can create custom user tags in addition to using the Priority account tag.
+If your organization has Defender for Office 365 (included in your subscription or as an add-on), you can create custom user tags in addition to using the Priority account tag:
 
-> [!NOTE]
-> Currently, you can only apply user tags to mailbox users.
->
-> Your organization can tag a maximum of 250 users using the Priority account system tag.
->
-> Each custom tag has a maximum of 999 users per tag and your organization can create up to 500 custom tags.
+- You can assign the Priority account tag to a maximum of 250 users.
+- You can create a maximum of 500 custom user tags.
+- You can assign a custom tag to a maximum of 10000 individual users.
+- If you assign a custom user tag to a group, the tag is applied to the first 999 group members (users). 
 
 This article explains how to configure user tags in the Microsoft Defender portal. You can also apply or remove the Priority account tag using the _VIP_ parameter on the [Set-User](/powershell/module/exchange/set-user) cmdlet in [Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell). No PowerShell cmdlets are available to manage custom user tags.
 
@@ -83,7 +81,7 @@ To see how user tags are part of the strategy to help protect high-impact user a
 
    - Select :::image type="icon" source="media/m365-cc-sc-create-icon.png" border="false"::: **Add members**. In the **Add members** flyout that opens, do any of the following steps to add individual users or groups in the **Search users and groups to add** box:
      - Click in the box and scroll through the list to select a user or group.
-     - Click in the box, start typing a name to filter the list, and then select the value below the box. select a user or group.
+     - Or, start typing a name to filter the list, and then select the value below the box. 
 
      To add more members, click in an empty area in the box and repeat the previous step.