Skip to content

Commit d590723

Browse files
committed
More IB cmdlet updates
1 parent d9a2613 commit d590723

File tree

2 files changed

+28
-8
lines changed

2 files changed

+28
-8
lines changed

exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierPolicy.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,8 @@ The Identity parameter specifies the information barrier policy that you want to
5757

5858
- GUID
5959

60+
You can't use this parameter with the ExOPolicyId parameter.
61+
6062
```yaml
6163
Type: PolicyIdParameter
6264
Parameter Sets: Identity
@@ -70,7 +72,13 @@ Accept wildcard characters: False
7072
```
7173
7274
### -ExoPolicyId
73-
This parameter is reserved for internal Microsoft use.
75+
The ExOPolicyId parameter specifies the information barrier policy that you want to view, but using an alternative GUID value:
76+
77+
- The identity of the information barrier policy from the audit logs in Exchange Online.
78+
79+
- The GUID part of the ExoPolicyId property value in the Get-InformationBarrierRecipientStatus cmdlet results.
80+
81+
You can't use this parameter with the Identity parameter.
7482
7583
```yaml
7684
Type: Guid

exchange/exchange-ps/exchange/policy-and-compliance/Get-InformationBarrierRecipientStatus.md

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ monikerRange: "o365scc-ps"
1111
## SYNOPSIS
1212
This cmdlet is available only in the Office 365 Security & Compliance Center. For more information, see Office 365 Security & Compliance Center PowerShell (https://technet.microsoft.com/library/mt587091.aspx).
1313

14-
Use the Get-InformationBarrierRecipientStatus cmdlet to see whether specific user accounts are subject to information barrier policies and segments. You create segments by using the New-OrganizationSegment cmdlet.
14+
Use the Get-InformationBarrierRecipientStatus cmdlet to return information about recipients and their relationship to information barrier policies.
1515

1616
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
1717

@@ -22,6 +22,16 @@ Get-InformationBarrierRecipientStatus [-Identity] <RecipientIdParameter> [[-Iden
2222
```
2323

2424
## DESCRIPTION
25+
The following information is returned in the output of this cmdlet:
26+
27+
- A warning message that indicates whether or not the recipient is included in an information barrier policy.
28+
29+
- If present, the GUID part in the ExOPolicyId property value identifies the information barrier policy that the recipient is included in. You can run the command `Get-InformationBarrierPolicy -ExOPolicyId <GUID>` to identify and view the details of the policy.
30+
31+
- Basic information about the recipient (display name, alias, and last name).
32+
33+
- Recipient properties that can be used in organization segments (Department, CustomAttributeN, etc.) and the current property values for the recipient.
34+
2535
You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in Office 365 Security & Compliance Center (https://go.microsoft.com/fwlink/p/?LinkId=511920).
2636

2737
## EXAMPLES
@@ -31,16 +41,14 @@ You need to be assigned permissions in the Office 365 Security & Compliance Cent
3141
Get-InformationBarrierRecipientStatus -Identity meganb
3242
```
3343

34-
This example returns the segment and policy assignment information for the user meganb.
44+
This example returns the information barrier policy information for the user meganb.
3545

3646
### -------------------------- Example 2 --------------------------
3747
```
3848
Get-InformationBarrierRecipientStatus -Identity meganb -Identity2 alexw
3949
```
4050

41-
This example returns the information barrier policy information
42-
43-
In this example, we refer to two user accounts in Office 365: *meganb* for *Megan*, and *alexw* for *Alex*.
51+
This example returns the information barrier policy relationship for the users meganb and alexw.
4452

4553
## PARAMETERS
4654

@@ -72,7 +80,7 @@ Accept wildcard characters: False
7280
```
7381
7482
### -Identity2
75-
The Identity2 parameter specifies an optional second recipient that you want to view in relation to the first recipient specified by the Identity parameter. You can use any value that uniquely identifies the second recipient. For example:
83+
The Identity2 parameter specifies an optional second recipient when you want to view the information barrier policy relationship to the first recipient specified by the Identity parameter. You can use any value that uniquely identifies the second recipient. For example:
7684
7785
- Name
7886
@@ -86,12 +94,16 @@ The Identity2 parameter specifies an optional second recipient that you want to
8694
8795
- GUID
8896
97+
When you include this parameter in a command, you get output for each recipient.
98+
99+
You can only use this parameter with the Identity parameter; you can't use it by itself.
100+
89101
```yaml
90102
Type: RecipientIdParameter
91103
Parameter Sets: (All)
92104
Aliases:
93105
Applicable: Office 365 Security & Compliance Center
94-
Required: True
106+
Required: False
95107
Position: 1
96108
Default value: None
97109
Accept pipeline input: True (ByPropertyName, ByValue)

0 commit comments

Comments
 (0)