New Invoke-Command Workarounds article

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.

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

@@ -1,9 +1,9 @@
 ---
-title: Workarounds 
+title: Workarounds for Invoke-Command scenarios in REST API connections 
 ms.author: chrisda
 author: chrisda
 manager: dansimp
-ms.date:
+ms.date: 7/5/2023
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -17,16 +17,19 @@ search.appverid: MET150
 description: "Learn about the alternatives to Invoke-Command commands in REST API connections using the EXO V3 module."
 ---
 
-# Workarounds
+# Workarounds for Invoke-Command scenarios in REST API connections
 
-In multiple remote PowerShell connections to Exchange Online in the same window, you use the [Invoke-Command](/powershell/module/microsoft.powershell.core/invoke-command) cmdlet to run scripts or commands in specific remote PowerShell sessions. 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 PowerShell.
+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
@@ -110,15 +113,15 @@ This example shows how to create two PowerShell sessions in the same window and
   5. Now you can run commands in either session. For example:
 
      ```powershell
-     $CommandStr1 = "Get-$($ConnectionInfo1.ModulePrefix)Mailbox -ResultSize 1" 
+     $CommandStr1 = "Get-$($ConnectionInfo1.ModulePrefix)Mailbox -ResultSize 10" 
 
      Invoke-Expression $CommandStr1
      ```
 
      Or
 
      ```powershell
-     $CommandStr2 = "Get-$($ConnectionInfo2.ModulePrefix)Mailbox -ResultSize 1" 
+     $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