Skip to content

Commit 104b734

Browse files
Merge pull request #4658 from MicrosoftDocs/main
[AutoPublish] main to live - 08/04 13:33 PDT | 08/05 02:03 IST
2 parents 7822787 + 1cb2aa6 commit 104b734

29 files changed

+402
-68
lines changed

defender-office-365/configure-junk-email-settings-on-exo-mailboxes.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.collection:
1616
- tier2
1717
description: Admins can learn how to configure the junk email settings in Exchange Online mailboxes. Many of these settings are available to users in Outlook or Outlook on the web.
1818
ms.service: defender-office-365
19-
ms.date: 07/03/2025
19+
ms.date: 07/31/2025
2020
appliesto:
2121
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Default email protections for cloud mailboxes</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>
@@ -33,9 +33,11 @@ But, there are also specific anti-spam settings that admins can configure on ind
3333

3434
- **Deliver messages to the Junk Email folder based on anti-spam policies**: When an anti-spam policy is configured with the action **Move message to Junk Email folder** for a spam filtering verdict, the message is delivered to the Junk Email folder of the mailbox. For more information about spam filtering verdicts in anti-spam policies, see [Configure anti-spam policies](anti-spam-policies-configure.md). Similarly, if zero-hour auto purge (ZAP) determines that a delivered message is spam or phishing, the message is moved to the Junk Email folder for **Move message to Junk Email folder** spam filtering verdict actions. For more information about ZAP, see [Zero-hour auto purge (ZAP) in Exchange Online](zero-hour-auto-purge.md).
3535

36-
- **Junk email settings that users configure for themselves in Outlook or Outlook on the web**: The _safelist collection_ is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list on each mailbox. The entries in these lists determine whether the message is moved to the Inbox or the Junk Email folder. Users can configure the safelist collection for their own mailboxes in Outlook or Outlook on the web (formerly known as Outlook Web App). Admins can configure the safelist collection on any user's mailbox.
36+
- **Junk email settings that users configure for themselves in Outlook or Outlook on the web**: The _safelist collection_ is the Safe Senders list, the Safe Recipients list, and the Blocked Senders list on each mailbox. The entries in these lists determine whether the message is delivered to the Inbox or the Junk Email folder. Users can configure the safelist collection for their own mailboxes in Outlook or Outlook on the web (formerly known as Outlook Web App or OWA). Admins can configure the safelist collection on any user's mailbox.
3737

