Prioritize comprehensive security and compliance measures before integrating AI into your IT ecosystem. This video showcases what the Microsoft AI Hub (preview) brings to the table in this context.
Regards
Sathish Veerapandian
Diversified Cloud Spot
Prioritize comprehensive security and compliance measures before integrating AI into your IT ecosystem. This video showcases what the Microsoft AI Hub (preview) brings to the table in this context.
Regards
Sathish Veerapandian
Till Exchange 2013 we were using the Search-Mailbox to delete any suspicious spam emails circulated in the organization.
From Exchange 2016 there is a new component New-ComplianceSearch introducted for performing this action.
In exchange 2016, New-ComplianceSearch cmdlet was introduced to search and delete messages. There are no limits for the number of mailboxes in a single search when using New-ComplianceSearch. If you use Search-Mailbox, you can only search a maximum of 10,000 mailboxes in a single search.
Still the Search-Mailbox is applicable and working for Exchange 2016 servers as well.
Example to create compliance search:
New-ComplianceSearch -Name “New Phishing Message” -ExchangeLocation “All”

Allowed parameters are few of them but we require these two at-least for better search:
ContentMatchQuery – The ContentMatchQuery parameter specifies a content search filter and uses the KQL – keyword query language syntax
Example :
New-ComplianceSearch -Name “Remove Phishing Message” -ExchangeLocation “All” -ContentMatchQuery “‘virus’ AND ‘your account closure'”
ExchangeLocation – This parameter specifies the location to look for the search
Accepted values are:
Specific Mailbox can be mentioned.
A distribution group can be mentioned.
All – When we specify all it looks for All mailboxes.
Force – After specifying this parameter only the command executed . Not sure why this was the case.
Also there is an option to modify the created one by using Set-ComplianceSearch cmdlet
IMPNote:
When a new compliance search is created a shadow in-place ediscovery search will be created in In-Place eDiscovery & Hold page in the EAC like below.

But the status will not be started and we can see this by running Get-MailboxSearch as well.
Microsoft recommends to delete this autocreated shadow In-Place eDiscovery search.
Instead run the Microsoft provided script in New-ComplianceSearch page that will convert an existing compliance search to an In-Place eDiscovery search
So when we run Get-ComplianceSearch we need to see the Compliances that we created
But When we run Get-MailboxSearch We should not see any shadow in-placediscovery which was created f0r them.
In short below will be the procedure:
Tips:
When we run the compliance search ps1 script provided by microsoft we should enter the value of the new compliance we created as below

While creating the inplace hold better to enter the values of all the available fields

Once the search completed there is an option to preview the search results through delegated admin account.
After that the data can be exported as PST.

Post that the New-ComplianceSearchAction command should be used to remove the emails.
Note:
Thanks & Regards
Sathish Veerapandian
MVP -Office Servers & Services