Skip to content

Add Information Barriers policy compliance cmdlet help docs - #1222

Merged
Gary Moore (garycentric) merged 3 commits into
MicrosoftDocs:mainfrom
srmuppana:user/srmuppana/ib-policy-compliance-cmdlet-help
Sep 24, 2026
Merged

Gary Moore (garycentric) merged 3 commits into
MicrosoftDocs:mainfrom
srmuppana:user/srmuppana/ib-policy-compliance-cmdlet-help

Conversation

@srmuppana

@srmuppana Kiran Muppana (srmuppana) commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

PubOps Review Feedback

Summary

  • Add help documentation for Start-SPOInformationBarriersPolicyComplianceReport.
  • Add help documentation for Get-SPOInformationBarriersPolicyComplianceReport.
  • Document Information Barriers compliance reporting and segment updates for user-owned SharePoint Embedded containers.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 3451f6c:

✅ Validation status: passed

File Status Preview URL Details
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Get-SPOInformationBarriersPolicyComplianceReport.md ✅Succeeded View (sharepoint-ps)
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Microsoft.Online.SharePoint.PowerShell.md ✅Succeeded View (sharepoint-ps)
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Start-SPOInformationBarriersPolicyComplianceReport.md ✅Succeeded View (sharepoint-ps)

For more details, please refer to the build report.


When you specify `-ReportID`, the cmdlet returns the metadata and content of that report. The content identifies SharePoint sites, OneDrive accounts, and user-owned SharePoint Embedded containers that are noncompliant with current Information Barriers policies.

The cmdlet can return the following properties:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove this entire part -- we don't both to include the returned object shape, since that might change


### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use this updated text:

This cmdlet supports the common parameters: `-Debug`, `-ErrorAction`, `-ErrorVariable`, `-InformationAction`, `-InformationVariable`, `-OutVariable`, `-OutBuffer`, `-PipelineVariable`, `-ProgressAction`, `-Verbose`, `-WarningAction`, and `-WarningVariable`. For more information, see [about_CommonParameters](/powershell/module/microsoft.powershell.core/about/about_commonparameters).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other file too


This cmdlet generates an Information Barriers policy compliance report that identifies SharePoint sites, OneDrive accounts, and user-owned SharePoint Embedded containers that are noncompliant with current Information Barriers policies.

Use the optional update parameters to automatically update segments for noncompliant OneDrive accounts or user-owned SharePoint Embedded containers while the report is being generated. Report generation can take a long time, depending on the number of sites, accounts, and containers in the organization.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What should user do in case the report is taking a long time?

@samkabue-msft Sam M. Kabue (samkabue-msft) added the Back to submitter The pull request didn't pass the review criteria and has been returned to the writer for updates label Sep 23, 2026
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 0e2137dc-af03-423f-87f0-42a0cc88106f
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit e2ff249:

✅ Validation status: passed

File Status Preview URL Details
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Get-SPOInformationBarriersPolicyComplianceReport.md ✅Succeeded View (sharepoint-ps)
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Microsoft.Online.SharePoint.PowerShell.md ✅Succeeded View (sharepoint-ps)
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Start-SPOInformationBarriersPolicyComplianceReport.md ✅Succeeded View (sharepoint-ps)

For more details, please refer to the build report.

@samkabue-msft Sam M. Kabue (samkabue-msft) added Sign off The pull request is ready to be reviewed and merged by PubOps and removed Back to submitter The pull request didn't pass the review criteria and has been returned to the writer for updates labels Sep 24, 2026
@Shipra-M09 Shipra Choudhary (Shipra-M09) added the In review PubOps is reviewing the pull request label Sep 24, 2026
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 0838c59:

✅ Validation status: passed

File Status Preview URL Details
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Get-SPOInformationBarriersPolicyComplianceReport.md ✅Succeeded View (sharepoint-ps)
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Microsoft.Online.SharePoint.PowerShell.md ✅Succeeded View (sharepoint-ps)
sharepoint/sharepoint-ps/Microsoft.Online.SharePoint.PowerShell/Start-SPOInformationBarriersPolicyComplianceReport.md ✅Succeeded View (sharepoint-ps)

For more details, please refer to the build report.

@Shipra-M09

Copy link
Copy Markdown
Contributor

Hi Kiran Muppana (@srmuppana),

Following is a blocking issue that needs to be resolved before we can merge:

These files are missing a TOC entry. If it’s not intended for the TOC, it should have the required metadata.


Reference

Criteria used for pull request reviews

Blocking

  • When a new article is added, the same PR must also contain at least one updated TOC with an entry for the new article. Exceptions are allowed when the file has ROBOTS: NOINDEX, NOFOLLOW in the metadata.

After you resolve the blocking issues, remove the Back to submitter label and add the Sign off label again.
If you need help resolving issues in this PR, post your question in the Trusted Content Teams Channel.

Thanks,
Shipra

@Shipra-M09 Shipra Choudhary (Shipra-M09) added Back to submitter The pull request didn't pass the review criteria and has been returned to the writer for updates and removed In review PubOps is reviewing the pull request Sign off The pull request is ready to be reviewed and merged by PubOps labels Sep 24, 2026
@garycentric Gary Moore (garycentric) added Admin review The pull request has been referred to the admins for review and removed Back to submitter The pull request didn't pass the review criteria and has been returned to the writer for updates labels Sep 24, 2026
@garycentric
Gary Moore (garycentric) merged commit 0ac3d6c into MicrosoftDocs:main Sep 24, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Admin review The pull request has been referred to the admins for review Microsoft submitter sharepoint-server-itpro/svc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants