Add Get-AllMessageTraceResults script and documentation#2527
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a reusable PowerShell helper to fetch all Exchange Online message trace results by wrapping Get-MessageTraceV2 and automatically handling pagination, plus accompanying documentation.
Changes:
- Introduces
Get-AllMessageTraceResultswith automatic pagination and a timeout guard. - Adds docs describing parameters and usage examples.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| Transport/Get-AllMessageTraceResults.ps1 | New function wrapping Get-MessageTraceV2 and paging through all results. |
| docs/Transport/Get-AllMessageTraceResults.md | New documentation page for the script/function and its parameters. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
344fb99 to
7ff4275
Compare
dpaulson45
reviewed
Apr 3, 2026
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ected warnings - Use moreAvailable[-1] instead of joining all warnings - Add warning message when pagination fails with unexpected warning - Include last command in warning for debugging Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0e61149 to
fecae41
Compare
…voke-Command - Use StartingRecipientAddress and EndDate from last result for pagination - Remove warning message parsing and dynamic scriptblock execution - Move timeout check inside loop to only warn when data is actually truncated Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Replace 3>$null with 3>&1 stream redirection to capture warnings from Get-MessageTraceV2, then filter WarningRecord objects and surface them via Write-Verbose with page context - Update doc description to clarify this is an Exchange Online wrapper requiring an active EXO PowerShell session - Remove dot-sourcing from doc examples since the script is no longer a function Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Add the missing navigation entry for Get-AllMessageTraceResults under the Transport section so the doc page appears on the site. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
dpaulson45
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a standalone reusable function that wraps Get-MessageTraceV2 with automatic pagination support. This makes it easy to retrieve all matching message trace results from Exchange Online without manually
handling the pagination logic.
Changes
Details