An integrated threat protection solution designed to detect, investigate, and respond to cyber threats across Microsoft 365 services.
What you're seeing usually comes from how outbound spam policies fall through. The default outbound policy applies to all senders and can't have exclusions. Only custom policies can be scoped. Protection stops at the first (highest priority) policy that matches the sender. So if you excluded the mailbox from your high-volume custom policy, it drops down to the default policy, whose lower limits restrict it again.
The cleaner setup is to give that mailbox its own policy:
- In the Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Anti-spam.
- Create a new outbound spam policy that applies only to that mailbox.
- Set its recipient limits to cover the mailbox's real volume (0 means "use the service defaults", and the maximum is 10,000).
- For the action when the user exceeds the limits, pick No action, alert only if you never want it blocked, or keep a restriction and rely on the higher limits.
- Move this policy to priority 0, above your high-volume policy.
- If the mailbox is still on Restricted entities (
https://security.microsoft.com/restrictedusers), release it there.
Keep in mind that Exchange Online's own service-wide sending limits still apply. For real bulk mailings, a dedicated bulk email service is the safer route.
Roughly how many recipients a day does this mailbox send to?
If the mailbox stops getting restricted, please consider accepting it as the answer. If it's still added to Restricted entities after this, let me know and I'll be happy to keep helping.
Reference: