Skip to content

Commit 1fe63f4

Browse files
acro fix
1 parent 850f7fb commit 1fe63f4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

defender-office-365/remediate-malicious-email-delivered-office-365.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ Open any remediation item to view details about it, including its remediation na
122122
> [!TIP]
123123
> For best results, remediation should be done in batches of 50,000 or fewer.
124124
125-
Only remediable email messages are acted on during remediation. Nonremediable emails can't be remediated by Microsoft 365, becayse they aren't stored in cloud mailboxes.
125+
Only remediable email messages are acted on during remediation. Nonremediable emails can't be remediated by Microsoft 365, because they aren't stored in cloud mailboxes.
126126

127127
Admins can take actions on emails in quarantine if necessary, but those emails expire out of quarantine if they're not manually purged. By default, emails quarantined because of malicious content aren't accessible by users, so security personnel don't have to take any action to get rid of threats in quarantine. If the emails are on-premises or external, the user can be contacted to address the suspicious email. Or the admins can use separate email server/security tools for removal. These emails can be identified by applying the *delivery location = on-premises* external filter in Explorer. For failed or dropped email, or email not accessible by users, there isn't any email to mitigate, since these mails don't reach the mailbox.
128128

0 commit comments

Comments
 (0)