Skip to content

Commit 9b3dcad

Browse files
chrisdachrisda
authored
Merge pull request MicrosoftDocs#11373 from MicrosoftDocs/chrisda
Chrisda to Main
2 parents 65295b5 + b070dee commit 9b3dcad

File tree

4 files changed

+78
-34
lines changed

4 files changed

+78
-34
lines changed

‎exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,7 @@ Get-ManagementRoleAssignment [[-Identity] <RoleAssignmentIdParameter>]
3434
[-ExclusiveRecipientWriteScope <ManagementScopeIdParameter>]
3535
[-GetEffectiveUsers]
3636
[-RecipientAdministrativeUnitScope <AdministrativeUnitIdParameter>]
37+
[-RecipientGroupScope <GroupIdParameter>]
3738
[-RecipientOrganizationalUnitScope <OrganizationalUnitIdParameter>]
3839
[-RecipientWriteScope <RecipientWriteScopeType>]
3940
[-RoleAssigneeType <RoleAssigneeType>]
@@ -58,6 +59,7 @@ Get-ManagementRoleAssignment [-AssignmentMethod <AssignmentMethod[]>]
5859
[-ExclusiveRecipientWriteScope <ManagementScopeIdParameter>]
5960
[-GetEffectiveUsers]
6061
[-RecipientAdministrativeUnitScope <AdministrativeUnitIdParameter>]
62+
[-RecipientGroupScope <GroupIdParameter>]
6163
[-RecipientOrganizationalUnitScope <OrganizationalUnitIdParameter>]
6264
[-RecipientWriteScope <RecipientWriteScopeType>]
6365
[-RoleAssignee <RoleAssigneeIdParameter>]
@@ -377,6 +379,24 @@ Accept pipeline input: False
377379
Accept wildcard characters: False
378380
```
379381
382+
### -RecipientGroupScope
383+
This parameter is functional only in the cloud-based service.
384+
385+
The RecipientGroupScope parameter returns only the role assignments that are scoped to universal security groups. You can use any value that uniquely identifies the group: Name, DistinguishedName, GUID, DisplayName.
386+
387+
```yaml
388+
Type: GroupIdParameter
389+
Parameter Sets: (All)
390+
Aliases:
391+
Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
392+
393+
Required: False
394+
Position: Named
395+
Default value: None
396+
Accept pipeline input: False
397+
Accept wildcard characters: False
398+
```
399+
380400
### -RecipientOrganizationalUnitScope
381401
The RecipientOrganizationalUnitScope parameter returns only the role assignments that include the specified organizational unit (OU). If the OU tree contains spaces, enclose it in quotation marks (").
382402

‎exchange/exchange-ps/exchange/New-AntiPhishPolicy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -944,8 +944,8 @@ This parameter uses the syntax: "DisplayName;EmailAddress".
944944

945945
- DisplayName specifies the display name of the user that could be a target of impersonation. This value can contain special characters.
946946
- EmailAddress specifies the internal or external email address that's associated with the display name.
947-
- You can specify multiple values by using the syntax: "DisplayName1;EmailAddress1","DisplayName2;EmailAddress2",..."DisplayNameN;EmailAddressN". The combination of DisplayName and EmailAddress needs to be unique for each value.
948-
- You can append new values by using the syntax: `@{Add="NewDisplayName1;NewEmailAddress1","NewDisplayName2;NewEmailAddress2",..."NewDisplayNameN;NewEmailAddressN"}` or remove a value with `@{Remove="OldDisplayName1;OldEmailAddress1"}`.
947+
- You can specify multiple values by using the syntax: `"DisplayName1;EmailAddress1","DisplayName2;EmailAddress2",..."DisplayNameN;EmailAddressN"`. The combination of DisplayName and EmailAddress needs to be unique for each value.
948+
949949

950950
```yaml
951951
Type: MultiValuedProperty

‎exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -915,7 +915,8 @@ This parameter uses the syntax: "DisplayName;EmailAddress".
915915

916916
- DisplayName specifies the display name of the user that could be a target of impersonation. This value can contain special characters.
917917
- EmailAddress specifies the internal or external email address that's associated with the display name.
918-
- You can specify multiple values by using the syntax: "DisplayName1;EmailAddress1","DisplayName2;EmailAddress2",..."DisplayNameN;EmailAddressN". The combination of DisplayName and EmailAddress needs to be unique for each value.
918+
- You can specify multiple values that overwrite any existing values by using the syntax: `"DisplayName1;EmailAddress1","DisplayName2;EmailAddress2",..."DisplayNameN;EmailAddressN"`. The combination of DisplayName and EmailAddress needs to be unique for each value.
919+
- You can append new values by using the syntax: `@{Add="NewDisplayName1;NewEmailAddress1","NewDisplayName2;NewEmailAddress2",..."NewDisplayNameN;NewEmailAddressN"}` or remove an existing value using the syntax: `@{Remove="OldDisplayName1;OldEmailAddress1"}`.
919920

