Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Microsoft 365 Foundations v7.0.0 · 2.1.6

Exchange Online spam policies should notify administrators

  • E3 Level 1
  • Microsoft Defender
  • Automated check

This check looks at the outbound spam policy in Exchange Online and whether it sends an alert to administrators when a mailbox is blocked or limited for sending spam. The safe setting is to have the policy copy or notify a named admin mailbox, so a compromised account is noticed quickly.

Why it matters

When a mailbox starts sending large volumes of junk, the usual cause is a stolen password or a rogue forwarding rule. Microsoft's outbound spam filtering limits or blocks such senders on its own, but a block that nobody hears about leaves the user locked out and the root cause unexamined.

Notification settings in the outbound spam policy let you tell your admins at the moment the service acts. That turns a silent block into a ticket someone can investigate the same day.

Source: Microsoft Learn, Configure outbound spam filtering in EOP.

How to check it yourself

In the Microsoft Defender portal open Email & collaboration > Policies & rules > Threat policies > Anti-spam, select the outbound policy and read the Notifications section. Look for the option that sends a copy of suspicious outbound messages to specific people, and the option that notifies specific people when a sender is blocked.

A read-only look with Exchange Online PowerShell:

Connect-ExchangeOnline
Get-HostedOutboundSpamFilterPolicy |
  Select-Object Name,NotifyOutboundSpam,NotifyOutboundSpamRecipients,BccSuspiciousOutboundMail,BccSuspiciousOutboundAdditionalRecipients

If the notify flag is false or the recipient lists are empty, no administrator is told when the service acts.

How to fix it

Portal steps:

  • Open Threat policies > Anti-spam in the Microsoft Defender portal and select the outbound spam policy.
  • Choose Edit protection settings.
  • Under Notifications, turn on the notification for blocked senders and add a monitored shared mailbox or distribution list, not one person's inbox.
  • Save the policy.

The same change with PowerShell, after you have tested it on a non-production policy:

Set-HostedOutboundSpamFilterPolicy -Identity Default `
  -NotifyOutboundSpam $true `
  -NotifyOutboundSpamRecipients secops@contoso.example

The address above is an invented example. ConfigCobra never makes these changes for you: it reports the finding and suggests the steps.

What changes when you fix it

Nothing changes for ordinary users and no mail is blocked or delayed by this setting. The people on the recipient list start receiving alert emails when the service restricts a sender, so choose a mailbox that someone reads and agree who follows up.

Expect the first alerts to come from genuine bulk senders such as newsletters or scanners, and allow time to tell those apart from real compromises.

Write down in your runbook who reads the alert mailbox and what they do first, for example resetting the password and checking the account's forwarding rules.

Included in

BenchmarkCIS IDProfile
CIS Microsoft 365 Foundations v7.0.02.1.6E3 Level 1

Check this on your Microsoft 365

ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial