Microsoft 365: Managing Spam Email
Your mailbox is safeguarded by Microsoft’s “Standard protection” preset security policy. This policy is designed to identify and manage spam, phishing, and malware messages effectively. Depending on the confidence level with which a message is identified as spam or potentially harmful, the following actions may occur:
High Level of Confidence: If the policy is highly confident that a message is spam or harmful, it will not be accepted by the email system. The sender will receive a non-deliverable message, if the senders email system supports this.
Medium High Level of Confidence: Messages flagged with medium-high confidence of being harmful, will not be delivered to your mailbox and instead, will be stored in quarantine.
Standard Level of Confidence: Messages identified with a standard level of confidence as being spam will be delivered to your Junk Email folder.
Reviewing Your Quarantine
To review messages that have been quarantined:
- Log into the Microsoft 365 Security Portal (https://security.microsoft.com).
- Select “Review” under “Email & Collaboration”
- Choose “Quarantine” to view the Quarantine page, where quarantined messages are displayed.
Quarentine Notifications
The system is set up to send spam notifications every 4 hours, which is the most frequent interval supported by the Microsoft 365 system.
Managing Safe and Blocked Senders or Domains
You have the option to customise settings to block or allow specific senders or domains. These settings will apply only to your mailbox.
- Log into https://www.office.com/ and click on the “Outlook” icon.
- In Outlook, click the settings icon (gear symbol).
- From the settings menu, select “View all Outlook settings”.
- In the Settings pop-up window, navigate to “Junk email”.
- Here, you can manage your allowed (safe) and blocked senders and domains.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article