Docs Build status updates of commit 9970da4:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit 2c72ffd:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit 103e20e:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

All CLA requirements met.

Docs Build status updates of commit 35254bd:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

I made some edits:

• Unclear why AttachmentContainsWords was deleted from the syntax block, so I added it back. That parameter is definitely available in Exchange Online, and Exchange Server 2013-2019 in both New-TransportRule and Set-TransportRule.
• New-TransportRule and Set-TransportRule are basically identical, so anything you do in one needs to be done in the other.
• The description of a condition parameter is basically identical to the description of the corresponding exception parameter. So, whatever change you make to ExceptIfMessageTypeMatches, you also need to do to MessageTypeMatches.
• I noticed a strange problem for every parameter in the syntax block that contains []: there's a space between the parameter type and the [] that shouldn't be there (for example, <RecipientIdParameter[]> not <RecipientIdParameter []>). I'll fix that in a different pull request.