[AutoPublish] main to live - 02/23 15:38 PST | 02/24 05:08 IST

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

@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 The Export switch filters the results by Export compliance search actions. You don't need to specify a value with this switch.
 

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

@@ -15,16 +15,17 @@ title: New-ComplianceSearchAction
 ## SYNOPSIS
 This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the New-ComplianceSearchAction cmdlet to create actions for content searches in Exchange Server and in the Microsoft Purview compliance portal.
+Use the New-ComplianceSearchAction cmdlet to create actions for content searches in Exchange Server and in Microsoft Purview.
+
+**Note**: Several of the parameters on this cmdlet are functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
 ## SYNTAX
 
 ### Export
 ```
-New-ComplianceSearchAction [-SearchName] <String[]>
- [-Export]
+New-ComplianceSearchAction [-SearchName] <String[]> [-Export]
  [-ActionName <String>]
  [-ArchiveFormat <ComplianceExportArchiveFormat>]
  [-Confirm]
@@ -55,8 +56,7 @@ New-ComplianceSearchAction [-SearchName] <String[]>
 
 ### Preview
 ```
-New-ComplianceSearchAction [-SearchName] <String[]>
- [-Preview]
+New-ComplianceSearchAction [-SearchName] <String[]> [-Preview]
  [-ActionName <String>]
  [-Confirm]
  [-Force]
@@ -75,8 +75,7 @@ New-ComplianceSearchAction [-SearchName] <String[]>
 
 ### Purge
 ```
-New-ComplianceSearchAction [-SearchName] <String[]>
- [-Purge]
+New-ComplianceSearchAction [-SearchName] <String[]> [-Purge]
  [-PurgeType <ComplianceDestroyType>]
  [-ActionName <String>]
  [-Confirm]
@@ -126,7 +125,7 @@ New-ComplianceSearchAction -SearchName "Project X" -Export
 
 This example creates an export search action for the content search named Project X.
 
-**Note**: After May 26, 2025, this example no longer works. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This example works only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 ### Example 3
 ```powershell
@@ -142,7 +141,7 @@ New-ComplianceSearchAction -SearchName "Case 321 All Sites" -Export -SharePointA
 
 This example exports the results returned by the content search named "Case 321 All Sites". The search results are compressed and exported to a single ZIP file. If the search included any Exchange locations, the search results are exported as one PST file per mailbox.
 
-**Note**: After May 26, 2025, this example no longer works. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This example works only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 ## PARAMETERS
 
@@ -253,7 +252,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 This parameter is functional only in the cloud-based service.
 
@@ -286,7 +285,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 This parameter is functional only in the cloud-based service.
 
@@ -312,7 +311,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 The FileTypeExclusionsForUnindexedItems specifies the file types to exclude because they can't be indexed. You can specify multiple values separated by commas.
 
@@ -394,7 +393,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 This parameter is available only in the cloud-based service.
 
@@ -437,7 +436,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 In Security & Compliance PowerShell, this parameter requires the Export role. By default, this is assigned only to the eDiscovery Manager role group.
 
@@ -461,7 +460,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 In Security & Compliance PowerShell, this parameter requires the Export role. By default, this role is assigned only to the eDiscovery Manager role group.
 
@@ -485,6 +484,8 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+
 In Security & Compliance PowerShell, this parameter requires the Preview role. By default, this role is assigned only to the eDiscovery Manager role group.
 
 The Preview switch specifies the action for the content search is to preview the results that match the search criteria. You don't need to specify a value with this switch.
@@ -592,7 +593,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 This parameter is functional only in the cloud-based service.
 
@@ -614,7 +615,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 The RetentionReport switch specifies the action for the content search is to export a retention report. You don't need to specify a value with this switch.
 
@@ -679,7 +680,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 The Scope parameter specifies the items to include when the action is Export. Valid values are:
 
@@ -725,7 +726,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 This parameter is functional only in the cloud-based service.
 
@@ -757,7 +758,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
+**Note**: This parameter is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 {{ Fill ShareRootPath Description }}
 

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

@@ -13,10 +13,7 @@ title: Set-ComplianceSearchAction
 # Set-ComplianceSearchAction
 
 ## SYNOPSIS
-> [!NOTE]
-> After May 26, 2025, this cmdlet is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
-
-This cmdlet is functional only in on-premises Exchange.
+This cmdlet is functional only in on-premises Exchange. For more information, see [May 2025 changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
 Use the Set-ComplianceSearchAction cmdlet to change the export key on export compliance search actions in on-premises Exchange.
 

teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md

@@ -20,7 +20,7 @@ Use the New-CsComplianceRecordingForCallQueueTemplate cmdlet to create a Complia
 
 ```
 New-CsComplianceRecordingForCallQueueTemplate -Name <String> -Description <String> -BotApplicationInstanceObjectId <String>
- [-RequiredDuringCall <Boolean>] [-RequiredBeforeCall <Boolean>] [-CurrentInvitationCount <Int32>]
+ [-RequiredDuringCall] [-RequiredBeforeCall] [-CurrentInvitationCount <Int32>]
  [-PairedApplicationInstanceObjectId <String>] [<CommonParameters>]
 ```
 
@@ -31,7 +31,7 @@ Use the New-CsComplianceRecordingForCallQueueTemplate cmdlet to create a Complia
 
 ### Example 1
 ```
-New-CsComplianceRecordingForCallQueueTemplate -Name "Customer Service" -Description "Required before/during call" -BotApplicationInstanceObjectId 14732826-8206-42e3-b51e-6693e2abb698 -RequiredDuringCall $true -RequiredBeforeCall $true
+New-CsComplianceRecordingForCallQueueTemplate -Name "Customer Service" -Description "Required before/during call" -BotApplicationInstanceObjectId 14732826-8206-42e3-b51e-6693e2abb698 -RequiredDuringCall -RequiredBeforeCall
 ```
 
 This example creates a new Compliance Recording for Call Queue template.
@@ -126,13 +126,13 @@ Indicates if the compliance recording for call queues bot must be able to join t
 *Strict recording* - if the bot can't join the call, the call will end.
 
 ```yaml
-Type: System.Booleen
+Type: SwitchParameter
 Parameter Sets: (All)
 Aliases:
 
 Required: False
 Position: Named
-Default value: False
+Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
@@ -143,13 +143,13 @@ Indicates if the compliance recording for call queues bot must remain part of th
 *Strict recording* - if the bot leaves the call, the call will end.
 
 ```yaml
-Type: System.Booleen
+Type: SwitchParameter
 Parameter Sets: (All)
 Aliases:
 
 Required: False
 Position: Named
-Default value: False
+Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
 ```