MC393818 – Add DKIM Domain in Sending Infrastructure for Tenant Allow Block Lists-Spoofing (archived)

Microsoft Exchange Logo

check before: 2022-07-02

Product:

Defender, Defender for Office 365, Exchange, Microsoft 365 Defender

Platform:

Online, US Instances, Web, World tenant

Status:

Launched

Change type:

New feature, User impact, Admin impact

Links:

93359

Details:

For Microsoft Defender for Office 365 and Exchange Online Protection, we are adding support for providing "DKIM verified domain" as the "Sending Infrastructure" within Tenant allow-block lists-Spoofing, so that Security Administrators can better manage Anti-Spoofing activity and override it based on Spoof Intelligence. Currently, what is supported in this field is either the domain from DNS PTR record or /24 IP Subnet. Additionally, being able to specify a 'DKIM verified domain' will help serve scenarios where shared infrastructure provider services are used for sending emails. Since the DKIM domain is unique to each tenant and if it passes verification even when other authentication signals fail, if desired for legitimate business reasons, a spoofed message can still be allowed instead of being blocked.
This message is associated with Microsoft 365 Roadmap ID 93359
[When this will happen:]
Standard: Rollout will begin in early July and is expected to be completed by late August.
Gov Cloud: Rollout will begin in early September and is expected to be completed by late September.

Change Category:
XXXXXXX ...

Scope:
XXXXXXX ...

Release Phase:
General Availability

Created:
2022-06-19

updated:
2022-08-27

the free basic plan is required to see all details. Sign up here


A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.


changes*

DatePropertyoldnew
2022-09-15MC prepareThere is nothing you need to do to prepare for this change. You may want to notify your users about this change and update your training and documentation as appropriate.
ps://docs.microsoft.com/microsoft-365/security/office-365-security/tenant-allow-block-list?view=o365-worldwide#domain-pair-syntax-for-spoofed-sender-entries-in-the-tenant-allowblock-li
ps://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=93359
There is nothing you need to do to prepare for this change. You may want to notify your users about this change and update your training and documentation as appropriate.
https://docs.microsoft.com/microsoft-365/security/office-365-security/tenant-allow-block-list?view=o365-worldwide#domain-pair-syntax-for-spoofed-sender-entries-in-the-tenant-allowblock-list
https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=93359
2022-08-27MC prepareThere is nothing you need to do to prepare for this change. You may want to notify your users about this change and update your training and documentation as appropriate.
https://docs.microsoft.com/microsoft-365/security/office-365-security/tenant-allow-block-list?view=o365-worldwide#domain-pair-syntax-for-spoofed-sender-entries-in-the-tenant-allowblock-list
https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=93359
There is nothing you need to do to prepare for this change. You may want to notify your users about this change and update your training and documentation as appropriate.
ps://docs.microsoft.com/microsoft-365/security/office-365-security/tenant-allow-block-list?view=o365-worldwide#domain-pair-syntax-for-spoofed-sender-entries-in-the-tenant-allowblock-li
ps://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=93359

*starting April 2022

Last updated 1 month ago

Login to your account

Welcome Back, We Missed You!