Mailinblack enhances its email security solution, Protect, by introducing a native API deployment for Microsoft 365, eliminating the need to alter MX records or DNS configurations. This seamless integration reduces installation time to just minutes and introduces after-delivery remediation capabilities that were previously absent from its historical architecture. The French cybersecurity provider maintains its pre-delivery analysis, unlike several competing models that inspect emails only after they have been delivered.
Since its inception in 2003, Protect has filtered incoming emails by redirecting MX records upstream. The new direct integration with Microsoft 365 shifts this connection point, placing it directly within the email environment. This technical shift paves the way for new capabilities, notably the ability to delete already delivered emails.
Two Connection Pathways for Email Management
The MX record redirection remains relevant in hybrid environments or those utilizing multiple email providers, where it serves as a shared filter for all incoming flows. For a uniform Microsoft 365 setup, the native API integration fulfills the need for a quicker deployment and simplified management, without altering routing records.
“Our clients can now choose between traditional MX redirection and a native API 365 deployment. In both cases, the level of protection remains identical,” said Justine De Ubeda, Product Director at Mailinblack. The vendor claims that protection equivalence between the two modes will be tested during pilot phases, given that the two architectures intercept emails at different points in the delivery chain.
Pre-Delivery Analysis and After-Delivery Remediation
The critical distinction lies in the timing of the inspection, which is significant considering current threats. Email is still the primary entry point for attacks, from targeted phishing to ransomware dissemination, with the time between receiving a compromised message and user interaction often measured in mere seconds. Several competing API integrations, known as Subscription or Journaling modes, analyze emails after they’ve been deposited into the user’s mailbox. Mailinblack asserts that its Inline API retains upstream analysis, inspecting each message prior to delivery. This preemptive verification eliminates any exposure window to malicious messages, a unique advantage in a threat landscape where swift response is crucial.
The new model also introduces a capability absent from the MX architecture: after-delivery remediation. IT teams can delete emails that have already been distributed upon identifying a threat or addressing a false negative that slipped through the filter. The same interface allows for the banning of an entire sender or domain for the organization with a single action. This post-distribution control addresses a known blind spot of upstream filters, which cannot act on messages once delivered, bringing email protection practices closer to detection and response protocols already employed in security operations centers, where the ability to rectify after the fact is as critical as initial filtering.
A Deployment Incentive for Managed Service Providers
The reduced installation time, cut from several hours to just minutes according to Mailinblack, targets not only direct clients but also Managed Service Providers (MSPs) who manage multiple client environments simultaneously. These providers bear the costs associated with routing manipulations during each deployment. A native API integration that bypasses the MX switch lightens this operational burden, facilitating scalability across client portfolios.
This approach highlights the Marseille-based vendor’s strategy, claiming protection for around 25,000 organizations and over two million users with solutions developed and hosted in France, leveraging a broad network of resellers and integrators for distribution. By aligning with the deployment method expected by Microsoft 365 environments, Mailinblack aims to reduce friction that could otherwise divert partners to competing solutions with native integrations. This commercial objective intertwines with the technical one, as expedited deployment becomes both a selling point and a practical advantage.
The Impact of Remediation on Incident Response for CISOs
Beyond the convenience of deployment, the capability for after-delivery remediation shifts incident response posture regarding email channels. Previously, a malicious message that bypassed filters and was already delivered required manual intervention for each affected workstation or reliance on Microsoft 365’s native tools. Centralized deletion of a compromised email from all affected mailboxes expedites the containment of a late-detected phishing campaign.
However, this capability carries implications that security leaders must define clearly. Granting a third-party tool the authority to delete messages from users’ inboxes necessitates governance of administrative rights, action traceability, and coordination with internal response procedures. Centralized remediation is a boost to efficiency, provided its scope of use is established prior to an incident, rather than during one.
The deployment of Protect via the Microsoft 365 API will be available to new clients starting in September 2026. This addition complements the existing MX redirection without replacing it, positioning the two modes as alternatives depending on organizational needs. For IT departments already engaged with Microsoft 365, the decision will hinge on the balance between the simplicity of native integration and the neutrality of an upstream filter, two distinct email security strategies that do not entirely overlap.



