Merge branch 'main' into main

Author: aditisrivastava07

exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md

@@ -3,7 +3,7 @@ title: "Connect to Exchange servers using remote PowerShell"
 ms.author: chrisda
 author: chrisda
 manager: orspodek
-ms.date: 9/7/2023
+ms.date: 01/23/2026
 ms.audience: ITPro
 audience: ITPro
 ms.topic: article
@@ -74,7 +74,8 @@ If you don't have the Exchange management tools installed on your local computer
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<ServerFQDN>/PowerShell/ -Authentication Kerberos -Credential $UserCredential
    ```
 
-      **Note**: The _ConnectionUri_ value is `http`, not `https`.
+   > [!TIP]
+   > The _ConnectionUri_ value uses `http`, not `https` because the session is encrypted by the Kerberos token in the payload. Kerberos encryption removes the need to encrypt the session again using `https`.
 
 3. Run the following command:
 

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

@@ -3,7 +3,7 @@ title: About the Exchange Online PowerShell V3 module
 ms.author: chrisda
 author: chrisda
 manager: orspodek
-ms.date: 08/11/2025
+ms.date: 01/22/2026
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -704,12 +704,18 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 
 ### Current release
 
-#### Version 3.9.0
+#### Version 3.9.2
 
-- New _EnableSearchOnlySession_ switch on **Connect-IPPSSession**, which enables certain eDiscovery cmdlets and related cmdlets that connect to other Microsoft 365 services.
+- New **Add-WorkforceInsightsDelegationAccess**, **Get-WorkforceInsightsDelegationAccess**, and **Remove-WorkforceInsightsDelegationAccess** cmdlets for Workforce Insights delegation.
+- New _EXOModuleBasePath_ parameter in **Connect-ExchangeOnline** and **Connect-IPPSSession** to store temporary EXO module files in a custom path.
+- Deprecated _UseRpsSession_ parameter from **Connect-ExchangeOnline** and **Connect-IPPSSession**.
 
 ### Previous releases
 
+#### 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.
+
 #### Version 3.8.0
 
 - New _AccessToken_ parameter on **Connect-IPPSSession**.

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

@@ -3,7 +3,7 @@ title: What's new in the Exchange Online PowerShell module
 ms.author: chrisda
 author: chrisda
 manager: orspodek
-ms.date: 06/23/2025
+ms.date: 01/22/2026
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -22,6 +22,12 @@ 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 PowerShell for [the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop). Features that are currently in preview are denoted with **(preview)**.
 
+## January 2026
+
+- [Version 3.9.2](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.9.2)
+
+  For information about what's in this release, see [Version 3.9.2](exchange-online-powershell-v2.md#version-392).
+
 ## August 2025
 
 - [Version 3.9.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.9.0)

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

@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The TargetServiceEpr parameter specifies the Exchange Online Calendar Service URL of the external Microsoft 365 organization that you're trying to read free/busy information from. Valid values are:
+The TargetServiceEpr parameter specifies the Exchange Online address of the external Microsoft 365 organization that you're trying to read free/busy information from. Valid values are:
 
 - Microsoft 365 or Microsoft 365 GCC: outlook.office.com
 - Office 365 operated by 21Vianet: partner.outlook.cn

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

@@ -702,7 +702,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The Organization parameter specifies the organization when you connect using CBA or managed identity. A valid value for this parameter is the primary .onmicrosoft.com domain or tenant ID of the organization.
+The Organization parameter specifies the organization when you connect using CBA or managed identity. A valid value for this parameter is the primary .onmicrosoft.com domain of the organization.
 
 For more information about connecting with CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba).
 
@@ -922,11 +922,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**Note**: Remote PowerShell connections to Exchange Online PowerShell are deprecated. For more information, see [Deprecation of Remote PowerShell in Exchange Online](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-in-exchange-online-re-enabling/ba-p/3779692).
-
-The UseRPSSession switch allows you to connect to Exchange Online PowerShell using traditional remote PowerShell access to all cmdlets. You don't need to specify a value with this switch.
-
-If you don't use this switch, REST API mode is used for the connection, so Basic authentication in WinRM isn't required.
+**Note**: This parameter is deprecated in module version 3.9.2 or later. Remote PowerShell connections to Exchange Online PowerShell were deprecated in October 2023. For more information, see [Deprecation of Remote PowerShell in Exchange Online](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-in-exchange-online-re-enabling/ba-p/3779692).
 
 ```yaml
 Type: SwitchParameter

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

