[AutoPublish] main to live - 06/17 20:44 PDT | 06/18 09:14 IST#1183
Merged
Conversation
* Add auto archive public documentation files * Update cmdlet documentation for File Archive Policies Added, updated, and removed cmdlet documentation for File Archive Policies. * Address PR review feedback for file archive policy cmdlets - Add missing front matter properties (applicable, title, author, ms.author, ms.reviewer) - Use 'This cmdlet...' instead of repeating cmdlet name in descriptions - Remove assumed admin role requirement line - Remove 'PS C:\>' prefix from examples - Use lowercase 'file archive policy' instead of Title Case - Remove (e.g., ...) examples from parameter descriptions - Update CommonParameters with backtick-formatted params and new URL - Move preview note from NOTES to Description using [!NOTE] decorator - Format WhatIf in backticks when referenced in prose Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address remaining review feedback - Use backticks instead of quotes for parameter values in prose (SelectedSites, AllSites, Active, Inactive) - Use [!IMPORTANT] tag for LastAccessDateCriteria July 2025 accuracy note - Move Inactive state note from NOTES section to Description in New-SPOFileArchivePolicy Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Populate RELATED LINKS sections with cross-references to all file archive policy cmdlets Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update PolicyType and State parameter types from String to enums - PolicyType: String -> SPOFileArchivePolicyType (in New-SPO and Set-SPO) - State: String -> SPOFileArchivePolicyState (in Set-SPO) - Updated SYNTAX blocks to match Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Hector Mota <hemota@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…#1182) * Add -PolicyName parameter to Start-SPORestrictedAccessForSitesInsights * Fixing format issues * Addressing Format --------- Co-authored-by: Ruchika Mittal <v-rucmittal@microsoft.com>
Contributor
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@MicrosoftDocs/marveldocs-pubops
This is an automated pull request to publish changes from the main branch to the live branch. Merging this PR will publish the changes to the live learn.microsoft.com site.
Auto-merge is enabled. The repo will attempt to automatically merge this PR when all required checks pass. If the PR is automatically merged, no further action is required to publish the contents of this PR.
In the event the repo can't automatically merge this PR, the Manual merge required label will be added to the PR. If this happens, complete the following checks before merging this PR:
After you've completed these steps, manually merge the PR.
If you have questions, post a message to https://aka.ms/tcphelp.