Docs Build status updates of commit fd7754c:

✅ 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 856499c:

✅ 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 15c45a1:

✅ 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

@dariomws, see my comments in the related Issue (I don't believe Set-ExternalInOutlook and MailTipsExternalRecipientsTipsEnabled on Set-OrganizationConfig have anything to do with each other).

The removal of [-ExternalInOutlook] from the syntax block is fine.

Two additional things to remember:

• Availability of a cmdlet/parameter is different from functionality. The applicable/Applicable metadata values on cmdlets/parameters need to accurately reflect if the cmdlet/parameter is AVAILABLE in a particular environment. We can use additional text (the parameter description, the SYSOPSIS section, and/or the DESCRIPTION section) to explain that the cmdlet/parameter doesn't work in a specific environment. In other words: if a cmdlet/parameter is AVAILABLE, don't remove it (including its applicable/Applicable value).
• Always use full docs.microsoft.com topic URLs in cmdlet reference topics. Relative topic links will work fine on the web, but they won't populate correctly when the topics are converted from markdown to MAML XML for code check-in and use at the command line.

Thank you @chrisda. It was my mistake, I didn't see that one parameter is for inbound and the other one for outbound.

• Availability of a cmdlet/parameter is different from functionality. The applicable/Applicable metadata values on cmdlets/parameters need to accurately reflect if the cmdlet/parameter is AVAILABLE in a particular environment. We can use additional text (the parameter description, the SYSOPSIS section, and/or the DESCRIPTION section) to explain that the cmdlet/parameter doesn't work in a specific environment. In other words: if a cmdlet/parameter is AVAILABLE, don't remove it (including its applicable/Applicable value).

I remember this one, thank you.

• Always use full docs.microsoft.com topic URLs in cmdlet reference topics. Relative topic links will work fine on the web, but they won't populate correctly when the topics are converted from markdown to MAML XML for code check-in and use at the command line.

I have a different message, let's talk about it in private.

Docs Build status updates of commit 6aaa513:

✅ 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 ad25181:

✅ 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