Merge pull request MicrosoftDocs#7199 from MicrosoftDocs/chrisda

Chrisda to Master

Author: chrisda

exchange/docs-conceptual/recipient-filters.md

@@ -221,7 +221,9 @@ When creating your own custom OPath filters, consider the following items:
   - `-like` (string comparison)
   - `-notlike` (string comparison)
 
-- Many filterable properties accept wildcard characters. If you use a wildcard character, use the **-like** operator instead of the **-eq** operator. The **-like** operator is used to find pattern matches in rich types (for example, strings) whereas the **-eq** operator is used to find an exact match.
+- Many filterable properties accept wildcard characters. If you use a wildcard character, use the **-like** operator instead of the **-eq** operator. Use the **-like** operator to find pattern matches in rich types (for example, strings). Use the **-eq** operator to find an exact match.
+
+  When you use the **-like** operator in Exchange Online PowerShell, the wildcard character is supported only as a suffix. For example, `"Department -like 'sales*'"` is allowed; `"Department -like '*sales'"` is not allowed.
 
 - For more information about operators you can use, see:
 

exchange/docs-conceptual/recipientfilter-properties.md

@@ -39,7 +39,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 
 - You typically use the object's name for properties that require a valid object value (for example, a mailbox, a distribution group, or an email address policy, but the property might also accept the object's distinguished name (DN) or globally unique identifier (GUID). To find the object's DN or GUID, use the **Get-** cmdlet that corresponds to the object's type (for example, `Get-EmailAddressPolicy | Format-List Name,DistinguishedName,GUID`).
 
-- Text string properties that accept wildcard characters require the `-like` operator (for example, `"Property -like 'abc*'"`).
+- Text string properties that accept wildcard characters require the `-like` operator (for example, `"Property -like 'abc*'"`). In Exchange Online PowerShell, you can't use the wildcard as a prefix (for example, `"Property -like '*abc'"`) is not allowed).
 
 - The Value column in the table describes the acceptable values for the *filter*, not necessarily for the property itself. For example, a property might obviously contain a date or numeric value, but when you use that property in a filter, it might be treated like a text string (no value check, and wildcards are supported).
 

exchange/exchange-ps/exchange/Set-User.md

@@ -26,6 +26,8 @@ Set-User [-Identity] <UserIdParameter>
  [-Arbitration]
  [-AssistantName <String>]
  [-AuthenticationPolicy <String>]
+ [-BlockCloudCache <Boolean>]
+ [-CanHaveCloudCache <Boolean>]
  [-CertificateSubject <MultiValuedProperty>]
  [-City <String>]
  [-Company <String>]
@@ -67,6 +69,7 @@ Set-User [-Identity] <UserIdParameter>
  [-SamAccountName <String>]
  [-SeniorityIndex <Int32>]
  [-SimpleDisplayName <String>]
+ [-SkipDualWrite]
  [-StateOrProvince <String>]
  [-StreetAddress <String>]
  [-StsRefreshTokensValidFrom <DateTime>]
@@ -75,6 +78,7 @@ Set-User [-Identity] <UserIdParameter>
  [-UMCallingLineIds <MultiValuedProperty>]
  [-UMDtmfMap <MultiValuedProperty>]
  [-UserPrincipalName <String>]
+ [-VIP <Boolean>]
  [-WebPage <String>]
  [-WhatIf]
  [-WindowsEmailAddress <SmtpAddress>]
@@ -204,6 +208,42 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -BlockCloudCache
+This parameter is available only in the cloud-based service.
+
+{{ Fill BlockCloudCache Description }}
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -CanHaveCloudCache
+This parameter is available only in the cloud-based service.
+
+{{ Fill CanHaveCloudCache Description }}
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -CertificateSubject
 This parameter is available only in on-premises Exchange.
 
@@ -935,6 +975,24 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -SkipDualWrite
+This parameter is available only in on-premises Exchange.
+
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -StateOrProvince
 The StateOrProvince parameter specifies the user's state or province.
 
@@ -1085,6 +1143,29 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -VIP
+This parameter is available only in the cloud-based service.
+
+The VIP parameter specifies whether the user is a priority account. Valid values are:
+
+- $true: The user is a priority account.
+- $false: The user is not a priority account.
+
+For more information about priority accounts, see [Manage and monitor priority accounts](https://docs.microsoft.com/microsoft-365/admin/setup/priority-accounts).
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WebPage
 The WebPage parameter specifies the user's Web page.