Skip to content

Commit 509a6a4

Browse files
authored
Merge branch 'main' into 1c4245c1-ab45-4c2b-bb00-c5e57dc43c42_39
2 parents 379aa5c + fc4c381 commit 509a6a4

File tree

4 files changed

+25
-8
lines changed

4 files changed

+25
-8
lines changed

defender-office-365/quarantine-policies.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.collection:
1616
ms.custom:
1717
description: Admins can learn how to use quarantine policies to control what users are able to do to quarantined messages.
1818
ms.service: defender-office-365
19-
ms.date: 05/29/2025
19+
ms.date: 06/02/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>
@@ -751,10 +751,12 @@ The effect of **No access** permissions (admin only access) on user capabilities
751751
- **In quarantine notifications**: Users receive quarantine notifications, but the only available action is **Review message**.
752752

753753
> [!TIP]
754-
> To enable quarantine notifications while maintaining restricted access, [create a custom quarantine policy](#step-1-create-quarantine-policies-in-the-microsoft-defender-portal) with the following settings:
755754
>
756-
> - **Recipient message access** page: Select **Set specific access (Advanced)**, but leave **Select release action preference** and **Select additional actions recipients can take on quarantined messages** blank/unselected (equivalent to the value 0 for the _EndUserQuarantinePermissionsValue_ parameter on the **New-QuarantinePolicy** cmdlet [in Powershell](#create-quarantine-policies-in-powershell)).
757-
> - **Quarantine notification** page: Select **Enable** and then select **Don't include quarantined messages from blocked sender addresses** (default) or **Include quarantined messages from blocked sender addresses**.
755+
> - To enable quarantine notifications while maintaining restricted access, [create a custom quarantine policy](#step-1-create-quarantine-policies-in-the-microsoft-defender-portal) with the following settings:
756+
> - **Recipient message access** page: Select **Set specific access (Advanced)**, but leave **Select release action preference** and **Select additional actions recipients can take on quarantined messages** blank/unselected (equivalent to the value 0 for the _EndUserQuarantinePermissionsValue_ parameter on the **New-QuarantinePolicy** cmdlet [in Powershell](#create-quarantine-policies-in-powershell)).
757+
> - **Quarantine notification** page: Select **Enable** and then select **Don't include quarantined messages from blocked sender addresses** (default) or **Include quarantined messages from blocked sender addresses**.
758+
>
759+
> - If a sender is blocked and **Don't show blocked senders** is selected (default), messages from those senders are shown on the **Quarantine** page and are included in quarantine notifications when the **Sender address override reason** value is **None**. This behavior occurs because the messages were blocked due to reasons other than sender address overrides.
758760
759761
##### Limited access
760762

defender-office-365/tenant-allow-block-list-email-spoof-configure.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,14 +47,19 @@ This article describes how admins can manage entries for email senders in the Mi
4747

4848
- For blocking inbound and outbound email from a domain, any subdomains in that domain, and any email addresses in that domain, create the block entry using the syntax: `*.TLD`, where `TLD` can be any top-level domain, internal domain, or email address domain.
4949

50-
- For blocking inbound and outbound email from a sudomain in a domain and any email addresses in that subdomain, create the block entry using the syntax: `*.SD1.TLD`, `*.SD2.SD1.TLD`, `*.SD3.SD2.SD1.TLD`, etc. for internal domains and email address domains.
50+
- For blocking inbound and outbound email from a subdomain in a domain and any email addresses in that subdomain, create the block entry using the syntax: `*.SD1.TLD`, `*.SD2.SD1.TLD`, `*.SD3.SD2.SD1.TLD`, etc. for internal domains and email address domains.
5151

5252
- For details about the syntax for spoofed sender entries, see the [Domain pair syntax for spoofed sender entries](#domain-pair-syntax-for-spoofed-sender-entries) section later in this article.
5353

5454
- An entry should be active within 5 minutes.
5555

5656
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
57-
- [Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration** \> **Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Detection tuning (manage)** or **Authorization and settings/Security settings/Core security settings (read)**.
57+
- [Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration** \> **Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell):
58+
- *Add and remove entries from the Tenant Allow/Block List*: Membership assigned with the following permissions:
59+
- **Authorization and settings/Security settings/Detection tuning (manage)**
60+
- *Read-only access to the Tenant Allow/Block List*:
61+
- **Authorization and settings/Security settings/Read-only**.
62+
- **Authorization and settings/Security settings/Core Security settings (read)**.
5863
- [Exchange Online permissions](/exchange/permissions-exo/permissions-exo):
5964
- *Add and remove entries from the Tenant Allow/Block List*: Membership in one of the following role groups:
6065
- **Organization Management** or **Security Administrator** (Security admin role).

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

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,12 @@ This article describes how admins can manage entries for files in the Microsoft
5454
- An entry should be active within 5 minutes.
5555

5656
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
57-
- [Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration** \> **Exchange Online permissions** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Detection tuning (manage)** or **Authorization and settings/Security settings/Core security settings (read)**.
57+
- [Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration** \> **Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell):
58+
- *Add and remove entries from the Tenant Allow/Block List*: Membership assigned with the following permissions:
59+
- **Authorization and settings/Security settings/Detection tuning (manage)**
60+
- *Read-only access to the Tenant Allow/Block List*:
61+
- **Authorization and settings/Security settings/Read-only**.
62+
- **Authorization and settings/Security settings/Core Security settings (read)**.
5863
- [Exchange Online permissions](/exchange/permissions-exo/permissions-exo):
5964
- _Add and remove entries from the Tenant Allow/Block List_: Membership in one of the following role groups:
6065
- **Organization Management** or **Security Administrator** (Security admin role).

defender-office-365/tenant-allow-block-list-ip-addresses-configure.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,12 @@ This article describes how admins can manage entries for IPv6 addresses in the M
5252
- An entry should be active within 5 minutes.
5353

5454
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
55-
- [Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration** \> **Exchange Online permissions** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Detection tuning (manage)** or **Authorization and settings/Security settings/Core security settings (read)**.
55+
- [Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration** \> **Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell):
56+
- *Add and remove entries from the Tenant Allow/Block List*: Membership assigned with the following permissions:
57+
- **Authorization and settings/Security settings/Detection tuning (manage)**
58+
- *Read-only access to the Tenant Allow/Block List*:
59+
- **Authorization and settings/Security settings/Read-only**.
60+
- **Authorization and settings/Security settings/Core Security settings (read)**.
5661
- [Exchange Online permissions](/exchange/permissions-exo/permissions-exo):
5762
- _Add and remove entries from the Tenant Allow/Block List_: Membership in one of the following role groups:
5863
- **Organization Management** or **Security Administrator** (Security admin role).

0 commit comments

Comments
 (0)