skip to Main Content

Whitelist domain in Office 365 to bypass SPAM filtering

How to whitelist a domain in Office 365 and bypass spam filter? An issue that a lot of companies are facing is SPAM. We all have heard about it. However, sometimes you get a request to bypass specific domains. This article will teach you how to whitelist a domain in Office 365 to bypass SPAM filtering.

Allow domain to bypass SPAM filtering in Microsoft Office 365

To whitelist a domain in Office 365, follow these steps:

  1. Sign in to Microsoft 365 Defender portal
  2. Click on Policies & rules in the menu
  3. Choose Threat policies in the list
Whitelist domain in Office 365 to bypass SPAM filtering threat policies

Select Anti-spam inbound policy (Default).

Whitelist domain in Office 365 to bypass SPAM filtering anti-spam inbound policy

Scroll down and click on Edit allowed and blocked senders and domains.

Edit allowed and blocked senders and domains

There are two options to bypass SPAM filtering in Office 365:

  • Senders: Fill in the sender email address
  • Domains: Fill in the sender domain

In our example, we will click on Allow domains.

Whitelist domain in Office 365 to bypass SPAM filtering allow domains
  • Fill in the domain that you want to allow (whitelist)
  • Confirm the entered domain
  • Click Add domains
Whitelist domain in Office 365 to bypass SPAM filtering add domain

Click on Save.

Save settings

The domain is added to the Office 365 spam filter allow list. From now on, all the emails with that domain will not be marked as SPAM.

Read more: Verify DNS SRV records for Office 365 »

Conclusion

You learned how to whitelist a domain in Office 365 to bypass SPAM filtering. First, sign in to Office 365. After that, add the domain to the allowed domain section. From now on the domain will not be flagged as SPAM in Exchange Online Protection (EOP).

Did you enjoy this article? You may also like Add domain to Office 365 tenant. Don’t forget to follow us and share this article.

ALI TAJRAN

ALI TAJRAN

ALI TAJRAN is a passionate IT Architect, IT Consultant, and Microsoft Certified Trainer. He started Information Technology at a very young age, and his goal is to teach and inspire others. Read more »

This Post Has 2 Comments

  1. that is unfortunately not the best practice according to Microsoft. please google and you will find MS article that says transport rules with DKIM check is best practice.

Leave a Reply

Your email address will not be published.