Feedback by UserVoice

How can we improve compliance or protect your users better in Office 365?

Add multiple wildcard options to message trace capabilities

Please allow for the ability to use get-messagetrace in combination with multiple wildcard scenarios. For instance, if I want to see *@*.co.uk via a PowerShell query.

Example script
$mystart = (Get-Date).addhours(-72)
$myend = Get-Date
Get-MessageTrace -StartDate $mystart -EndDate $myend | where {$_.senderaddress -like "*@*.co.uk"}

This information use to be available with the ForeFront for Exchange on-prem solution and is still available with the Exchange on-prem Get-MessageTrackingLog function currently.

92 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Patrick shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Syed Saleemula commented  ·   ·  Flag as inappropriate

    Yes, please allow for the ability to use multiple wildcard scenarios..one more like .. Allow to track all emails which are older than 10 days ( all inbound and outbound emails from any tenant which includes user mails,Relay emails (sent using anonymous Domains)

  • Katherine Bargas commented  ·   ·  Flag as inappropriate

    Yes please we are in a situation right now where we could use a wild card on sender. For example where {$_.senderaddress -like "testsubject*@*.co.uk"} this would be very very helpful.

Feedback and Knowledge Base