|
| 1 | +--- |
| 2 | +external help file: Microsoft.Exchange.TransportMailflow-Help.xml |
| 3 | +online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetracedetailv2 |
| 4 | +applicable: Exchange Online, Exchange Online Protection |
| 5 | +title: Get-MessageTraceDetailV2 |
| 6 | +schema: 2.0.0 |
| 7 | +author: chrisda |
| 8 | +ms.author: chrisda |
| 9 | +ms.reviewer: |
| 10 | +--- |
| 11 | + |
| 12 | +# Get-MessageTraceDetailV2 |
| 13 | + |
| 14 | +## SYNOPSIS |
| 15 | + |
| 16 | +## SYNTAX |
| 17 | + |
| 18 | +``` |
| 19 | +Get-MessageTraceDetailV2 [-MessageTraceId] <Guid> [-RecipientAddress] <String> |
| 20 | + [[-Action] <MultiValuedProperty>] |
| 21 | + [[-EndDate] <System.DateTime>] |
| 22 | + [[-Event] <MultiValuedProperty>] |
| 23 | + [[-MessageId] <String>] |
| 24 | + [[-SenderAddress] <String>] |
| 25 | + [[-StartDate] <System.DateTime>] |
| 26 | + [<CommonParameters>] |
| 27 | +``` |
| 28 | + |
| 29 | +## DESCRIPTION |
| 30 | +{{ Fill in the Description }} |
| 31 | + |
| 32 | +## EXAMPLES |
| 33 | + |
| 34 | +### Example 1 |
| 35 | +```powershell |
| 36 | +Get-MessageTraceDetail -MessageTraceId ae5c1219-4c90-41bf-fef5-08d837917e7c -RecipientAddress [email protected] |
| 37 | +``` |
| 38 | + |
| 39 | +This example retrieves detailed message trace information for messages with the message trace ID value ae5c1219-4c90-41bf-fef5-08d837917e7c that were received by `[email protected]`. |
| 40 | + |
| 41 | +### Example 2 |
| 42 | +```powershell |
| 43 | +Get-MessageTrace -MessageTraceId 2bbad36aa4674c7ba82f4b307fff549f -SenderAddress [email protected] -StartDate 05/13/2025 -EndDate 05/15/2025 | Get-MessageTraceDetail |
| 44 | +``` |
| 45 | + |
| 46 | +This example uses the Get-MessageTrace cmdlet to retrieve message trace information for messages with the Exchange Network Message ID value 2bbad36aa4674c7ba82f4b307fff549f sent by `[email protected]` between May 13, 2025 and May 15, 2025, and pipelines the results to the Get-MessageTraceDetail cmdlet. |
| 47 | + |
| 48 | +## PARAMETERS |
| 49 | + |
| 50 | +### -MessageTraceId |
| 51 | +The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1). |
| 52 | + |
| 53 | +The MessageTraceId value is also available in the output of the following cmdlets: |
| 54 | + |
| 55 | +- Get-MailDetailATPReport |
| 56 | +- Get-MailDetailDlpPolicyReport |
| 57 | +- Get-MailDetailEncryptionReport |
| 58 | +- Get-MailDetailTransportRuleReport |
| 59 | +- Get-MessageTraceV2 |
| 60 | + |
| 61 | +```yaml |
| 62 | +Type: Guid |
| 63 | +Parameter Sets: (All) |
| 64 | +Aliases: |
| 65 | +Applicable: Exchange Online, Exchange Online Protection |
| 66 | + |
| 67 | +Required: True |
| 68 | +Position: 5 |
| 69 | +Default value: None |
| 70 | +Accept pipeline input: True (ByPropertyName) |
| 71 | +Accept wildcard characters: False |
| 72 | +``` |
| 73 | +
|
| 74 | +### -RecipientAddress |
| 75 | +The RecipientAddress parameter filters the results by the recipient's email address. |
| 76 | +
|
| 77 | +```yaml |
| 78 | +Type: String |
| 79 | +Parameter Sets: (All) |
| 80 | +Aliases: |
| 81 | +Applicable: Exchange Online, Exchange Online Protection |
| 82 | + |
| 83 | +Required: True |
| 84 | +Position: 6 |
| 85 | +Default value: None |
| 86 | +Accept pipeline input: True (ByPropertyName) |
| 87 | +Accept wildcard characters: False |
| 88 | +``` |
| 89 | +
|
| 90 | +### -Action |
| 91 | +The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports. |
| 92 | + |
| 93 | +You can specify multiple values separated by commas. |
| 94 | + |
| 95 | +```yaml |
| 96 | +Type: MultiValuedProperty |
| 97 | +Parameter Sets: (All) |
| 98 | +Aliases: |
| 99 | +Applicable: Exchange Online, Exchange Online Protection |
| 100 | +
|
| 101 | +Required: False |
| 102 | +Position: 1 |
| 103 | +Default value: None |
| 104 | +Accept pipeline input: False |
| 105 | +Accept wildcard characters: False |
| 106 | +``` |
| 107 | + |
| 108 | +### -EndDate |
| 109 | +The EndDate parameter specifies the end date of the date range. |
| 110 | + |
| 111 | +Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2025 to specify September 1, 2025. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2025 5:00 PM". |
| 112 | + |
| 113 | +If don't use the StartDate and EndDate parameters, only data from the last 48 hours is returned. |
| 114 | + |
| 115 | +```yaml |
| 116 | +Type: System.DateTime |
| 117 | +Parameter Sets: (All) |
| 118 | +Aliases: |
| 119 | +Applicable: Exchange Online, Exchange Online Protection |
| 120 | +
|
| 121 | +Required: False |
| 122 | +Position: 2 |
| 123 | +Default value: None |
| 124 | +Accept pipeline input: True (ByPropertyName) |
| 125 | +Accept wildcard characters: False |
| 126 | +``` |
| 127 | + |
| 128 | +### -Event |
| 129 | +The Event parameter filters the report by the message event. The following are examples of common events: |
| 130 | + |
| 131 | +- RECEIVE: The message was received by the service. |
| 132 | +- SEND: The message was sent by the service. |
| 133 | +- FAIL: The message failed to be delivered. |
| 134 | +- DELIVER: The message was delivered to a mailbox. |
| 135 | +- EXPAND: The message was sent to a distribution group that was expanded. |
| 136 | +- TRANSFER: Recipients were moved to a bifurcated message because of content conversion, message recipient limits, or agents. |
| 137 | +- DEFER: The message delivery was postponed and may be re-attempted later. |
| 138 | + |
| 139 | +You can specify multiple values separated by commas. |
| 140 | + |
| 141 | +```yaml |
| 142 | +Type: MultiValuedProperty |
| 143 | +Parameter Sets: (All) |
| 144 | +Aliases: |
| 145 | +Applicable: Exchange Online, Exchange Online Protection |
| 146 | +
|
| 147 | +Required: False |
| 148 | +Position: 3 |
| 149 | +Default value: None |
| 150 | +Accept pipeline input: False |
| 151 | +Accept wildcard characters: False |
| 152 | +``` |
| 153 | + |
| 154 | +### -MessageId |
| 155 | +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"). |
| 156 | + |
| 157 | +```yaml |
| 158 | +Type: String |
| 159 | +Parameter Sets: (All) |
| 160 | +Aliases: |
| 161 | +Applicable: Exchange Online, Exchange Online Protection |
| 162 | +
|
| 163 | +Required: False |
| 164 | +Position: 4 |
| 165 | +Default value: None |
| 166 | +Accept pipeline input: True (ByPropertyName) |
| 167 | +Accept wildcard characters: False |
| 168 | +``` |
| 169 | + |
| 170 | +### -SenderAddress |
| 171 | +The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas. |
| 172 | + |
| 173 | +```yaml |
| 174 | +Type: String |
| 175 | +Parameter Sets: (All) |
| 176 | +Aliases: |
| 177 | +Applicable: Exchange Online, Exchange Online Protection |
| 178 | +
|
| 179 | +Required: False |
| 180 | +Position: 7 |
| 181 | +Default value: None |
| 182 | +Accept pipeline input: True (ByPropertyName) |
| 183 | +Accept wildcard characters: False |
| 184 | +``` |
| 185 | + |
| 186 | +### -StartDate |
| 187 | +The StartDate parameter specifies the start date of the date range. |
| 188 | + |
| 189 | +Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2025 to specify September 1, 2025. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2025 5:00 PM". |
| 190 | + |
| 191 | +If don't use the StartDate and EndDate parameters, only data from the last 48 hours is returned. |
| 192 | + |
| 193 | +```yaml |
| 194 | +Type: System.DateTime |
| 195 | +Parameter Sets: (All) |
| 196 | +Aliases: |
| 197 | +Applicable: Exchange Online, Exchange Online Protection |
| 198 | +
|
| 199 | +Required: False |
| 200 | +Position: 8 |
| 201 | +Default value: None |
| 202 | +Accept pipeline input: True (ByPropertyName) |
| 203 | +Accept wildcard characters: False |
| 204 | +``` |
| 205 | + |
| 206 | +### CommonParameters |
| 207 | +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216). |
| 208 | + |
| 209 | +## INPUTS |
| 210 | + |
| 211 | +## OUTPUTS |
| 212 | + |
| 213 | +## NOTES |
| 214 | + |
| 215 | +## RELATED LINKS |
0 commit comments