@@ -43,6 +43,7 @@ Connect-IPPSSession
  [-DisableWAM]
  [-EnableErrorReporting]
  [-EnableSearchOnlySession]
+ [-EXOModuleBasePath <String>]
  [-LogDirectoryPath <String>]
  [-LogLevel <LogLevel>]
  [-Organization <String>]
@@ -481,6 +482,28 @@ 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
+```
+
 ### -LogDirectoryPath
 
 > Applicable: Exchange Online
@@ -590,13 +613,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-**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).
-
-The UseRPSSession switch allows you to connect to Security & Compliance PowerShell using traditional remote PowerShell access to all cmdlets. You don't need to specify a value with this switch.
-
-If you don't use this switch, REST API mode is used for the connection, so Basic authentication in WinRM isn't required.
+**Note**: This parameter is deprecated in module version 3.9.2 or later. Remote PowerShell connections to Security & Compliance PowerShell were deprecated in October 2023. 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).
 
 ```yaml
 Type: SwitchParameter

exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md

@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 The Mode parameter specifies how the rule operates after it's enabled. Valid values are:
 
-- Audit: The actions that the rule would have taken are written to the message tracking log, but no any action is taken on the message that would affect delivery.
+- Audit: The actions that the rule would have taken are written to the message tracking log, but no action is taken on the message that would affect delivery.
 - AuditAndNotify: The rule operates the same as in Audit mode, but notifications are also enabled.
 - Enforce: All actions specified in the rule are taken.
 

exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md

@@ -51,11 +51,9 @@ This example creates a DLP keyword dictionary named Diseases by using the specif
 
 ### Example 2
 ```powershell
-$Keywords = Get-Content "C:\My Documents\InappropriateTerms.txt"
+$fileData = [System.IO.File]::ReadAllBytes('C:\My Documents\InappropriateTerms.txt')
 
-$EncodedKeywords = $Keywords | ForEach-Object {[System.Text.Encoding]::Unicode.GetBytes($_+"`r`n")}
-
-New-DlpKeywordDictionary -Name "Inappropriate Language" -Description "Unprofessional and inappropriate terminology" -FileData $EncodedKeywords
+New-DlpKeywordDictionary -Name "Inappropriate Language" -Description "Unprofessional and inappropriate terminology" -FileData $fileData
 ```
 
 This example creates a DLP keyword dictionary named Inappropriate Language from the file C:\\My Documents\\InappropriateTerms.txt. The file contains one term on each line.

exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md

@@ -3391,7 +3391,8 @@ This switch doesn't remove the following types of holds:
 - eDiscovery holds (maintained for compliance).
 - Litigation holds (maintained for compliance).
 - Restrictive retention policies (preserved for compliance rules).
