none
Office 365 Reporting Web Service Message Trace - It says it can get the past 30 days but i can only get the past 7 days RRS feed

  • Question

  • It says Message Trace data is stored for 90 days here: http://technet.microsoft.com/library/jj723162(v=exchg.150).aspx

    When running the MessageTrace report using the Office 365 Reporting Web Service it only returns the past 7 days, even though it says up to 30 days here: http://msdn.microsoft.com/en-us/library/office/jj984335(v=office.15).aspx.

    PowerShell’s "Get-MessageTrace" cmdlet only returns the past 7 days as well. PowerShell also has an alternative cmdlet called "Start-HistoricalSearch" which returns the MessageTrace results between 7 and 90 days old.

    Is it supposed to return 30 days, or is the documentation wrong, or is their an alternative report (like PowerShell) to get MessageTrace results for over 7 days using the Office 365 Reporting Web Service?

    Note: I'm aware that the results are returned in batches of 2000 MessageTrace results.


    • Edited by Megga.Richard Wednesday, November 19, 2014 9:09 AM Corrected title
    Thursday, November 13, 2014 3:50 PM

Answers

  • That document is pretty old last modified March 2013 so I would say it's out of date. The reporting services are still pretty new in the current release I believe 7 days is limit for the Rest Endpoint and the Get-MessageTrace cmdlet (which is what the more recent documentation around message tracking say) there is no REST endpoint for Start-HistoricalSearch you can see all the current endpoints by looking at the Metadata via

    https://reports.office365.com/ecp/reportingwebservice/reporting.svc/$metadata

    These services are evolving so new features and reports are added which is explained in http://msdn.microsoft.com/EN-US/library/office/jj984346(v=office.15).aspx . But there is no public information on Timeframes and what reports and features are going to be added in future updates (that I know of). If you need data older then 7 days then Automating the HistoricalSearch cmdlets would be the way to do it for now.

    Cheers
    Glen

     
    • Marked as answer by Megga.Richard Tuesday, December 9, 2014 10:01 AM
    Wednesday, November 19, 2014 5:15 AM

All replies

  • Our Office 365 Support representative continues to tell us that this is the best (possibly only) method to get support for the Office 365 Reporting Web Service.

    Can anyone help?

    Tuesday, November 18, 2014 12:10 PM
  • Please try this powershell command:

    Get-MessageTrace -start “11/3/2014 14:00:00” -end “11/4/2014 12:00:00” -Recipients user@domain.com | export-csv c:\temp\track.csv

    Please change date and time according to your requirements.


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work


    • Edited by Off2work Tuesday, November 18, 2014 8:27 PM edit
    Tuesday, November 18, 2014 8:27 PM
  • That document is pretty old last modified March 2013 so I would say it's out of date. The reporting services are still pretty new in the current release I believe 7 days is limit for the Rest Endpoint and the Get-MessageTrace cmdlet (which is what the more recent documentation around message tracking say) there is no REST endpoint for Start-HistoricalSearch you can see all the current endpoints by looking at the Metadata via

    https://reports.office365.com/ecp/reportingwebservice/reporting.svc/$metadata

    These services are evolving so new features and reports are added which is explained in http://msdn.microsoft.com/EN-US/library/office/jj984346(v=office.15).aspx . But there is no public information on Timeframes and what reports and features are going to be added in future updates (that I know of). If you need data older then 7 days then Automating the HistoricalSearch cmdlets would be the way to do it for now.

    Cheers
    Glen

     
    • Marked as answer by Megga.Richard Tuesday, December 9, 2014 10:01 AM
    Wednesday, November 19, 2014 5:15 AM
  • Good spot, Microsoft's technical support have agreed there's a documentation bug.

    Microsoft's technical support representative is currently looking into the possibility of an enhancement to PowerShell's "Get-MessageTrace" cmdlet to return more than 7 days. Note: behind the scenes the REST endpoint uses the "Get-MessageTrace" cmdlet.

    Tuesday, December 9, 2014 10:06 AM