Skip to content

Commit 1c20b57

Browse files
authored
Merge pull request #1669 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/defender-docs (branch public)
2 parents 42fcfa1 + 65b5609 commit 1c20b57

File tree

2 files changed

+7
-11
lines changed

2 files changed

+7
-11
lines changed

defender-office-365/outbound-spam-high-risk-delivery-pool-about.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,8 +72,6 @@ The forwarded or relayed message should meet one of the following criteria to av
7272
- SPF passes when the message comes to Microsoft 365.
7373
- DKIM on the sender domain passes when the message comes to Microsoft 365.
7474

75-
You can tell that a message was sent via the relay pool by looking at the outbound server IP (the relay pool is in the 40.95.0.0/16 range).
76-
7775
In cases where we can authenticate the sender, we use Sender Rewriting Scheme (SRS) to help the recipient email system know that the forwarded message is from a trusted source. You can read more about how that works and what you can do to help make sure the sending domain passes authentication in [Sender Rewriting Scheme (SRS) in Office 365](/office365/troubleshoot/antispam/sender-rewriting-scheme).
7876

7977
For DKIM to work, make sure you enable DKIM for sending domain. For example, fabrikam.com is part of contoso.com and is defined in the accepted domains of the organization. If the message sender is [email protected], DKIM needs to be enabled for fabrikam.com. you can read on how to enable at [Use DKIM to validate outbound email sent from your custom domain](email-authentication-dkim-configure.md).

defender-office-365/safe-links-about.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ audience: Admin
99
ms.topic: overview
1010
f1_keywords:
1111
- '197503'
12-
ms.date: 07/18/2024
12+
ms.date: 10/22/2024
1313
ms.localizationpriority: medium
1414
ms.collection:
1515
- Strat_O365_IP
@@ -55,15 +55,13 @@ Safe Links protection by Safe Links policies is available in the following locat
5555
For more information about Safe Links protection for email messages, see the [Safe Links settings for email messages](#safe-links-settings-for-email-messages) section later in this article.
5656

5757
> [!NOTE]
58-
> Safe Links doesn't work on mail-enabled public folders.
5958
>
60-
> Safe Links doesn't provide protection for URLs in Rich Text Format (RTF) email messages.
61-
>
62-
> Safe Links supports only HTTP(S) and FTP formats.
63-
>
64-
> Safe Links no longer wraps URLs pointing to SharePoint Online sites. SharePoint URLs are still processed by the Safe Links service. This change doesn't cause a degradation in the protection a tenant receives. It's intended to improve the performance of loading SharePoint URLs.
65-
>
66-
> Using another service to wrap links before Defender for Office 365 might prevent Safe Links from process links, including wrapping, detonating, or otherwise validating the "maliciousness" of the link.
59+
> - Safe Links doesn't work on mail-enabled public folders.
60+
> - Safe Links doesn't provide protection for URLs in Rich Text Format (RTF) email messages.
61+
> - Safe Links supports only HTTP(S) and FTP formats.
62+
> - Safe Links ignores S/MIME signed messages.
63+
> - Safe Links no longer wraps URLs pointing to SharePoint Online sites. SharePoint URLs are still processed by the Safe Links service. This change doesn't cause a degradation in the protection a tenant receives. It's intended to improve the performance of loading SharePoint URLs.
64+
> - Using another service to wrap links before Defender for Office 365 might prevent Safe Links from process links, including wrapping, detonating, or otherwise validating the "maliciousness" of the link.
6765
6866
- **Microsoft Teams**: Safe Links protection for links in Teams conversations, group chats, or from channels.
6967

0 commit comments

Comments
 (0)