Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update quarantine-faq.yml #138

Merged
merged 2 commits into from
Nov 6, 2024
Merged

Update quarantine-faq.yml #138

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c90fd4f
Update quarantine-faq.yml
faoquong Nov 6, 2024
068367c
Update quarantine-faq.yml
chrisda Nov 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions defender-office-365/quarantine-faq.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,8 @@ sections:

- Some mail flow rules that quarantined a message can cause the released message to be quarantined again.

- Inform admins that routing released quarantine messages to onpremises recipients can cause messages to lose anti-spam headers, which makes the messages land in quarantine again after release.

Admins can use [message trace](message-trace-defender-portal.md) to determine if a released message was delivered to the recipient's Inbox.

- question: |
Expand Down Expand Up @@ -219,6 +221,8 @@ sections:
>
> For messages quarantined by zero-hour auto purge (ZAP), quarantine notifications are generated based on when the message was quarantined, not when the message was delivered to the mailbox.

You can also set up quarantine notifications for internal (intra-organization) messages only in quarantine policies.

- question: |
Why aren't users receiving notifications about their quarantined messages?
answer: |
Expand Down