Applies to: Exchange Online, Exchange Server 2016

This cmdlet is available in on-premises Exchange Server 2016 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.

Use the Search-MessageTrackingReport cmdlet to find the unique message tracking report based on the search criteria provided. You can then pass this message tracking report ID to the Get-MessageTrackingReport cmdlet to get full message tracking information. For more information, see Get-MessageTrackingReport. The message tracking report cmdlets are used by the delivery reports feature.

For information about the parameter sets in the Syntax section below, see Syntax.

Search-MessageTrackingReport -Identity <MailboxIdParameter> -Sender <SmtpAddress> [-BypassDelegateChecking <SwitchParameter>] [-DoNotResolve <SwitchParameter>] [-MessageEntryId <String>] [-MessageId <String>] [-ResultSize <Unlimited>] [-Subject <String>] [-TraceLevel <Low | Medium | High>] <COMMON PARAMETERS>
Search-MessageTrackingReport -Identity <MailboxIdParameter> [-BypassDelegateChecking <SwitchParameter>] [-DoNotResolve <SwitchParameter>] [-MessageEntryId <String>] [-MessageId <String>] [-Recipients <SmtpAddress[]>] [-ResultSize <Unlimited>] [-Subject <String>] [-TraceLevel <Low | Medium | High>] <COMMON PARAMETERS>
COMMON PARAMETERS: [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

This example searches the message tracking report for messages sent from one user to another. This example returns the message tracking report for a message that David Jones sent to Wendy Richardson.

Search-MessageTrackingReport -Identity "David Jones" -Recipients ""

This example searches the message tracking report for the following scenario: The user Cigdem Akin was expecting an email message from that never arrived. She contacted the Help desk, which needs to generate the message tracking report on behalf of Cigdem and doesn't need to see the display names.

This example returns the message tracking reports that the Help desk can analyze to resolve the issue.

Search-MessageTrackingReport -Identity "Cigdem Akin" -Sender "" -BypassDelegateChecking -DoNotResolve

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Message tracking" entry in the Mail flow permissions topic.


Parameter Required Type Description




The Identity parameter specifies the name of the mailbox for whom the message tracking report is being searched. The message tracking report only contains the tracking events related to the specified mailbox.

This parameter accepts the following values:

  • Alias

    Example: JPhillips

  • Canonical DN

    Example: Atlanta.Corp.Contoso.Com/Users/JPhillips

  • Display Name

    Example: Jeff Phillips

  • Distinguished Name (DN)

    Example: CN=JPhillips,CN=Users,DC=Atlanta,DC=Corp,DC=contoso,DC=com

  • Domain\Account

    Example: Atlanta\JPhillips

  • GUID

    Example: fb456636-fe7d-4d58-9d15-5af57d0354c2

  • Immutable ID


  • Legacy Exchange DN

    Example: /o=Contoso/ou=AdministrativeGroup/cn=Recipients/cn=JPhillips

  • SMTP Address


  • User Principal Name





The Sender parameter specifies the email address of the message sender.

By default, this command searches for messages sent by the user specified in the Identity parameter. If you want to search the message tracking report for a message sent to the user, you must specify the email address of the sender of that message using this parameter.




The BypassDelegateChecking switch allows Help desk staff and administrators to track messages for any user. End-users can only track messages that they send or receive. You don't have to specify a value with this switch.




The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.

  • Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.

  • Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.




This parameter is available only in on-premises Exchange 2016.

The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example,




The DoNotResolve switch prevents the resolution of email addresses to display names. This improves performance, but the end result may not be as easy to interpret because it's missing the display names. You don't have to specify a value with this switch.




This parameter is reserved for internal Microsoft use.




The MessageId parameter specifies the Internet message ID of the message for which you want to get the tracking report.




The Recipients parameter specifies the recipients for whom you want to get the tracking report.




The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.




The Subject parameter specifies text to be used to track messages that have the specified text in their subject lines.




This parameter is available only in on-premises Exchange 2016.

The TraceLevel parameter specifies whether additional trace details will be included in the output of the message tracking report. This parameter is intended to be used when troubleshooting message tracking issues.

The acceptable values for the TraceLevel parameter are:

  • Low   Minimal additional data is returned, including servers that were accessed, timing, message tracking search result counts, and any error information.

  • Medium   In addition to all the data returned for the Low setting, the actual message tracking search results are also returned.

  • High   Full diagnostic data is returned.




The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.