Skip to content

Remove MalwareName parameter from Get-MailDetailATPReport#13504

Open
EHLOBen wants to merge 2 commits intoMicrosoftDocs:mainfrom
EHLOBen:patch-1
Open

Remove MalwareName parameter from Get-MailDetailATPReport#13504
EHLOBen wants to merge 2 commits intoMicrosoftDocs:mainfrom
EHLOBen:patch-1

Conversation

@EHLOBen
Copy link
Copy Markdown

@EHLOBen EHLOBen commented Apr 9, 2026

Removed the MalwareName parameter and its details from the documentation, as this has been deprecated

Removed the MalwareName parameter and its details from the documentation, as this has been deprecated
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 9b95670:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

@chrisda
Copy link
Copy Markdown
Contributor

chrisda commented Apr 9, 2026

@EHLOBen, has the parameter been removed from visibility in code, or is it just no longer supported? I still see it in my plain M365 E5 tenant, but I realize changes take a while to propagate through the datacenters.

PS C:\Users> (Get-Command Get-MailDetailATPReport).Parameters.Keys | Where-Object {$_ -notin @('AsJob','Debug','ErrorAction','ErrorVariable','InformationAction','InformationVariable','OutBuffer','OutVariable','PipelineVariable','Verbose','WarningAction','WarningVariable')} | Sort-Object
DataSource
Direction
Domain
EndDate
EventType
MalwareName
MessageId
MessageTraceId
Page
PageSize
ProbeTag
RecipientAddress
SenderAddress
StartDate

@EHLOBen
Copy link
Copy Markdown
Author

EHLOBen commented Apr 9, 2026

It is removed from visibility, but still rolling out (rollout has started)

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 1b0b5ba:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

@github-actions
Copy link
Copy Markdown

@lusassl-msft
You've been added as a reviewer to this pull request because you're listed as a Content Lead for the product area or feature covered by one or more articles in this PR.

Before this PR can be merged, a Content Lead needs to add the Sign off label to it. Only one of the listed reviewers needs to add the Sign off label. Before you sign off a PR, confirm the following:

  • Article content has been checked for technical accuracy.
  • There are no errors or warnings in build validation.
  • There are no severity 1 or 2 PoliCheck issues.
  • All articles have a minimum Acrolinx score of 80.
  • All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

  1. Select the gear next to Labels.
  2. Select Sign off from the label list.
  3. Click away from the label list.

image

After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return
the PR to the submitter with required changes. After they've completed those changes, you need to sign off again.

When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours.

If you think you were incorrectly added as a reviewer, have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp.

@github-actions github-actions bot requested a review from lusassl-msft April 13, 2026 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants