Microsoft Defender for Office 365-Configure trusted ARC sealers email authentication for Microsoft 365 Custom domains

Authenticated Received Chain (ARC) is a mechanism used in email authentication protocols to address the issues of message forwarding and intermediary handling of emails. It is designed to improve the reliability and security of email authentication systems like SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail).

When an email is forwarded or relayed through multiple mail servers, the sender’s original authentication information may become unreliable or lost entirely. This can lead to problems such as SPF or DKIM signature verification failures, flagging legitimate emails as spam or phishing attempts.

ARC aims to solve these problems by creating a cryptographic chain of custody for an email message as it passes through intermediate mail servers. This chain allows each server in the delivery path to add its authentication information to the email header without breaking the original SPF or DKIM signatures.

Authenticated Received Chain (ARC) consists of three main components:

ARC-Seal: The ARC-Seal is a cryptographic signature added by each intermediate mail server in the email delivery chain. It includes information about the actions taken by the server, such as forwarding or relaying the message, as well as the results of any authentication checks performed by the server. The ARC-Seal helps establish the authenticity and integrity of the email delivery chain.

ARC-Message-Signature (AMS): The ARC-Message-Signature is added by the originating email server and covers the entire message, including the email headers and body. It serves as the initial cryptographic signature for the email and is used to verify the integrity of the message content. The AMS signature is carried through the entire delivery chain and is augmented by ARC-Seals added by intermediate servers.

ARC-Authentication-Results (AAR): The ARC-Authentication-Results header aggregates the authentication results from all intermediate servers in the email delivery chain. It summarizes the authentication checks performed by each server, including SPF, DKIM, and DMARC (Domain-based Message Authentication, Reporting, and Conformance) results. The AAR header helps the final destination server assess the trustworthiness of the email based on the collective authentication status of all servers involved in the delivery process.

Trusted ARC sealers are email services that provide valid and trustworthy Authenticated Received Chain (ARC) signatures to preserve the original email authentication information. You might need to use trusted ARC sealers when you have legitimate intermediate services that modify the messages before they are delivered to your Microsoft 365 organization, which can cause email authentication failures such as SPF, DKIM, or DMARC.

Before adding Trusted ARC sealers in the Microsoft Defender for Office 365, you must be assigned permissions as one of the below.

-Microsoft Defender XDR Unified role-based access control (RBAC) (Affects the Defender portal only, not PowerShell): Authorization and settings/Security settings/Core Security settings (manage) or Authorization and settings/Security settings/Core Security settings (read)

-Exchange Online permissions: Membership in the Organization Management or Security Administrator role groups.

-Microsoft Entra permissions: Membership in the Global Administrator or Security Administrator roles gives users the required permissions and permissions for other features in Microsoft 365.

Configure trusted ARC sealers

1.Login to the Microsoft Defender portal, expand Email & collaboration and select Policies & rules.

https://security.microsoft.com/