Skip to content

Commit 790e7af

Browse files
authored
Fix date format and clarify filtering note
1 parent 5fecb60 commit 790e7af

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

defender-office-365/connection-filter-policies-configure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.custom:
1818
- seo-marvel-apr2020
1919
description: Admins can learn how to configure connection filtering in Microsoft 365 to allow or block emails from email servers.
2020
ms.service: defender-office-365
21-
ms.date: 07/03/2025
21+
ms.date: 009/05/2025
2222
appliesto:
2323
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Default email protections for cloud mailboxes</a>
2424
- ✅ <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>
@@ -194,7 +194,7 @@ For example, the source email server 192.168.1.25 sends email from the domains c
194194
### Scenarios where messages from sources in the IP Allow List are still filtered
195195

196196
> [!NOTE]
197-
> These scenarios apply to all environments (standalone, hybrid, multi-geo, and cross-forest), and the filtering behavior is based on security checks such as malware detection, phishing protection, or transport rules, not on the deployment model.
197+
> These scenarios apply to all environments: standalone, hybrid, multi-geo, and cross-forest. Filtering behavior is based on security checks (for example, malware detection, phishing protection, or mail flow rules, not on the deployment model.
198198
199199
Messages from an email server in your IP Allow List are still subject to spam filtering in the following scenarios:
200200

0 commit comments

Comments
 (0)