MC711018: Microsoft Exchange Online: Support for inbound SMTP DANE with DNSSEC

Announcement IDMC711018Published Date01-29-2024
ServiceExchangeLast Updated07-17-2024
CategoryStay informedExpiration Date01-13-2025
Roadmap ID63213Action Required by Date
TagsAdmin impact, New feature, User impact


Summary
                Microsoft Exchange Online is updating to support inbound SMTP DANE with DNSSEC. Public Preview begins in July 2024, with General Availability rolling out from early September to late October 2024. This feature will be off by default and can be enabled using Exchange PowerShell, with a new experience for enabling without PowerShell coming by the end of 2024. There are specific supported and unsupported domain configurations to consider.


More Information

We are adding support for DNS-based Authentication of Named Entities (or DANE) for SMTP and Domain Name System Security Extensions (DNSSEC) for inbound mail to Exchange Online. DANE for SMTP is a security protocol that uses DNS to verify the authenticity of the certificates used for securing email communication with TLS and protecting against TLS downgrade attacks. DNSSEC is a set of extensions to DNS that provides cryptographic verification of DNS records, preventing DNS-spoofing and adversary-in-the-middle attacks to DNS.

When this will happen:

Public Preview: We will begin rolling out in July 2024.

General Availability: We begin rolling out early September 2024 (previously late August) and expect to complete by late October 2024 (previously late September).

How this will affect your organization:

Inbound SMTP DANE with DNSSEC will be off by default. If you do not want to enable the feature, you do not need to do anything.

What you need to do to prepare:

Review your domain configuration internally to ensure you won't be impacted by any of the limitations below.

  • Not supported: Fully delegated domain, onmicrosoft.com domains, and domains purchased from Microsoft known as viral or self-service sign-up domains
  • Supported with risk: 3rd-party gateways, connectors, and integration with hybrid mail flow (ex. if you are using a connector to smarthost to a domain that you want to enable with DNSSEC, you need to update the smarthost name for that connector ex. contoso-com.mail.protection.outlook.com to match the new MX record that will be provided during DNSSEC enablement or, preferably, to match the tenant's onmicrosoft.com domain ex. tenant-name.onmicrosoft.com before enabling the feature.)

Previous Post Next Post