Skip to content

Commit 83ab3c3

Browse files
Merge pull request #4571 from MicrosoftDocs/main
[AutoPublish] main to live - 07/24 13:32 PDT | 07/25 02:02 IST
2 parents b322f75 + 6895557 commit 83ab3c3

File tree

2 files changed

+8
-5
lines changed

2 files changed

+8
-5
lines changed

defender-office-365/email-authentication-spf-configure.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ f1.keywords:
55
ms.author: chrisda
66
author: chrisda
77
manager: deniseb
8-
ms.date: 04/15/2025
8+
ms.date: 07/24/2025
99
audience: ITPro
1010
ms.topic: how-to
1111

@@ -111,10 +111,10 @@ v=spf1 ip4:192.168.0.10 ip4:192.168.0.12 include:spf.protection.outlook.com -all
111111
112112
- `~all` (soft fail): Sources not specified in the SPF TXT record _probably_ aren't authorized to send mail for the domain, so the messages should be accepted but marked. What actually happens to the message depends on the destination email system. For example, the message might be quarantined as spam, delivered to the Junk Email folder, or delivered to the Inbox with an identifier added to the Subject or message body.
113113

114-
Because we also recommend DKIM and DMARC for Microsoft 365 domains, the differences between `-all` (hard fail) and `~all` (soft fail) are effectively eliminated (DMARC treats either result as an SPF failure). DMARC uses SPF to confirm the domains in the MAIL FROM and From addresses align _and_ the message came from a valid source for the From domain.
114+
> [!NOTE]
115+
> DMARC treats `-all` (hard fail) and `~all` (soft fail) as SPF failures. But the DMARC policy is effectively ignored for SPF `~all` failures if the messages don't also contain DKIM signatures. We recommend `-all` so DMARC can act on messages that fail SPF if the messages also lack DKIM signatures.
115116
116-
> [!TIP]
117-
> `?all` (neutral) is also available to suggest no specific action on messages from unidentified sources. This value is used for testing, and we don't recommend this value in production environments.
117+
- `?all` (neutral): Suggests no specific action on messages from unidentified sources. This value is used for testing, and we don't recommend this value in production environments.
118118

119119
Important points to remember:
120120

defender-office-365/submissions-outlook-report-messages.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
description: Learn how to report phishing and suspicious emails in supported versions of Outlook using the built-in Report button.
1515
ms.service: defender-office-365
1616
search.appverid: met150
17-
ms.date: 02/24/2025
17+
ms.date: 07/24/2025
1818
appliesto:
1919
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Exchange Online Protection</a>
2020
- ✅ <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>
@@ -62,6 +62,9 @@ Admins configure user reported messages to go to a specified reporting mailbox,
6262
- Shared mailboxes require Send As or Send On Behalf permission for the user.
6363
- Other mailboxes require Send As or Send On Behalf permission _and_ Read and Manage permissions for the delegate.
6464

65+
> [!NOTE]
66+
> If the previously described permissions aren't granted, reported messages aren't shown on the [User reported](submissions-admin.md#view-user-reported-messages-to-microsoft) tab. Reported messages are still quarantined to protect the mailbox from phishing attacks.
67+
6568
### Use the built-in Report button in Outlook to report junk and phishing messages
6669

6770
- Users can report a message as junk from the Inbox or any email folder other than Junk Email folder.

0 commit comments

Comments
 (0)