Microsoft Makes Exchange Online Direct Send Protection Generally Available

Microsoft has made Reject Direct Send generally available in Exchange Online, helping organizations block unauthenticated messages that spoof their own domains. This change could reduce phishing risks, but administrators may need to review and update existing mail flows before enabling the protection.

Cloud Computing

Key Takeaways:

  • Microsoft has made Reject Direct Send generally available for Exchange Online tenants.
  • The feature blocks unauthenticated messages that attempt to use an organization’s accepted domains as sender addresses.
  • Organizations should review Direct Send dependencies and configure trusted connectors before enabling the protection.

Organizations often allow devices, applications, and third-party services to send email directly to Exchange Online using their own domain through a feature called Direct Send. The problem is that Direct Send doesn’t require authentication, so attackers can abuse it to send messages that appear to originate from the organization’s domain.

This creates an unnecessary opportunity for domain spoofing and phishing attacks for many tenants that no longer rely on Direct Send. More than 70,000 organizations have already enabled Microsoft’s protection during preview, which highlights the scale of the risk.

Exchange Online gets Reject Direct Send

To address this issue, Microsoft introduced Reject Direct Send, which is now generally available for Exchange Online tenants worldwide. When enabled, Exchange Online blocks anonymous messages that use one of the organization’s accepted domains as the envelope sender address unless the message can be attributed to a trusted mail flow connector.

To help administrators identify legitimate senders, Microsoft has also made the Change Optics Report generally available in the Exchange admin center. Organizations can review existing Direct Send traffic, create partner connectors for approved senders, and then enable the protection using PowerShell. Microsoft is also rolling out this protection by default for new Exchange Online tenants as part of its secure-by-default strategy.

Organizations may need to update existing mail flows

However, keep in mind that some legitimate email flows may stop working if they rely on unauthenticated Direct Send. Organizations must first inventory devices, applications, and third-party services that send mail using their domain and configure connectors based on TLS certificates or sending IP addresses.

Microsoft also notes that certain third-party forwarding scenarios that do not support Sender Rewriting Scheme (SRS) may experience message rejections after the setting is enabled. This adds administrative work and may require changes to older mail workflows, but it significantly reduces the risk of attackers spoofing the organization’s own domain.