TL;DR: Residual malware that Microsoft 365 let through was blocked with zero false positives in Virus Bulletin's first VB ESA - M365 certification, according to Coro. Email controls need proof against what reaches the inbox after native filtering, not just standalone block rates.
Editorial analysis by NHI Mgmt Group, based on content published by Coro: “Coro Email Security Earns VB ESA M365 Certification”.
By the numbers:
- Virus Bulletin ran a continuous stream of live email through a Microsoft 365 tenant over 17 days.
- Coro Email Security recorded zero false positives across the 371 legitimate messages that reached it.
- Coro Email Security caught 99 of the 108 spam messages that made it past Microsoft 365's native filtering.
Key questions
Q: Why do false negatives matter more than false positives in email security operations?
A: False negatives matter because they let malicious messages reach users and create real compromise risk, including credential theft and account takeover.
Q: What breaks when an email security layer is tuned too aggressively?
A: Business communications break first.
Q: How should security teams evaluate email protection when Microsoft 365 is part of the stack?
A: They should test whether all inbound mail is routed through the same inspection path, then compare the same threat set across products and time periods.
Practitioner guidance
- Define success as residual-risk reduction Measure email security products against the messages Microsoft 365 lets through, not against all inbound mail, and require that metric in proof-of-value testing.
- Validate false-positive tolerance with live traffic Test legitimate mail handling using real business samples, then set an acceptance threshold that reflects the support burden your team can absorb.
- Review delegated tenant permissions If the product connects through API, document the mailbox scopes, remediation actions, and audit trail required for least-privilege operation.
Bottom line: The core issue is not whether Microsoft 365 filters email, but how much harmful traffic still reaches users after native controls have already done their job.
Glossary terms: Incremental Detection Rate, False Positive, Residual Risk, API-Based Email Security
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Residual-risk testing is the right yardstick for email security in Microsoft 365. The meaningful question is not how many messages a product blocks in isolation, but what it adds after native filtering has already done its work. That shifts evaluation from headline detection claims to the much harder operational question of whether the layered stack changes inbox exposure in practice. Practitioners should treat incremental detection as the metric that matches real deployment conditions.
A few things that frame the scale:
- Security researchers tracked consent phishing campaigns affecting 900 tenants and 3,000 user accounts in 2025.
A question worth separating out:
Q: Should organisations rely on Microsoft 365 native filtering alone?
A: Not if they face phishing or malware risk that survives the base layer. Native filtering is essential, but organisations should assess whether a second control materially reduces inbox exposure while keeping legitimate mail flowing. The right decision depends on residual threat volume and the team’s tolerance for operational overhead.
👉 Read our full editorial: Independent testing shows layered email security can catch residual malware