Edit

Share via

Get-InformationBarrierPolicy

  • Reference
Module:
ExchangePowerShell
Applies to:
Security & Compliance

This cmdlet is available only in Security & Compliance PowerShell. For more information, see Security & Compliance PowerShell.

Use the Get-InformationBarrierPolicy cmdlet to view information barrier policies in the Microsoft Purview compliance portal.

For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax.

Syntax

Get-InformationBarrierPolicy
   [-ExoPolicyId <Guid>]
   [<CommonParameters>]
Get-InformationBarrierPolicy
   [[-Identity] <PolicyIdParameter>]
   [-ExoPolicyId <Guid>]
   [<CommonParameters>]

Description

For more information, see Information barrier policies.

To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see Permissions in the Microsoft Purview compliance portal.

Examples

Example 1

Get-InformationBarrierPolicy | Format-Table Name,State,AssignedSegment,Segments* -Auto

This example displays a summary list of all information barrier policies.

Example 2

Get-InformationBarrierPolicy -Identity HR-Sales

This example displays detailed information for the information barrier policy named HR-Sales.

Parameters

-ExoPolicyId

The ExOPolicyId parameter specifies the information barrier policy that you want to view, but using the GUID part of the ExoPolicyId property value from the output of the Get-InformationBarrierRecipientStatus cmdlet.

You can't use this parameter with the Identity parameter.

Type:Guid
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Security & Compliance

-Identity

The Identity parameter specifies the information barrier policy that you want to view. You can use any value that uniquely identifies the policy. For example:

  • Name
  • Distinguished name (DN)
  • GUID

You can't use this parameter with the ExOPolicyId parameter.

Type:PolicyIdParameter
Position:0
Default value:None
Required:False
Accept pipeline input:True
Accept wildcard characters:False
Applies to:Security & Compliance