Microsoft Exchange: Improved bulk detection and updated bulk complaint level recommendations [MC913443]

Microsoft Exchange: Improved bulk detection and updated bulk complaint level recommendations [MC913443]

Message ID: MC913443

As part of ongoing improvements to bulk email filtering in Microsoft Defender for Office | Exchange Online Protection, we are refining our detection capabilities by recalibrating and redistributing bulk senders across different bulk complaint levels (BCL). This would automatically make the current bulk thresholds slightly more aggressive. As a consequence, we are updating bulk threshold for standard preset policy to 7 from current value of 6. In response to general customer feedback around receiving more bulk email, we are keeping current default BCL threshold of 7 in default policy as is. Here’s what’s changing:

  • Redistribution for aggressive filtering: The new BCL distribution makes higher levels as aggressive as lower levels in previous version, enabling more precise targeting of unwanted bulk emails.
  • Updated BCL recommendations: The new recommended settings are 7 for default and standard, and 5 for strict to improve control over bulk filtering (replacing the previous levels of 7, 6, and 5).

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-October 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

Higher BCL levels are now more aggressive, reaching filtering precision similar to lower levels in the previous version.

If false positives occur, we recommend adjusting thresholds to higher BCL levels (including above default) and experimenting to find the right balance for your organization.

This feature is on by default, and admins can adjust their bulk threshold based on tenant preference.

[What you need to do to prepare:]

Admins should review and adjust their BCL settings using the bulk senders insight tool to align with the new recommendations, optimizing bulk filtering accordingly and managing false positives and false negatives. During and after the rollout, monitor email flows to assess the impact on bulk email management. If any false positives occur, test and experiment with higher BCL levels to ensure the updated thresholds effectively meet your organization’s filtering requirements.

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation.

Learn more: Bulk complaint level values – Microsoft Defender for Office 365 | Microsoft Learn (will be updated before rollout)

Source: Microsoft

Show 1 Comment

1 Comment

  1. Mike Rosoft

    Hey there, fellow tech enthusiasts!

    Exciting news from Microsoft Exchange – they’re shaking things up with an update to bulk email filtering in Microsoft Defender for Office | Exchange Online Protection. Picture this: recalibrating and redistributing bulk senders across different complaint levels to fine-tune those spam filters! ✨

    So, what’s the scoop? Well, the new changes will make the filtering more aggressive, like a ninja guarding your inbox against unwanted bulk emails. They’re cranking up the precision to tackle those pesky false positives and negatives.

    Now, admins, this is your time to shine! Get ready to adjust those Bulk Complaint Level (BCL) settings using the bulk senders insight tool. Experiment, tweak, and find that sweet spot for your organization. It’s like being a master chef, but instead of spices, you’re seasoning your email filters!

    And fear not, this update will roll out automatically – no need to break a sweat. Just keep an eye on your email flows, test those settings, and voila! You’re on your way to email filtering greatness.

    So, what do you think about these changes? Share your thoughts below, and let’s get the conversation going!

    Remember to stay tuned for more updates, and happy filtering! ✉️

Leave a Reply

Your email address will not be published. Required fields are marked *