You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,9 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available only in the cloud-based service.
16
16
17
-
Use the Add-UnifiedGroupLinks cmdlet to add members, owners and subscribers to Microsoft 365 Groups in your cloud-based organization. To remove members, owners and subscribers, use the Remove-UnifiedGroupLinks cmdlet. To modify other properties of Microsoft 365 Groups, use the Set-UnifiedGroup cmdlet.
17
+
Use the Add-UnifiedGroupLinks cmdlet to add members, owners and subscribers to Microsoft 365 Groups in your cloud-based organization. To remove members, owners, and subscribers, use the Remove-UnifiedGroupLinks cmdlet. To modify other properties of Microsoft 365 Groups, use the Set-UnifiedGroup cmdlet.
18
+
19
+
**Note**: You can't use this cmdlet to modify Microsoft 365 Group members, owners, or subscribers if you connect using certificate based authentication (also known as CBA or app-only authentication for unattended scripts). You can use Microsoft Graph instead. For more information, see [Group resource type](https://docs.microsoft.com/graph/api/resources/group).
18
20
19
21
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
49
49
50
-
**Note**: Currently, not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list:
50
+
**Note**: Not all protocols support authentication type filters, and even protocols that support authentication type filters don't support all authentication types. The supported combinations are described in the following lists. Use caution when mixing protocols and authentication types in the same rule.
51
+
52
+
Protocols that support authentication type filters:
51
53
52
54
- ExchangeActiveSync: BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication.
53
55
- ExchangeAdminCenter: BasicAuthentication and AdfsAuthentication.
@@ -56,6 +58,15 @@ Client access rules are like mail flow rules (also known as transport rules) for
56
58
- POP3: BasicAuthentication and OAuthAuthentication.
57
59
- RemotePowerShell: BasicAuthentication and NonBasicAuthentication.
58
60
61
+
Protcols that don't support authentication type filters:
62
+
63
+
- ExchangeWebServices
64
+
- OfflineAddressBook
65
+
- OutlookAnywhere
66
+
- PowerShellWebServices
67
+
- REST
68
+
- UniversalOutlook
69
+
59
70
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
60
71
61
72
## EXAMPLES
@@ -123,6 +134,8 @@ Valid values for this parameter are:
123
134
124
135
You can enter multiple values separated by commas. Don't use quotation marks.
125
136
137
+
**Note**: Refer to the Description section to see which authentication types can be used with what protocols.
138
+
126
139
```yaml
127
140
Type: MultiValuedProperty
128
141
Parameter Sets: (All)
@@ -279,6 +292,8 @@ Valid values for this parameter are:
279
292
280
293
You can enter multiple values separated by commas. Don't use quotation marks.
281
294
295
+
**Note**: Refer to the Description section to see which authentication types can be used with what protocols.
This parameter is functional only in the cloud-based service.
487
502
488
-
The UserRecipientFilter parameter specifies a condition for the client access rule that uses OPath filter syntax to identify the user. The syntax is `"Property -ComparisonOperator 'Value'"` (for example, `"City -eq 'Redmond'"`).
489
-
490
-
- Enclose the whole OPath filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
491
-
- Property is a filterable property. For filterable recipient properties, see [Filterable properties for the RecipientFilter parameter on Exchange cmdlets](https://docs.microsoft.com/powershell/exchange/recipientfilter-properties).
492
-
- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators).
493
-
- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`).
494
-
495
-
You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`.
496
-
497
-
For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information).
503
+
The UserRecipientFilter parameter specifies a condition for the client access rule that uses OPath filter syntax to identify the user based on a limited set of recipient properties. Client Access Rules don't support the full list of available recipient properties.
498
504
499
-
The filterable properties that you can use with this parameter are:
505
+
You can use the following properties with this parameter:
500
506
501
507
- City
502
508
- Company
503
-
- CountryOrRegion
509
+
- CountryOrRegion (ISO 3166-1 alpha-2 country code.)
504
510
- CustomAttribute1 to CustomAttribute15
505
511
- Department
506
512
- Office
507
513
- PostalCode
508
514
- StateOrProvince
509
515
- StreetAddress
510
516
517
+
The basic syntax for this parameter is `"Property -ComparisonOperator 'Value'"`:
518
+
519
+
- Property is one of the filterable properties in the list above (for example `City` or `CustomAttribute1`).
520
+
- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators).
521
+
- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead).
522
+
- Enclose the whole OPath filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
523
+
524
+
For example:
525
+
526
+
- `"City -eq 'Redmond'"`
527
+
- `"CountryOrRegion -eq 'SG'"`.
528
+
529
+
You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example:
- `"(CountryOrRegion -eq 'US' -and Department -eq 'Sales') -or Department -eq 'Research'"`.
533
+
534
+
For detailed information about OPath filter syntax in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information).
Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
51
51
52
-
**Note**: Not all authentication types are supported for all protocols. The supported authentication types per protocol are described in this list:
52
+
**Note**: Not all protocols support authentication type filters, and even protocols that support authentication type filters don't support all authentication types. The supported combinations are described in the following lists. Use caution when mixing protocols and authentication types in the same rule.
53
+
54
+
Protocols that support authentication type filters:
53
55
54
56
- ExchangeActiveSync: BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication.
55
57
- ExchangeAdminCenter: BasicAuthentication and AdfsAuthentication.
@@ -58,6 +60,15 @@ Client access rules are like mail flow rules (also known as transport rules) for
58
60
- POP3: BasicAuthentication and OAuthAuthentication.
59
61
- RemotePowerShell: BasicAuthentication and NonBasicAuthentication.
60
62
63
+
Protcols that don't support authentication type filters:
64
+
65
+
- ExchangeWebServices
66
+
- OfflineAddressBook
67
+
- OutlookAnywhere
68
+
- PowerShellWebServices
69
+
- REST
70
+
- UniversalOutlook
71
+
61
72
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
62
73
63
74
## EXAMPLES
@@ -124,6 +135,8 @@ To enter multiple values and overwrite any existing entries, use the following s
124
135
125
136
To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
126
137
138
+
**Note**: Refer to the Description section to see which authentication types can be used with what protocols.
139
+
127
140
```yaml
128
141
Type: MultiValuedProperty
129
142
Parameter Sets: (All)
@@ -286,6 +299,8 @@ To enter multiple values and overwrite any existing entries, use the following s
286
299
287
300
To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
288
301
302
+
**Note**: Refer to the Description section to see which authentication types can be used with what protocols.
This parameter is functional only in the cloud-based service.
510
525
511
-
The UserRecipientFilter parameter specifies a condition for the client access rule that uses OPath filter syntax to identify the user. The syntax is `"Property -ComparisonOperator 'Value'"` (for example, `"City -eq 'Redmond'"`).
512
-
513
-
- Enclose the whole OPath filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
514
-
- Property is a filterable property.
515
-
- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators).
516
-
- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values (for example, `500`, `$true`, `$false`, or `$null`).
517
-
518
-
You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example, `"Criteria1 -and Criteria2"` or `"(Criteria1 -and Criteria2) -or Criteria3"`.
519
-
520
-
For detailed information about OPath filters in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information).
526
+
The UserRecipientFilter parameter specifies a condition for the client access rule that uses OPath filter syntax to identify the user based on a limited set of recipient properties. Client Access Rules don't support the full list of available recipient properties.
521
527
522
-
The filterable properties that you can use with this parameter are:
528
+
You can use the following properties with this parameter:
523
529
524
530
- City
525
531
- Company
526
-
- CountryOrRegion
532
+
- CountryOrRegion (ISO 3166-1 alpha-2 country code.)
527
533
- CustomAttribute1 to CustomAttribute15
528
534
- Department
529
535
- Office
530
536
- PostalCode
531
537
- StateOrProvince
532
538
- StreetAddress
533
539
540
+
The basic syntax for this parameter is `"Property -ComparisonOperator 'Value'"`:
541
+
542
+
- Property is one of the filterable properties in the list above (for example `City` or `CustomAttribute1`).
543
+
- ComparisonOperator is an OPath comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators).
544
+
- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead).
545
+
- Enclose the whole OPath filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
546
+
547
+
For example:
548
+
549
+
- `"City -eq 'Redmond'"`
550
+
- `"CountryOrRegion -eq 'SG'"`.
551
+
552
+
You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example:
- `"(CountryOrRegion -eq 'US' -and Department -eq 'Sales') -or Department -eq 'Research'"`.
556
+
557
+
For detailed information about OPath filter syntax in Exchange, see [Additional OPATH syntax information](https://docs.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information).
0 commit comments