Merge branch 'main' into SIS-chrisda

Author: chrisda

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

@@ -231,7 +231,7 @@ The module is supported in the following versions of macOS:
   |---|---|
   |3.5.0 or later|7.4.0 or later|
 
-  PowerShell 7.4.0 is the minimum supported version of PowerShell 7 in macOS 13 or later. Module versions 3.0.0 to 3.4.0 are also supported.
+  7.4.0 is the minimum supported version of PowerShell 7 in macOS 13 or later. Module versions 3.0.0 to 3.4.0 are also supported.
 
 - **macOS 12 Monterey** and **mac OS 11 Big Sur**:
 
@@ -245,7 +245,7 @@ The module is supported in the following versions of macOS:
 
   Module versions 2.0.4 and 2.0.5 run natively on Intel processors. Apple M1 or Apple M2 processors require Apple Rosetta 2.
 
-  macOS 11 and macOS 12 don't support PowerShell 7.5.x.
+  7.4.x is the latest supported version of PowerShell 7 in macOS 11 and macOS 12.
 
 - **macOS 10.15 Catalina**:
 
@@ -254,15 +254,15 @@ The module is supported in the following versions of macOS:
   |3.0.0 to 3.4.0|7.2.0 to 7.2.22|
   |2.0.4 and 2.0.5|7.0.3 to 7.1.5 (or later)|
 
-  macOS 10.15 doesn't support PowerShell 7.3.x.
+  7.2.22 is the latest supported version of PowerShell 7 in macOS 10.15.
 
 - **macOS 10.14 Mojave**
 
   |Module version|PowerShell version|
   |---|---|
   |2.0.4 and 2.0.5|7.0.3 to 7.1.5|
 
-  macOS 10.14 doesn't support PowerShell 7.2.x.
+  7.1.5 is the latest supported version of PowerShell 7 in macOS 10.14.
 
 For instructions on installing PowerShell 7 on macOS, see [Installing PowerShell on macOS](/powershell/scripting/install/installing-powershell-core-on-macos).
 
@@ -343,7 +343,7 @@ Now you can do the [regular PowerShell prerequisites](#prerequisites-for-the-exc
   - Current versions of Windows include the required versions of the .NET Framework, so you don't need to install the .NET Framework to use the module in Windows PowerShell 5.1.
 
 - **PowerShell 7**:
-  - Module versions 3.5.0 (May 2024) or later require PowerShell 7.4.0 (November 2023) or later due to .NET 8.0 assembly dependencies. Earlier versions of PowerShell 7 might encounter compatibility issues (PowerShell 7.3.6 is more compatible than 7.3.7).
+  - Module versions 3.5.0 (May 2024) or later require PowerShell 7.4.0 (November 2023) or later due to .NET 8.0 assembly dependencies. Earlier versions of PowerShell 7 might encounter compatibility issues (PowerShell 7.3.6 is more compatible with the module than 7.3.7).
   - Module versions 3.0.0 (September 2022) to 3.4.0 (October 2023) require PowerShell 7.2.0 (November 2021) or later due to .NET 6.0 assembly dependencies in REST API cmdlets and connections.
   - Support for the module in PowerShell 7 started with version 2.0.4 (February 2021) in PowerShell 7.0.3 (July 2020).
 
@@ -357,7 +357,7 @@ Specific module version support in Windows depends on Windows PowerShell support
   |3.5.0 or later|7.4.0 or later|.NET 8.0<br/>Included in 24H2 or later.|
   |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
 
-  PowerShell 7.2.0 (.NET 6.0) is the earliest supported version in Windows 11.
+  7.2.0 (.NET 6.0) is the earliest supported version of PowerShell 7 in Windows 11.
 
 - **Windows Server 2022**:
 
@@ -367,7 +367,7 @@ Specific module version support in Windows depends on Windows PowerShell support
   |3.5.0 or later|7.4.0 or later|.NET 8.0|
   |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
 
-  PowerShell 7.2.0 (.NET 6.0) is the earliest supported version in Windows Server 2022.
+  7.2.0 (.NET 6.0) is the earliest supported version of PowerShell 7 in Windows Server 2022.
 
 - **Windows 10**:
 
@@ -395,7 +395,7 @@ Specific module version support in Windows depends on Windows PowerShell support
   |3.0.0 to 3.4.0|7.2.x|.NET 6.0|
   |2.0.4 and 2.0.5|7.0.3 to 7.1.5 (or later)|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)|
 
-  PowerShell 7.2.22 (.NET 6.0) is the latest supported version in Windows 8.1, Windows Server 2012, and Windows Server 2012 R2.
+  7.2.22 (.NET 6.0) is the latest supported version of PowerShell 7 in Windows 8.1, Windows Server 2012, and Windows Server 2012 R2.
 
 - **Windows 7.1 SP1** and **Windows Server 2008 R2 SP1**:
 
