Merge branch 'main' into TP-chrisda

Author: chrisda

exchange/docs-conceptual/exchange-online-powershell-v2.md

@@ -3,7 +3,7 @@ title: About the Exchange Online PowerShell V2 module and V3 module
 ms.author: chrisda
 author: chrisda
 manager: dansimp
-ms.date: 6/21/2023
+ms.date: 7/5/2023
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -62,13 +62,15 @@ Version 3.0.0 or later is known as the EXO V3 module. The EXO V3 module improves
 
   - REST API cmdlets have the same cmdlet names and work just like their remote PowerShell equivalents, so you don't need to update any of your scripts.
 
+    The [Invoke-Command](/powershell/module/microsoft.powershell.core/invoke-command) cmdlet doesn't work in REST API connections. For alternatives, see [Workarounds for Invoke-Command scenarios in REST API connections](invoke-command-workarounds-rest-api.md).
+
   - In Exchange Online PowerShell and in Security & Compliance PowerShell, all of the available remote PowerShell cmdlets are backed by the REST API.
 
   - In Exchange Online PowerShell and in Security & Compliance PowerShell, REST API connections are used by default. You need to use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** or **Connect-IPPSSession** command to access cmdlets in remote PowerShell mode.
 
 - Consider the following items if you connect to Exchange Online PowerShell or Security & Compliance PowerShell in remote PowerShell mode:
   - [Basic authentication in WinRM](#turn-on-basic-authentication-in-winrm) is required on your client computer.
-  - If you don't connect i remote PowerShell mode, you have access to REST API cmdlets _only_.
+  - If you don't connect in remote PowerShell mode, you have access to REST API cmdlets _only_.
   - The end of remote PowerShell support in Exchange Online PowerShell has been announced. For more information, see [Announcing Deprecation of Remote PowerShell (RPS) Protocol in Exchange Online PowerShell](https://aka.ms/RPSDeprecation).
 
 - A few REST API cmdlets in Exchange Online PowerShell have been updated with the experimental _UseCustomRouting_ switch. This switch routes the command directly to the required Mailbox server, and might improve overall performance.
@@ -132,9 +134,7 @@ Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath <Path to store lo
 
 ## Cmdlets in the Exchange Online PowerShell module
 
-All versions of the module contain nine exclusive **Get-EXO\*** cmdlets for Exchange Online PowerShell that are optimized for speed in bulk data retrieval scenarios (thousands and thousands of objects). The older related remote PowerShell cmdlets are still available.
-
-The improved Exchange Online PowerShell cmdlets that are available only in the module are listed in the following table:
+All versions of the module contain nine exclusive **Get-EXO\*** cmdlets for Exchange Online PowerShell that are optimized for speed in bulk data retrieval scenarios (thousands and thousands of objects). The improved Exchange Online PowerShell cmdlets that are available only in the module are listed in the following table:
 
 |EXO module cmdlet|Older related cmdlet|
 |---|---|
@@ -148,6 +148,9 @@ The improved Exchange Online PowerShell cmdlets that are available only in the m
 |[Get-EXOMailboxFolderPermission](/powershell/module/exchange/get-exomailboxfolderpermission)|[Get-MailboxFolderPermission](/powershell/module/exchange/get-mailboxfolderpermission)|
 |[Get-EXOMobileDeviceStatistics](/powershell/module/exchange/get-exomobiledevicestatistics)|[Get-MobileDeviceStatistics](/powershell/module/exchange/get-mobiledevicestatistics)|
 
+> [!NOTE]
+> If you open multiple connections to Exchange Online PowerShell in the same window, the **Get-EXO\*** cmdlets are always associated with the last (most recent) Exchange Online PowerShell connection. Run the following command to find the REST API session where the **Get-EXO\*** cmdlets are run: `Get-ConnectionInformation | Where-Object {$_.ConnectionUsedForInbuiltCmdlets -eq $true}`. If the last Exchange Online PowerShell connection used remote PowerShell, the **Get-EXO\*** cmdlets are run in that connection (and the output of the **Get-ConnectionInformation** command is meaningless).
+
 The connection-related cmdlets in the module are listed in the following table:
 
 |EXO module cmdlet|Older related cmdlet|Comments|

exchange/docs-conceptual/invoke-command-workarounds-rest-api.md

@@ -0,0 +1,127 @@
+---
+title: Workarounds for Invoke-Command scenarios in REST API connections 
+ms.author: chrisda
+author: chrisda
+manager: dansimp
+ms.date: 7/5/2023
+ms.audience: Admin
+audience: Admin
+ms.topic: article
+ms.service: exchange-powershell
+ms.reviewer:
+ms.localizationpriority: normal
+ms.collection: Strat_EX_Admin
+ms.custom:
+ms.assetid:
+search.appverid: MET150
+description: "Learn about the alternatives to Invoke-Command commands in REST API connections using the EXO V3 module."
+---
+
+# Workarounds for Invoke-Command scenarios in REST API connections
+
+In multiple connections to Exchange Online or Security & Compliance PowerShell in the same window, you use the [Invoke-Command](/powershell/module/microsoft.powershell.core/invoke-command) cmdlet to run scripts or commands in a specific remote PowerShell session. But, the **Invoke-Command** cmdlet doesn't work in [REST API connections](exchange-online-powershell-v2.md#updates-for-the-exo-v3-module) to Exchange Online or Security & Compliance PowerShell.
+
+This article offers REST API alternatives for scenarios that that use **Invoke-Command** commands.
+
+## Scenario 1: Run Exchange Online cmdlets
+
+This example finds the identity of any other user (`$Us = $User.Identity`).
+
+> [!TIP]
+> Other commands were required to get the values of `$User` and therefore `$Us`. Those commands aren't important. The overall approach that's being used is what's important.
+
+- **In a remote PowerShell session**: Use the **Get-PSSession** cmdlet to store the remote PowerShell session details in the variable named `$Session`, and then run the following command:
+
+  ```powershell
+  Invoke-Command -Session $Session -ScriptBlock {Get-User $Using:Us | Select-Object DistinguishedName, ExternalDirectoryObjectId} -ErrorAction SilentlyContinue
+  ```
+
+- **In a REST API session**: Run the following command:
+
+  ```powershell
+  Get-User $Us | Format-List DistinguishedName, ExternalDirectoryObjectId
+  ```
+
+This example finds the identity of a group member:
+
+- **In a remote PowerShell session**: Use the **Get-PSSession** cmdlet to store the remote PowerShell session details in the variable named `$Session`, and then run the following command:
+
+  ```powershell
+  Invoke-Command -Session $Session -ScriptBlock {Get-Recipient -Filter "Members -eq '$($User.DistinguishedName)'" -RecipientTypeDetails MailUniversalDistributionGroup | Select-Object DisplayName, ExternalDirectoryObjectId, RecipientTypeDetails} -ErrorAction SilentlyContinue -HideComputerName
+  ```
+
+- **In a REST API session**: Run the following command:
+
+  ```powershell
+  Get-Recipient -Filter "Members -eq '$($User.DistinguishedName)'" -RecipientTypeDetails MailUniversalDistributionGroup | Format-List DisplayName, ExternalDirectoryObjectId, RecipientTypeDetails
+  ```
+
+## Scenario 2: Run Exchange Online cmdlets and expand specific properties
+
+This example finds all mailboxes where the GrantSendOnBehalfTo permission is set, and then returns the users who have the permission on the mailbox.
+
+- **In a remote PowerShell session**: Use the **Get-PSSession** cmdlet to store the remote PowerShell session details in the variable named `$Session`, and then run the following command:
+
+  ```powershell
+  Invoke-Command -Session $Session -ScriptBlock {Get-Mailbox -Filter "GrantSendOnBehalfTo -ne `$null" -ErrorAction SilentlyContinue | Select-Object ExternalDirectoryObjectId, GrantSendOnBehalfTo -ExpandProperty GrantSendOnBehalfTo}
+  ```
+
+- **In a REST API session**: Run the following command:
+
+  ```powershell
+  $mailboxes = Get-Mailbox -Filter "GrantSendOnBehalfTo -ne `$null" 
+
+  foreach ($mailbox in $mailboxes) 
+
+  { 
+    $users = $mailbox | Select-Object GrantSendOnBehalfTo -ExpandProperty GrantSendOnBehalfTo | Get-User 
+
+    $users | Select-Object Name, Guid 
+  } 
+  ```
+
+## Scenario 3: Run Exchange Online cmdlets in a specific PowerShell session when multiple sessions are present
+
+This example shows how to create two PowerShell sessions in the same window and run the **Get-Mailbox** cmdlet in each session.
+
+- **In a remote PowerShell session**:
+  1. Use the **Get-PSSession** cmdlet to store the first remote PowerShell session details in the variable named `$Session1`.
+  2. Use the **Get-PSSession** cmdlet to store the second remote PowerShell session details in the variable named `$Session2`.
+  3. Run the following commands:
+
+     ```powershell
+     Invoke-Command -Session $Session1 -ScriptBlock {Get-Mailbox -ResultSize 1}
+
+     Invoke-Command -Session $Session2 -ScriptBlock {Get-Mailbox -ResultSize 1}
+     ```
+
+- **In a REST API session**:
+  1. In the first **Connect-ExchangeOnline** command, use the parameter _Prefix_ with the value C1.
+  2. Store the first REST API connection details in the variable named `$ConnectionInfo1` by running the following command:
+
+     ```powershell
+     $ConnectionInfo1 = Get-ConnectionInformation | Where-Object { $_.ModulePrefix -eq "C1"}
+     ```
+
+  3. In the second **Connect-ExchangeOnline** command, use the parameter _Prefix_ with the value C2.
+  4. Store the second REST API connection details in the variable named `$ConnectionInfo2` by running the following command:
+
+     ```powershell
+     $ConnectionInfo1 = Get-ConnectionInformation | Where-Object { $_.ModulePrefix -eq "C2"}
+     ```
+
+  5. Now you can run commands in either session. For example:
+
+     ```powershell
+     $CommandStr1 = "Get-$($ConnectionInfo1.ModulePrefix)Mailbox -ResultSize 10" 
+
+     Invoke-Expression $CommandStr1
+     ```
+
+     Or
+
+     ```powershell
+     $CommandStr2 = "Get-$($ConnectionInfo2.ModulePrefix)Mailbox -ResultSize 10" 
+
+     Invoke-Expression $CommandStr2 
+     ```

exchange/docs-conceptual/toc.yml

@@ -38,6 +38,8 @@
           href: connect-exo-powershell-managed-identity.md
         - name: Connect using C#
           href: connect-to-exo-powershell-c-sharp.md
+        - name: Workarounds for Invoke-Command in REST API connections
+          href: invoke-command-workarounds-rest-api.md
         - name: Enable or disable access to Exchange Online PowerShell
           href: disable-access-to-exchange-online-powershell.md
         - name: Exchange cmdlet syntax

exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md

@@ -168,7 +168,7 @@ The AnyOfRecipientAddressContainsWords parameter specifies a condition for the a
 - Multiple words: `no_reply,urgent,...`
 - Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...`
 
-The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50.
+The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600.
 
 You can use this condition in auto-labeling policies that are scoped only to Exchange.
 
@@ -359,7 +359,7 @@ The ExceptIfAnyOfRecipientAddressContainsWords parameter specifies an exception
 - Multiple words: `no_reply,urgent,...`
 - Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...`
 
-The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50.
+The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600.
 
 You can use this exception in auto-labeling policies that are scoped only to Exchange.
 

exchange/exchange-ps/exchange/New-DlpComplianceRule.md

@@ -428,7 +428,7 @@ The AnyOfRecipientAddressContainsWords parameter specifies a condition for the D
 - Multiple words: `no_reply,urgent,...`
 - Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...`
 
-The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50.
+The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600.
 
 You can use this condition in DLP policies that are scoped only to Exchange.
 
@@ -979,7 +979,7 @@ The ExceptIfAnyOfRecipientAddressContainsWords parameter specifies an exception
 - Multiple words: `no_reply,urgent,...`
 - Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...`
 
-The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50.
+The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600.
 
 You can use this exception in DLP policies that are scoped only to Exchange.
 

exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md

@@ -740,17 +740,13 @@ Accept wildcard characters: False
 ```
 
 ### -LanguageBlockList
-The LanguageBlockList parameter specifies the email content languages that are marked as spam when the EnableLanguageBlockList parameter value is $true. A valid value is a supported ISO 639-1 two-letter language code:
+The LanguageBlockList parameter specifies the email content languages that are marked as spam when the EnableLanguageBlockList parameter value is $true. A valid value is a supported uppercase ISO 639-1 two-letter language code:
 
-af, ar, az, be, bg, bn, br, bs, ca, cs, cy, da, de, el, en, eo, es, et, eu, fa, fi, fo, fr, fy, ga, gl, gu, ha, he, hi, hr, hu, hy, id, is, it, ja, ka, kk, kl, kn, ko, ku, ky, la, lb, lt, lv, mi, mk, ml, mn, mr, ms, mt, nb, nl, nn, pa, pl, ps, pt, rm, ro, ru, se, sk, sl, sq, sr, sv, sw, ta, te, th, tl, tr, uk, ur, uz, vi, wen, yi, zh-cn, zh-tw, and zu.
+AF, AR, AZ, BE, BG, BN, BR, BS, CA, CS, CY, DA, DE, EL, EN, EO, ES, ET, EU, FA, FI, FO, FR, FY, GA, GL, GU, HA, HE, HI, HR, HU, HY, ID, IS, IT, JA, KA, KK, KL, KN, KO, KU, KY, LA, LB, LT, LV, MI, MK, ML, MN, MR, MS, MT, NB, NL, NN, PA, PL, PS, PT, RM, RO, RU, SE, SK, SL, SQ, SR, SV, SW, TA, TE, TH, TL, TR, UK, UR, UZ, VI, WEN, YI, ZH-CN, ZH-TW, and ZU.
 
-A reference for two-letter language codes is available at [ISO 639-2](https://www.loc.gov/standards/iso639-2/php/code_list.php). Note that not all possible language codes are available as input for this parameter.
+A reference for two-letter language codes is available at [ISO 639-2](https://www.loc.gov/standards/iso639-2/php/code_list.php). Not all possible language codes are available as input for this parameter.
 
-To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`.
-
-To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
-
-To empty the list, use the value $null.
+You can specify multiple values separated by commas.
 
 ```yaml
 Type: MultiValuedProperty

exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md

@@ -21,8 +21,7 @@ For information about the parameter sets in the Syntax section below, see [Excha
 ## SYNTAX
 
 ```
-New-TenantAllowBlockListSpoofItems [-Identity] <HostedConnectionFilterPolicyIdParameter> -Action <String>
- -SendingInfrastructure <String> -SpoofedUser <String> -SpoofType <String>
+New-TenantAllowBlockListSpoofItems [-Identity] <HostedConnectionFilterPolicyIdParameter> -Action <String> -SendingInfrastructure <String> -SpoofedUser <String> -SpoofType <String>
  [-Confirm]
  [-WhatIf]
  [<CommonParameters>]

exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md

@@ -193,7 +193,11 @@ Accept wildcard characters: False
 ```
 
 ### -ObjectIds
-The ObjectIds parameter filters the log entries by object ID. The object ID is the target object that was acted upon, and depends on the RecordType and Operations values of the event. For example, for SharePoint operations, the object ID is the URL path to a file, folder, or site. For Azure Active Directory operations, the object ID is the account name or GUID value of the account.
+The ObjectIds parameter filters the log entries by object ID. The object ID is the target object that was acted upon, and depends on the RecordType and Operations values of the event.
+
+For example, for SharePoint operations, the object ID is the URL path to a file, folder, or site. To search logs in a site, add a wildcard (\*) in front of the site URL (for example, `"https://contoso.sharepoint.com/sites/test/*"`).
+
+For Azure Active Directory operations, the object ID is the account name or GUID value of the account.
 
 The ObjectId value appears in the AuditData (also known as Details) property of the event.
 

exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md

@@ -151,7 +151,7 @@ The AnyOfRecipientAddressContainsWords parameter specifies a condition for the a
 - Multiple words: `no_reply,urgent,...`
 - Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...`
 
-The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50.
+The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600.
 
 You can use this condition in auto-labeling policies that are scoped only to Exchange.
 
@@ -342,7 +342,7 @@ The ExceptIfAnyOfRecipientAddressContainsWords parameter specifies an exception
 - Multiple words: `no_reply,urgent,...`
 - Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...`
 
-The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50.
+The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600.
 
 You can use this exception in auto-labeling policies that are scoped only to Exchange.
 

exchange/exchange-ps/exchange/Set-DlpComplianceRule.md

@@ -362,7 +362,7 @@ The AnyOfRecipientAddressContainsWords parameter specifies a condition for the D
 - Multiple words: `no_reply,urgent,...`
 - Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...`
 
-The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50.
+The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600.
 
 You can use this condition in DLP policies that are scoped only to Exchange.
 
@@ -911,7 +911,7 @@ The ExceptIfAnyOfRecipientAddressContainsWords parameter specifies an exception
 - Multiple words: `no_reply,urgent,...`
 - Multiple words and phrases: `"phrase 1",word1,"phrase with , or spaces",word2,...`
 
-The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 50.
+The maximum individual word or phrase length is 128 characters. The maximum number of words or phrases is 600.
 
 You can use this exception in DLP policies that are scoped only to Exchange.
 

exchange/exchange-ps/exchange/Set-HostedContentFilterPolicy.md

@@ -742,11 +742,11 @@ Accept wildcard characters: False
 ```
 
 ### -LanguageBlockList
-The LanguageBlockList parameter specifies the email content languages that are marked as spam when the EnableLanguageBlockList parameter value is $true. A valid value is a supported ISO 639-1 two-letter language code:
+The LanguageBlockList parameter specifies the email content languages that are marked as spam when the EnableLanguageBlockList parameter value is $true. A valid value is a supported uppercase ISO 639-1 two-letter language code:
 
-af, ar, az, be, bg, bn, br, bs, ca, cs, cy, da, de, el, en, eo, es, et, eu, fa, fi, fo, fr, fy, ga, gl, gu, ha, he, hi, hr, hu, hy, id, is, it, ja, ka, kk, kl, kn, ko, ku, ky, la, lb, lt, lv, mi, mk, ml, mn, mr, ms, mt, nb, nl, nn, pa, pl, ps, pt, rm, ro, ru, se, sk, sl, sq, sr, sv, sw, ta, te, th, tl, tr, uk, ur, uz, vi, wen, yi, zh-cn, zh-tw, and zu.
+AF, AR, AZ, BE, BG, BN, BR, BS, CA, CS, CY, DA, DE, EL, EN, EO, ES, ET, EU, FA, FI, FO, FR, FY, GA, GL, GU, HA, HE, HI, HR, HU, HY, ID, IS, IT, JA, KA, KK, KL, KN, KO, KU, KY, LA, LB, LT, LV, MI, MK, ML, MN, MR, MS, MT, NB, NL, NN, PA, PL, PS, PT, RM, RO, RU, SE, SK, SL, SQ, SR, SV, SW, TA, TE, TH, TL, TR, UK, UR, UZ, VI, WEN, YI, ZH-CN, ZH-TW, and ZU.
 
-A reference for two-letter language codes is available at [ISO 639-2](https://www.loc.gov/standards/iso639-2/php/code_list.php). Note that not all possible language codes are available as input for this parameter.
+A reference for two-letter language codes is available at [ISO 639-2](https://www.loc.gov/standards/iso639-2/php/code_list.php). Not all possible language codes are available as input for this parameter.
 
 To enter multiple values and overwrite any existing entries, use the following syntax: `"Value1","Value2",..."ValueN"`.