Skip to content

Conversation

cabailey
Copy link
Contributor

@cabailey cabailey commented Mar 8, 2025

No description provided.

Copy link

Learn Build status updates of commit 18501ed:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)
exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit a956b9a:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)
exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit 37d7c2b:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)
exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

For any questions, please:

@cabailey
Copy link
Contributor Author

@chrisda I didn't think PowerShell reference supported formatting for callouts and bold - or is that just for local help & EXO has none?

@chrisda
Copy link
Contributor

chrisda commented Mar 10, 2025

@cabailey, the cmdlet reference content serves two different opposing goals: help on the web and help at the command line. Most markdown formatting (with the exception of more than one level in bulleted/numbered lists) is supported but is lost for help at the command line. I try to strike a balance. Instead of using Alert text (with the exception of the SYNOPSIS or DESCRIPTION sections), I just use bold.

@cabailey cabailey requested a review from vilega March 10, 2025 16:41
Copy link

Learn Build status updates of commit 559722f:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)
exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit c7d2448:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)
exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

For any questions, please:

Copy link

Learn Build status updates of commit 2675d53:

✅ Validation status: passed

File Status Preview URL Details
exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)
exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md ✅Succeeded View (exchange-ps)

For more details, please refer to the build report.

For any questions, please:

@cabailey
Copy link
Contributor Author

#sign-off & merging

@cabailey cabailey merged commit b25070b into MicrosoftDocs:main Mar 11, 2025
6 checks passed
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.

4 participants