Exchange Online Mail Flow Rules to stop supporting DLP-related rules, conditions, and actions

The_Exchange_Team Thanks for the head’s up. We manage many tenants and always monitor the Message Center. Any plans to push out Message Center messages to those tenants actively using these ETR rules or do we need to check each tenant config if it’s used?

Jonas Back I was hoping we could, but sorry we won't be able to provide targeted MC posts to tenants using rules with these conditions. 

Shawn Christian actually the wizard only migrates DLP policies and associated mail flow rules so mail flow rules without policies that use these DLP-related conditions and action don't qualify for migration with the wizard. You can export your rules using PowerShell and filter/search for the above conditions/action. Apologies for the misleading statement in the blog post, we'll correct it shortly. 

lukesrees Depends on your rule - if the rule uses any of the mentioned predicates above then that rule won't work come mid-November (early to mid-next week). If you're using something else for your profanity list like a simple expression check using the condition "SubjectOrBodyContainsWords" (aka "The subject or body includes any of these words" in the EAC UI) then it won't be affected. That said, you might consider just moving it to DLP along with your outbound DLP rule. Purview DLP supports both outbound and inbound mail flows (e.g. use Content is received from. . .People outside my organization). 

AHA!

Thanks, I had recently upgraded to PS7 and was missing the exchange online management module.

Thanks for your help, and have a wonderful Thanksgiving.

So I have 8 ETRs that say "Support for DLP-related mail flow rules will stop in mid-November. See https://aka.ms/NoDLPinETRs."  But I when click Migrate Polices in Exchange Online nothing shows up to migrate.

How will this affect inbound rules that use SIT? Assume we have a SIT for profanities, we block outbound using DLP and use the same SIT to block inbound using an ETR...

Thanks

My current ETR's relating to credit Card blocking have been locked. How can I display the contents of those rules to allow me to recreate exclusions and other details in Purview. I have tried Get-TransportRule and it does not seem to be working. There is no banner for rule migration in Purview, so I am assuming my rules cannot be migrated?

Thanks

Bobby_ono While the Edit option is disabled for rules that include DLP-related conditions and actions, you can still click on the rule in the EAC to expose the rule's fly-out panel summary where you can still see the rule's description including its predicates and actions. The rule migration banner in Purview will only show up for ETRs that have linked DLP-policies in them. For rules that have DLP-related conditions/action those can't be migrated with the DLP migration wizard and won't trigger the banner in Purview. Using PowerShell try these cmdlets:

1. Check if you have ETRs linked to DLP policies via Exchange Online PowerShell:

Get-TransportRule | where { $_.DlpPolicyId -ne [Guid]::Empty }

2. Check if you have any other ETRs that include DLP-related conditions or actions:

Get-TransportRule | where { $_.SenderNotificationType -ne $null -or $_.MessageContainsDataClassifications -ne $null -or $_.ExceptIfMessageContainsDataClassifications -ne $null -or $_.HasSenderOverride -eq $true -or $_.ExceptIfHasSenderOverride -eq $true }

Itried those both, am getting a cmd error

PS C:\Windows\System32> Get-TransportRule | where { $_.SenderNotificationType -ne $null -or $_.MessageContainsDataClassifications -ne $null -or $_.ExceptIfMessageContainsDataClassifications -ne $null -or $_.HasSenderOverride -eq $true -or $_.ExceptIfHasSenderOverride -eq $true }

Get-TransportRule: The term 'Get-TransportRule' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

And 

PS C:\Windows\System32> Get-TransportRule | where { $_.DlpPolicyId -ne [Guid]::Empty }
Get-TransportRule: The term 'Get-TransportRule' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Bobby_ono If the Get-TransportRule cmdlet isn't recognized it's likely one of two things:

1. You haven't connected to Exchange Online PowerShell Connect to Exchange Online PowerShell | Microsoft Learn
   (be sure to import the ExchangeOnlineManagement module as stated in the doc)
2. You don't have email or global admin permissions for your tenant.

If after following the instructions in the above doc and ensuring you have email admin or global admin perms in the tenant you're still getting the error then please open a support ticket for further assistance.