Extending Message Trace to 90 days in Exchange Online

[The_Exchange_Team]

Message trace enables administrators to trace email messages as they pass through Exchange Online or Exchange Online Protection (EOP) service. It helps you determine whether a message was received, rejected, deferred, or delivered by the service.

You’ve told us that you need to be able to trace messages older than the current period of one week. We’re excited to announce that we’re increasing the look back period for message trace in Exchange Online to 90 days!

The existing functionality of looking up messages for the last week will persist and those results will be viewable immediately. When you search for messages older than a week, the request will be submitted as an extended message trace request. After the request has been processed, the trace results will be delivered to you in a CSV file by email. An example of an extended message trace request is shown below.

We’re already rolling out this feature. Look for more details later this month.

This feature applies to Exchange Online and Exchange Online Protection services. On-premises customers have the capability to manage and search message tracking logs in Exchange Server.

Want to know more about this topic? Join the Exchange engineering team and MVPs at MEC 2014 for a chance to get your questions answered. Register today at IAMMEC.com.

Vandana Kumbla
Senior Program Manager

[#2]

@abcd12356 1) The recipient_status column provides the status of the delivery of the message to the recipient. If the message was sent to multiple recipients, it will show all the recipients and the corresponding status against each, in the format: ##.

For example, ##Receive, Send means that the message was received by the service and sent to the intended destination. ##Receive, Fail means that the message was received by the service but failed to be delivered to the intended destination. ##Receive, Deliver

means that the message was received by the service and delivered to the recipient’s mailbox. 2) With regard to input criteria, you can provide the date and time range in which to search for message events. We do not offer search by message subject (is this

what you meant by title?) at this point.

[#3]

Extending Message Trace to 90 days in Exchange Online
thank you

[#4]

@John B: As mentioned in the post, on-premises customers can manage and search their own message tracking logs on their Exchange Server(s). By default, message tracking logs are retained for 30 days in Exchange 2013 and can be configured using

Set-TransportService cmdlet. See

Message Tracking and

Configure Message Tracking for details.

[#5]

The inability to search by subject or content is a huge limitation for us. Any plans to implement this sorely lacking functionality?

[#6]

Will this functionality be in SP1 for on prem?

[#7]

@John B - What trace functionality are you looking for w/ on-prem? You can currently use OWA/ECP and/or powershell to search your tracking logs for on-prem. Once it leaves your org, the above is handy if you're already a EPO customer, but otherwise I don't

see how this would benefit on-prem?

[#8]

Online users get the cool GUI interface while onprem users get the crummy powershell interface. Figures. Well, at least the option is there, but wow, the Exchange team onprem sucks.

[#9]

Right that is my point. Message Trace is not available on prem. No issue running from powershell.

[#10]

Finally, thank you!

[#11]

Well at least, we are getting info in this Article "On-premises customers have the capability to manage and search message tracking logs in Exchange Server." Usually, NO info for Exchange On-Premises customers!!!

[#12]

Exchange On-Premises customers can use ECP or Powershell and it works well.

[#13]

@John B "Right that is my point. Message Trace is not available on prem. No issue running from powershell." http://technet.microsoft.com/en-us/library/bb124926(v=exchg.141).aspx What is missing?

[#14]

I guess Microsoft will NEVER get it :) Enterprises do NOT want to move to the Public Cloud / Office 365, because Public Cloud is infested with Security Issues.

[#15]

Just have to say that interface looks like crap in the picture above. Blinding white and grey with huge amount sod wasted space and zero help buttons. Can't tell if I can click on any of the words. It's an unmitigated disaster of an interface you've created.

[#16]

In the CSV there are only these columns "origin_timestamp sender_address recipient_status message_subject total_bytes message_id network_message_id original_client_ip directionality connector_id delivery_priority". We are not sure if it's delivered from

the information.

[#17]

Also we often use "title" or "time/time zone" to find results, we hope they are possible to use before click "search".

[#18]

Can we please have the old Exchange Management Console back? It was 1000 times better than this web interface nonsense. It was also better for a lot of tasks over having to use PowerShell. Why is the Exchange team continually degrading the product functionality?

[#19]

What are the required Management Role Entries to download/view CSV files on the portal? With a helpdesk account (with minimal rights) I'm able to create reports but I can't view them, I'm redirect to a page with Runtime Error.