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-admin-manage-messages-files.md #94

Merged
merged 3 commits into from
Aug 30, 2024
Merged

Update quarantine-admin-manage-messages-files.md #94

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
abf2e8e
Update quarantine-admin-manage-messages-files.md
faoquong Aug 30, 2024
d35a97d
Update quarantine-admin-manage-messages-files.md
denisebmsft Aug 30, 2024
293ff07
Merge branch 'public' into patch-3
denisebmsft Aug 30, 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: 2 additions & 2 deletions defender-office-365/quarantine-admin-manage-messages-files.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ ms.custom:
- seo-marvel-apr2020
description: Admins can learn how to view and manage quarantined messages for all users in Exchange Online Protection (EOP). Admins in organizations with Microsoft Defender for Office 365 can also manage quarantined files in SharePoint Online, OneDrive for Business, and Microsoft Teams.
ms.service: defender-office-365
ms.date: 08/07/2024
ms.date: 08/30/2024
appliesto:
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Exchange Online Protection</a>
- ✅ <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>
Expand Down Expand Up @@ -215,7 +215,7 @@ In the details flyout that opens, the following information is available:
- **Not yet released to**, **Released to**, and/or **Released by**: Depending on the state of the message, one or more of the following values might be available:
- **Not yet released to**: Email addresses of recipients that the message hasn't been released to.
- **Released to**: Email addresses of recipients that the message has been released to.
- **Released by**: The admin that released the message using the format: `<email address of admin who released the message> released for <recipient>`. For example, `[email protected] released to [email protected]`.
- **Released by**: The admin that released the message using the format: `<email address of admin who released the message> released for <recipient>`. For example, `[email protected] released to [email protected]`. If the end user releases the message, it shows the end user's SMTP address. If the release is carried out by the system, it says, "System released". If the release is not carried by an admin, an end user, or the system, it defaults to "Admin."

The rest of the details flyout contains the **Delivery details**, **Email details**, **URLs**, and **Attachments** sections that are part of the _Email summary panel_. For more information, see [The Email summary panel](mdo-email-entity-page.md#the-email-summary-panel).

Expand Down