Forum Discussion
Exchange message trace by alias
- Jul 22, 2022
I was able to use the following in Powershell v7:
Install-Module -Name ExchangeOnlineManagement -RequiredVersion 2.0.5
Connect-ExchangeOnline
Get-MessageTrace -Sender mailto:email address removed for privacy reasons
Get-MessageTrace -Recipient mailto:email address removed for privacy reasons
This is confirmed to work with aliases
I have this same issue, and now that Classic message trace is pretty much gone in our tenants, this has become not only a practical issue, but a security issue.
I opened a ticket with Microsoft, and they are unable to resolve. The only option is a workaround to export all email within in the organization over a given time period, and look for aliases among all the other messages within the CSV. Besides being a huge pain to find emails to aliases, there is a security issue here in that it potentially exposes the admin to data irrelevant to the investigation at hand. If this is a HIPAA covered entity, for instance, and PII happens to be in the header/subject/etc in the CSV exported by message trace, this can lead to unauthorized PII exposure.
Classic message trace did not have this limitation.
- FarmhouseNetworkingJul 22, 2022Copper Contributor
I was able to use the following in Powershell v7:
Install-Module -Name ExchangeOnlineManagement -RequiredVersion 2.0.5
Connect-ExchangeOnline
Get-MessageTrace -Sender mailto:email address removed for privacy reasons
Get-MessageTrace -Recipient mailto:email address removed for privacy reasons
This is confirmed to work with aliases
- StevenAtRavnJul 25, 2022Copper ContributorOnce again, powershell proves its worth. Thanks!