920921
```yaml
921922
Type: MultiValuedProperty

‎exchange/exchange-ps/exchange/Set-ManagementRoleAssignment.md

Lines changed: 54 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,7 @@ For information about the parameter sets in the Syntax section below, see [Excha
2222

2323
### RelativeRecipientWriteScope
2424
```
25-
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter>
26-
[-RecipientRelativeWriteScope <RecipientWriteScopeType>]
25+
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter> [-RecipientRelativeWriteScope <RecipientWriteScopeType>]
2726
[-Confirm]
2827
[-CustomConfigWriteScope <ManagementScopeIdParameter>]
2928
[-DomainController <Fqdn>]
@@ -35,8 +34,7 @@ Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter>
3534

3635
### CustomRecipientWriteScope
3736
```
38-
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter>
39-
[-CustomConfigWriteScope <ManagementScopeIdParameter>]
37+
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter> [-CustomConfigWriteScope <ManagementScopeIdParameter>]
4038
[-Confirm]
4139
[-CustomRecipientWriteScope <ManagementScopeIdParameter>]
4240
[-DomainController <Fqdn>]
@@ -48,8 +46,7 @@ Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter>
4846

4947
### RecipientOrganizationalUnitScope
5048
```
51-
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter>
52-
[-RecipientOrganizationalUnitScope <OrganizationalUnitIdParameter>]
49+
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter> [-RecipientOrganizationalUnitScope <OrganizationalUnitIdParameter>]
5350
[-Confirm]
5451
[-CustomConfigWriteScope <ManagementScopeIdParameter>]
5552
[-DomainController <Fqdn>]
@@ -61,9 +58,7 @@ Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter>
6158

6259
### ExclusiveScope
6360
```
64-
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter>
65-
[-ExclusiveConfigWriteScope <ManagementScopeIdParameter>]
66-
[-ExclusiveRecipientWriteScope <ManagementScopeIdParameter>]
61+
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter> [-ExclusiveConfigWriteScope <ManagementScopeIdParameter>] [-ExclusiveRecipientWriteScope <ManagementScopeIdParameter>]
6762
[-Confirm]
6863
[-DomainController <Fqdn>]
6964
[-Enabled <Boolean>]
@@ -93,6 +88,16 @@ Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter> [-CustomRes
9388
[<CommonParameters>]
9489
```
9590

91+
### RecipientGroupScope
92+
```
93+
Set-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter> -RecipientGroupScope <GroupIdParameter>
94+
[-Confirm]
95+
[-Enabled <Boolean>]
96+
[-Force]
97+
[-WhatIf]
98+
[<CommonParameters>]
99+
```
100+
96101
## DESCRIPTION
97102
When you modify a role assignment, you can specify a new predefined or custom management scope or provide an organizational unit (OU) to scope the existing role assignment.
98103

@@ -150,6 +155,46 @@ Accept pipeline input: True
150155
Accept wildcard characters: False
151156
```
152157
158+
### -RecipientAdministrativeUnitScope
159+
This parameter is functional only in the cloud-based service.
160+
161+
The RecipientAdministrativeUnitScope parameter specifies the administrative unit to scope the role assignment to.
162+
163+
Administrative units are Azure Active Directory containers of resources. You can view the available administrative units by using the Get-AdministrativeUnit cmdlet.
164+
165+
You can't use this parameter with any of the other scope parameters.
166+
167+
```yaml
168+
Type: AdministrativeUnitIdParameter
169+
Parameter Sets: RecipientAdministrativeUnitScope
170+
Aliases:
171+
Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
172+
173+
Required: True
174+
Position: Named
175+
Default value: None
176+
Accept pipeline input: False
177+
Accept wildcard characters: False
178+
```
179+
180+
### -RecipientGroupScope
181+
This parameter is functional only in the cloud-based service.
182+
183+
The RecipientGroupScope parameter specifies the universal security group to scope the role assignment to. You can use any value that uniquely identifies the group: Name, DistinguishedName, GUID, DisplayName.
184+
185+
```yaml
186+
Type: GroupIdParameter
187+
Parameter Sets: RecipientGroupScope
188+
Aliases:
189+
Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
190+
191+
Required: True
192+
Position: Named
193+
Default value: None
194+
Accept pipeline input: False
195+
Accept wildcard characters: False
196+
```
197+
153198
### -Confirm
154199
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
155200
@@ -333,28 +378,6 @@ Accept pipeline input: False
333378
Accept wildcard characters: False
334379
```
335380

336-
### -RecipientAdministrativeUnitScope
337-
This parameter is functional only in the cloud-based service.
338-
339-
The RecipientAdministrativeUnitScope parameter specifies the administrative unit to scope the role assignment to.
340-
341-
Administrative units are Azure Active Directory containers of resources. You can view the available administrative units by using the Get-AdministrativeUnit cmdlet.
342-
343-
You can't use this parameter with any of the other scope parameters.
344-
345-
```yaml
346-
Type: AdministrativeUnitIdParameter
347-
Parameter Sets: RecipientAdministrativeUnitScope
348-
Aliases:
349-
Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
350-
351-
Required: True
352-
Position: Named
353-
Default value: None
354-
Accept pipeline input: False
355-
Accept wildcard characters: False
356-
```
357-
358381
### -RecipientOrganizationalUnitScope
359382
The RecipientOrganizationalUnitScope parameter specifies the OU to scope the new role assignment to. If the OU name contains spaces, enclose the ___domain and OU in quotation marks (").
360383

0 commit comments

Comments
 (0)