@@ -404,7 +404,7 @@ Specific module version support in Windows depends on Windows PowerShell support
   |2.0.3|5.1|.NET Framework 4.7.1|
 
   > [!NOTE]
-  > Although you can install this version of the module, you can't connect to Exchange Online PowerShell, because version 7.0.3 lacks support for REST API connections.
+  > Although you can install this version of the module, you can't connect to Exchange Online PowerShell. Module version 2.0.3 lacks support for REST API connections.
 
 ### Prerequisites for the Exchange Online PowerShell module
 
@@ -701,18 +701,22 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 
 ### Current release
 
+#### Version 3.9.0
+
+- New _EnableSearchOnlySession_ switch on **Connect-IPPSSession**, which enables certain eDiscovery cmdlets and related cmdlets that connect to other Microsoft 365 services.
+
+### Previous releases
+
 #### Version 3.8.0
 
-- Support for providing an access token with **Connect-IPPSSession**.
+- New _AccessToken_ parameter on **Connect-IPPSSession**.
 - **Get-VivaModuleFeature** now returns information about ParentFeature, ChildFeature, and PolicyModes. These values represent parent and child features of a Viva app feature along with available enablement modes for future policies.  
 - New parameters _IsUserOptedInByDefault_ on the **Add-VivaModuleFeaturePolicy** and **Update-VivaModuleFeaturePolicy** cmdlets and the corresponding property value in all **\*-VivaModuleFeaturePolicy** cmdlets. The value indicates if users are opted in or out by the policy, as long as the user doesn't set a preference.
 
   You can use this parameter to keep the feature enabled in your organization while opting out the affected users by default, effectively soft disabling the feature for those users.
 
 - Deprecated the **Get-VivaFeatureCategory** cmdlet, all category-related parameters, and return values (_CategoryId_, _IsCategoryEnabled_).
 
-### Previous releases
-
 #### Version 3.7.2
 
 - The _DisableWAM_ switch is available on the **Connect-ExchangeOnline** cmdlet to disable Web Account Manager (WAM) if you get WAM-related connection errors.

exchange/docs-conceptual/whats-new-in-the-exo-module.md

@@ -22,11 +22,17 @@ description: "Learn about the new features and functionality available in the la
 
 This article lists new features in the Exchange Online PowerShell module used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and Exchange Online Protection PowerShell for cloud protection of on-premises email environments. Features that are currently in preview are denoted with **(preview)**.
 
+## August 2025
+
+- [Version 3.9.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.9.0)
+
+  For information about what's in this release, see [Version 3.9.0](exchange-online-powershell-v2.md#version-390).
+
 ## May 2025
 
 - [Version 3.8.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.8.0)
 
-  - For information about what's in this release, see [Version 3.8.0](exchange-online-powershell-v2.md#version-380).
+  For information about what's in this release, see [Version 3.8.0](exchange-online-powershell-v2.md#version-380).
 
 ## March 2025
 

exchange/exchange-ps/ExchangePowerShell/Add-VivaModuleFeaturePolicy.md

@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.3.0 or later.
+**Note**: This parameter is available in module version 3.3.0-Preview1 or later.
 
 The IsUserControlEnabled parameter specifies whether user control is enabled by the policy. Valid values are:
 

exchange/exchange-ps/ExchangePowerShell/Add-VivaOrgInsightsDelegatedRole.md

@@ -1,4 +1,5 @@
 ---
+applicable: Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
 Locale: en-US

exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md

@@ -44,6 +44,7 @@ Connect-ExchangeOnline
  [-Device]
  [-DisableWAM]
  [-EnableErrorReporting]
+ [-EXOModuleBasePath <String>]
  [-InlineCredential]
  [-LoadCmdletHelp]
  [-LogDirectoryPath <String>]
@@ -294,7 +295,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.1.0 or later.
+**Note**: This parameter is available in module version 3.1.0-Preview1 or later.
 
 The AccessToken parameter specifies the OAuth JSON Web Token (JWT) that's used to connect to Exchange Online.
 
@@ -474,7 +475,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 2.0.4 or later, and only in PowerShell 7.
+**Note**: This parameter is available in module version 2.0.4-Preview6 or later, and only in PowerShell 7.
 
 The Device switch is typically used on computers without web browsers. You don't need to specify a value with this switch.
 