38-
Microsoft 365 is able to deliver messages to the Junk Email folder based on the spam filtering verdict action **Move message to Junk Email folder** and the Blocked Senders list in the mailbox, and prevent messages from being delivered to the Junk Email folder based on the Safe Senders list on the mailbox.
38+
Microsoft 365 adds the header `X-Forefront-Antispam-Report: SFV:BLK` to incoming messages from senders in a user's Blocked Senders list, and any future messages from that sender are classified as spam. The message is delivered to the user's Junk Email folder or to quarantine based on the action configured in the applicable anti-spam policy (our [recommended action](recommended-settings-for-eop-and-office365.md#anti-spam-policy-settings) is **Move message to Junk Email folder**).
39+
40+
If the sender is a user's Safe Senders list, the message is delivered to their Inbox.
3941

4042
Admins can use Exchange Online PowerShell to configure entries in the safelist collection on mailboxes (the Safe Senders list, the Safe Recipients list, and the Blocked Senders list).
4143

defender-office-365/reports-mdo-email-collaboration-dashboard.md

Lines changed: 1 addition & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.collection:
1818
description: Admins can learn about the information on the Microsoft Defender for Office 365 Overview dashboard in the Microsoft Defender portal.
1919
ms.custom:
2020
ms.service: defender-office-365
21-
ms.date: 07/16/2025
21+
ms.date: 08/01/2025
2222
appliesto:
2323
- ✅ <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>
2424
- ✅ <a href="https://learn.microsoft.com/defender-xdr/microsoft-365-defender" target="_blank">Microsoft Defender XDR</a>
@@ -33,7 +33,6 @@ The information on the **Overview** page is organized into the following areas:
3333
- [Defender for Office 365 summary](#defender-for-office-365-summary)
3434
- [Optimize section](#optimize-section)
3535
- [Risky allows section](#risky-allows-section)
36-
- [Compare solutions section](#compare-solutions-section)
3736
- [Insights section](#insights-section)
3837

3938
For the permissions required to view the dashboard and reports, see [What permissions are needed to view these reports?](reports-email-security.md#what-permissions-are-needed-to-view-these-reports).
@@ -187,42 +186,6 @@ Select **Review rules** to go to the **Rules** page in the Exchange admin center
187186

188187
:::image type="content" source="media/email-collab-overview-risky-allows-etrs.png" alt-text="Screenshot of the Exchange transport rules card in the Risky allows section of the Email & collaboration overview report page." lightbox="media/email-collab-overview-risky-allows-etrs.png":::
189188

190-
## Compare solutions section
191-
192-
The information in the **Compare solutions** section is described in the following subsections.
193-
194-
### Email detections card
195-
196-
<!--- https://go.microsoft.com/fwlink/?linkid=2323918--->
197-
198-
The graph on the **Email detections** shows Microsoft and non-Microsoft detections as part of [ICES Vendor Ecosystem integration](mdo-ices-vendor-ecosystem.md):
199-
200-
- **Defender mail flow detections**
201-
- **Defender post-delivery detections**
202-
- **Non-Microsoft post-delivery detections**
203-
- **Duplicate detections Duplicate post-delivery detections**
204-
205-
Hover over a category in the chart to see the number of messages in each category for the review period selected.
206-
207-
:::image type="content" source="media/email-collab-overview-compare-solutions-email-detections.png" alt-text="Screenshot of the Email detections card in the Compare solutions section of the Email & collaboration overview report page." lightbox="media/email-collab-overview-compare-solutions-email-detections.png":::
208-
209-
### Non-Microsoft detections card
210-
211-
<!--- https://go.microsoft.com/fwlink/?linkid=2324014 --->
212-
213-
The graphs on the **Non-Microsoft detections** show the following information for non-Microsoft detections as part of [ICES Vendor Ecosystem integration](mdo-ices-vendor-ecosystem.md):
214-
215-
- **Post delivery detections** graph:
216-
- **Malware**
217-
- **Phish**
218-
- **Spam**
219-
220-
Hover over a category in the chart to see the number of messages in each category for the review selected.
221-
222-
- **Efficacy** graph: Shows the unique detections by the non-Microsoft service as a percentage of the total detections by Defender for Office 365.
223-
224-
:::image type="content" source="media/email-collab-overview-compare-solutions-non-microsoft.png" alt-text="Screenshot of the Non-Microsoft detections card in the Compare solutions section of the Email & collaboration overview report page." lightbox="media/email-collab-overview-compare-solutions-non-microsoft.png":::
225-
226189
## Insights section
227190

228191
The information in the **Insights** section is described in the following subsections.

defender-office-365/tenant-allow-block-list-teams-domains-configure.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
- tier1
1616
description: Admins can learn how to block domains in Microsoft Teams using the Tenant Allow/Block List.
1717
ms.service: defender-office-365
18-
ms.date: 07/29/2025
18+
ms.date: 08/04/2025
1919
appliesto:
2020
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Default email protections for cloud mailboxes</a>
2121
- ✅ <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>
@@ -26,6 +26,9 @@ appliesto:
2626

2727
[!INCLUDE [MDO Trial banner](../includes/mdo-trial-banner.md)]
2828

29+
> [!NOTE]
30+
> The feature described in this article is currently in Preview, isn't available in all organizations, and is subject to change.
31+
2932
In all organizations with Microsoft Teams and cloud mailboxes, admins can create and manage block entries for domains in Microsoft Teams using the Tenant Allow/Block List. These blocked domain entries also appear on the **Organization settings** tab of the **External access** page in the Microsoft Teams admin center at <https://admin.teams.microsoft.com/company-wide-settings/external-communications> in the **Teams and Skype for Business users in external organizations** section:
3033

3134
:::image type="content" source="media/tenant-allow-block-list-teams-domains.png" alt-text="Screenshot of the External access page in the Microsoft Teams admin center showing blocked domains." lightbox="media/tenant-allow-block-list-teams-domains.png":::
@@ -46,6 +49,8 @@ This article describes how security admins can manage entries for blocked domain
4649
- **Block only specific external domains**
4750
- **Allow my security team to manage blocked domains** must be :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **On**.
4851

52+
- The maximum number of domain block entries for Microsoft Teams is 4,000.
53+
4954
- Block entries for domains in Teams never expire.
5055

5156
- An entry should be active within 5 minutes.
@@ -65,15 +70,11 @@ This article describes how security admins can manage entries for blocked domain
6570

6671
2. On the **Tenant Allow/Block Lists** page, select the **Teams domains** tab.
6772

68-
3. On the **Teams domains** tab, select :::image type="icon" source="media/m365-cc-sc-create-icon.png" border="false"::: **Add**, and then select **Block**.
69-
70-
4. In the **Block external domains in Teams** flyout that opens, configure the following settings:
71-
72-
- **Add domains**: Enter one domain per line, up to a maximum of 20.
73+
3. On the **Teams domains** tab, select :::image type="icon" source="media/m365-cc-sc-create-icon.png" border="false"::: **Block**.
7374

74-
5. When you're finished in the **Block external domains in Teams** flyout, select **Add**.
75+
4. In the **Block external domains in Teams** flyout that opens, enter up to 20 domains separated by commas or line breaks, and then select **Add**.
7576

76-
Back on the **Teams domains** tab, the entry is listed. After a few minutes, the blocked domain also appears on the **Organization settings** tab of the **External access** page in the Microsoft Teams admin center at <https://admin.teams.microsoft.com/company-wide-settings/external-communications>.
77+
Back on the **Teams domains** tab, the domain block entries are listed. After a few minutes, the blocked domains also appear on the **Organization settings** tab of the **External access** page in the Microsoft Teams admin center at <https://admin.teams.microsoft.com/company-wide-settings/external-communications>.
7778

7879
## View block entries for domains in Teams in the Tenant Allow/Block List
7980

0 commit comments

Comments
 (0)