MC1323250 High Major change
[Action Required] Update scripts using Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport
Summary AI-generated
Starting July 30, 2026, Exchange Online will require an explicit EventType parameter in two reporting cmdlets to return transport rule data, affecting scripts and reporting automation.
Suggested actions AI-generated
- Review and update scripts using affected Exchange cmdlets
- Explicitly include EventType parameter for transport rule data
- Validate updated scripts in a test environment
- Update documentation and notify relevant teams
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1213770 (Updated) Microsoft Purview | Data lifecycle Management cmdlet connectivity change
- MC1272554 Top domain mail flow report in Exchange Online is retiring
- MC1108848 (Updated) Changing output format for some database properties in Exchange Online cmdlets
- MC1485116 Microsoft Exchange Online: Exchange Web Services (EWS) enforcement update for EWSAllowedAppIDs
- MC1483974 Action Required: Upgrade ExchangeOnlineManagement PowerShell Module to Version 3.10.1 or Later
- MC1469960 (Updated) Microsoft Exchange Online: Review and configure EWSAllowedAppIDs before Exchange Web Services access changes
Original post from Microsoft
[What and Why:]
To improve clarity, precision, and performance of transport rule reporting, Microsoft is updating the behavior of two Exchange Online reporting cmdlets. Starting July 30, 2026, Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport will return transport rule data only when the request explicitly specifies the relevant EventType. This change helps ensure that reporting queries are intentional, predictable, and aligned with how transport rule events are generated and logged.
This update supports enterprise‑ready manageability by reducing ambiguous results and helping administrators build more reliable automation and compliance reporting.
[Rollout Schedule:]
General Availability (Worldwide): We will begin rolling out in late July 2026 and expect to complete by late July 2026.
[Impact on Your Organization:]
Who is affected:
- Exchange Online administrators
- Security, compliance, or messaging teams
- Any organization using PowerShell scripts, automation, or reporting that relies on transport rule data from these cmdlets
Platforms/Services:
- Exchange Online
- Exchange Online PowerShell
What will happen:
- Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport will no longer return transport rule results by default.
- Transport rule data will be returned only when one of the following parameters is explicitly included:
-EventType TransportRuleHits-EventType TransportRuleActionHits
- Scripts or reports that do not include one of these parameters may return empty or incomplete results.
- This change applies only to these two cmdlets. No other Exchange Online cmdlets are affected.
[Action Required / Recommendations:]
If your organization uses these cmdlets for transport rule reporting, action is required before July 30, 2026.
Recommended actions:
- Review all scripts, scheduled jobs, and automation that use:
Get-MailDetailTransportRuleReportGet-MailTrafficPolicyReport
- Update queries that require transport rule results to explicitly include:
-EventType TransportRuleHitsor-EventType TransportRuleActionHits
- Validate updated scripts in a non‑production or test context.
- Update internal documentation and operational runbooks.
- Notify messaging and security operations teams of this change.
[Compliance considerations:]
This change alters how admins retrieve and report on transport rule data for compliance and auditing purposes.
Additional details from Microsoft
- Summary
- Starting July 30, 2026, Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport will return transport rule data only when the -EventType parameter (TransportRuleHits or TransportRuleActionHits) is explicitly specified. Administrators must update related scripts and automation before this date to avoid incomplete results.