

Microsoft's URL Detonation Reputation filtering, a component of their email security system, has recently been causing significant issues for many organisations and individuals.
This article explores the challenges faced by innocent victims of this overzealous filtering mechanism and discusses potential solutions.
URL Detonation Reputation is a security feature designed to protect users from malicious email links. However, it has been flagging legitimate websites and URLs as potential phishing threats, leading to widespread email disruptions.
The overreach of URL Detonation Reputation filtering has led to severe consequences for many organisations:
While there is no one-size-fits-all solution, here are some steps that affected organisations can take:
You can use the admin submission process to report false positives to Microsoft. This can help improve the filtering system's accuracy over time.
To create a temporary override signal, add affected URLs to the Tenant Allow/Block List (TABL). This can help bypass the filters while Microsoft reviews the submission.
Open a support ticket with Microsoft to escalate the issue. Persistence may be necessary, as resolution times can vary.
As a temporary measure, create mail flow rules to bypass Spam Confidence Level (SCL) filtering for specific URLs. However, this should be done cautiously and only for trusted domains.
Ensure that SPF, DKIM, and DMARC are correctly configured for your domain. While this may not directly solve URL reputation issues, it can improve overall email deliverability.
For legitimate phishing simulations or similar scenarios, use the Advanced Delivery options in Microsoft 365 Defender to whitelist specific IPs and domains.
While Microsoft's URL Detonation Reputation filtering aims to protect users from phishing attacks, its current implementation is causing significant challenges for many organisations. Microsoft must improve its accuracy as the system evolves and provide more transparency to affected users. In the meantime, organisations must remain vigilant, proactively address false positives, and work closely with Microsoft support to resolve persistent issues.