@@ -534,11 +535,33 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -EXOModuleBasePath
+
+> Applicable: Exchange Online
+
+**Note**: This parameter is available in module version 3.9.1-Preview1 or later.
+
+The EXOModuleBasePath parameter specifies the folder where the local temporary copy of the Exchange Online PowerShell module is stored. If the value contains spaces, enclose the value in quotation marks (").
+
+Connect-ExchangeOnline commands store a temporary copy of the Exchange Online module locally on the client for session connectivity. By default, the temporary copy of the module is stored in the %TMP% folder (by default, `C:\Users\<UserName>\AppData\Local\Temp`).
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -InlineCredential
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 2.0.4 or later, and only in PowerShell 7.
+**Note**: This parameter is available in module version 2.0.4-Preview6 or later, and only in PowerShell 7.
 
 The InlineCredential switch specifies whether to pass credentials directly in the Windows PowerShell window. You don't need to specify a value with this switch.
 
@@ -759,7 +782,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.2.0 or later.
+**Note**: This parameter is available in module version 3.2.0-Preview4 or later.
 
 The SigningCertificate parameter specifies the client certificate that's used to sign the format files (\*.Format.ps1xml) or script module files (.psm1) in the temporary module that Connect-ExchangeOnline creates.
 
@@ -783,7 +806,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.3.0 or later.
+**Note**: This parameter is available in module version 3.3.0-Preview1 or later.
 
 In version 3.7.0-Preview1 or later, this parameter is replaced by the LoadCmdletHelp parameter. The SkipLoadingCmdletHelp parameter is no longer required and no longer does anything, because cmdlet help files are no longer downloaded by default.
 

exchange/exchange-ps/ExchangePowerShell/Connect-IPPSSession.md

@@ -421,7 +421,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.7.2 or later.
+**Note**: This parameter is available in module version 3.7.2-Preview1 or later.
 
 The DisableWAM switch disables Web Account Manager (WAM). You don't need to specify a value with this switch.
 
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.9.0-Preview1 or later.
+**Note**: This parameter is available in module version 3.8.1-Preview1 or later.
 
 The EnableErrorReporting switch specifies whether to enable error reporting. You don't need to specify a value with this switch.
 
@@ -483,7 +483,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.9.0-Preview1 or later.
+**Note**: This parameter is available in module version 3.8.1-Preview1 or later.
 
 The LogDirectoryPath parameter specifies the location of the log files. The default location is `%TMP%\EXOCmdletTelemetry\EXOCmdletTelemetry-yyyymmdd-hhmmss.csv`.
 
@@ -505,7 +505,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.9.0-Preview1 or later.
+**Note**: This parameter is available in module version 3.8.1-Preview1 or later.
 
 The LogLevel parameter specifies the logging level. Valid values are Default and All.
 
@@ -588,7 +588,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-This parameter is available in module version 3.2.0 or later.
+**Note**: This parameter is available in module version 3.2.0-Preview3 or later.
 
 **Note**: Remote PowerShell connections to Security & Compliance PowerShell are deprecated. For more information, see [Deprecation of Remote PowerShell in Security and Compliance PowerShell](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432).
 

exchange/exchange-ps/ExchangePowerShell/Disconnect-ExchangeOnline.md

@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.2.0 or later.
+**Note**: This parameter is available in module version 3.2.0-Preview2 or later.
 
 The ConnectionId parameter specifies the REST API connections to disconnect by ConnectionId. ConnectionId is a GUID value in the output of the Get-ConnectionInformation cmdlet that uniquely identifies a connection, even if you have multiple connections open. You can specify multiple ConnectionId values separated by commas.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.2.0 or later.
+**Note**: This parameter is available in module version 3.2.0-Preview2 or later.
 
 The ModulePrefix parameter specifies the REST API connections to disconnect by ModulePrefix. When you use the Prefix parameter with the Connect-ExchangeOnline cmdlet, the specified text is added to the names of all Exchange Online cmdlets (for example, Get-InboundConnector becomes Get-ContosoInboundConnector). The ModulePrefix value is visible in the output of the Get-ConnectionInformation cmdlet. You can specify multiple ModulePrefix values separated by commas.
 

exchange/exchange-ps/ExchangePowerShell/Get-ConnectionInformation.md

@@ -90,7 +90,7 @@ This example returns a list of active REST-based connections that are using the
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.2.0 or later.
+**Note**: This parameter is available in module version 3.2.0-Preview2 or later.
 
 The ConnectionId parameter filters the connections by ConnectionId. ConnectionId is a GUID value in the output of the Get-ConnectionInformation cmdlet that uniquely identifies a connection, even if you have multiple connections open. You can specify multiple ConnectionId values separated by commas.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: This parameter is available in module version 3.2.0 or later.
+**Note**: This parameter is available in module version 3.2.0-Preview2 or later.
 
 The ModulePrefix parameter filters the connections by ModulePrefix. When you use the Prefix parameter with the Connect-ExchangeOnline cmdlet, the specified text is added to the names of all Exchange Online cmdlets (for example, Get-InboundConnector becomes Get-ContosoInboundConnector). The ModulePrefix value is visible in the output of the Get-ConnectionInformation cmdlet. You can specify multiple ModulePrefix values separated by commas.