-- Policy configurations (doesn't update policy exclusion lists).
+
+ Policy configurations of Microsoft 365 retention policies is not updated (doesn't update exclusion lists).
 
 After you use this switch in a **Set-Mailbox** command on an inactive mailbox, run the following **Get-Mailbox** command to confirm the results:
 
@@ -3419,7 +3420,9 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Online.
 
-The ExcludeFromAllOrgHolds switch excludes the mailbox from all organization-wide Microsoft 365 retention policies. This switch can only be used for inactive mailboxes. You don't need to specify a value with this switch.
+The ExcludeFromAllOrgHolds switch excludes the mailbox from all organization-wide Microsoft 365 Exchange retention policies. This switch can only be used for inactive mailboxes. You don't need to specify a value with this switch.
+
+This switch doesn't exclude the mailbox from App-Retention policies (including organization-wide).
 
 When you use this switch, use the DistinguishedName or ExchangeGuid property value for the identity of the inactive mailbox (those are the only values that guarantee uniqueness).
 

teams/teams-ps/MicrosoftTeams/Get-CsOnlineTelephoneNumberOrder.md

@@ -25,7 +25,7 @@ Get-CsOnlineTelephoneNumberOrder -OrderId <String> [-OrderType <String>]
 
 ## DESCRIPTION
 
-This `Get-CsOnlineTelephoneNumberOrder` cmdlet can be used to get the status of specific telephone number orders. Currently supported orders for retrievals are: Search [New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/microsoftteams/new-csonlinetelephonenumberorder), Direct Routing Number Upload [New-CsOnlineDirectRoutingTelephoneNumberUploadOrder](https://learn.microsoft.com/powershell/module/microsoftteams/new-csonlinedirectroutingtelephonenumberuploadorder), and Direct Routing Number Release [New-CsOnlineTelephoneNumberReleaseOrder](https://learn.microsoft.com/powershell/module/microsoftteams/New-csonlinetelephonenumberreleaseorder). When the OrderType is not indicated, the cmdlet will default to a Search order.
+This `Get-CsOnlineTelephoneNumberOrder` cmdlet can be used to get the status of specific telephone number orders. Currently supported orders for retrievals are: Search [New-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/microsoftteams/new-csonlinetelephonenumberorder), Direct Routing Number Upload [New-CsOnlineDirectRoutingTelephoneNumberUploadOrder](https://learn.microsoft.com/powershell/module/microsoftteams/new-csonlinedirectroutingtelephonenumberuploadorder), Direct Routing Number Release [New-CsOnlineTelephoneNumberReleaseOrder](https://learn.microsoft.com/powershell/module/microsoftteams/New-csonlinetelephonenumberreleaseorder), and SMS Activation/Deactivation. When the OrderType is not indicated, the cmdlet will default to a Search order.
 
 ## EXAMPLES
 
@@ -183,12 +183,34 @@ PS C:\> $results.AdditionalDetails
 Key                 Value
 ---                 -----
 TelephoneNumber     +100001
-Status       	    Error
-Message				The Number is not found.
+Status       	      Error
+Message				      The Number is not found.
 ```
 
 This example returns the status of a partially successful NumberUpdate order for a telephone number tags.
 
+### Example 7
+```powershell
+PS C:\> $results = Get-CsOnlineTelephoneNumberOrder -OrderId 0fba1633-81f0-435d-b0a8-81d073cc6f29 -OrderType SmsActivation
+
+Key                 Value
+---                 -----
+OrderId             0fba1633-81f0-435d-b0a8-81d073cc6f29
+Status              PendingTelcoCallback
+OrderType           SmsActivation
+CreatedAt           1/6/2026 7:28:09 PM +00:00
+CreatedBy           UNATTRIBUTED
+TelephoneNumbers  {System.Collections.Generic.Dictionary`2[System.String,System.Object]}
+
+PS C:\> $results.TelephoneNumbers
+
+Key                 Value
+---                 -----
+TelephoneNumber     +12065555555
+```
+
+This example returns the status of an in progress SMS Activation order.
+
 ## PARAMETERS
 
 ### -OrderId
@@ -207,7 +229,7 @@ Accept wildcard characters: False
 ```
 
 ### -OrderType
-Specifies the type of telephone number order to look up. Currently supported values are **Search**, **Release**, and **DirectRoutingNumberCreation**. If this value is unspecified, then it will default to a **Search** order.
+Specifies the type of telephone number order to look up. Currently supported values are **Search**, **Release**, **DirectRoutingNumberCreation**, and **SmsActivation/Deactivation**. If this value is unspecified, then it will default to a **Search** order.
 
 ```yaml
 Type: String
@@ -243,3 +265,4 @@ Updates in Teams PowerShell Module version 6.7.1 and later:
 [Clear-CsOnlineTelephoneNumberOrder](https://learn.microsoft.com/powershell/module/microsoftteams/clear-csonlinetelephonenumberorder)
 [New-CsOnlineDirectRoutingTelephoneNumberUploadOrder](https://learn.microsoft.com/powershell/module/microsoftteams/new-csonlinedirectroutingtelephonenumberuploadorder)
 [New-CsOnlineTelephoneNumberReleaseOrder](https://learn.microsoft.com/powershell/module/microsoftteams/New-csonlinetelephonenumberreleaseorder)
+