Merge branch 'main' into DLP-chrisda

Author: chrisda

README.md

@@ -1,5 +1,5 @@
 ---
-ms.date: 9/15/2023
+ms.date: 05/16/2025
 ---
 
 # Overview
@@ -23,44 +23,48 @@ Contributors who make infrequent or small updates can edit the file directly on
 2. On learn.microsoft.com, find the article that you want to update.
 3. Above the title of the article, select ![Edit this document icon.](images/m365-cc-sc-edit-icon.png) **Edit this document**.
 
-   ![Edit this document button on a learn.microsoft.com article.](images/quick-update-edit-button-on-learn-page.png)
+   ![Screenshot of how to select the Edit this document button on a learn.microsoft.com article.](images/quick-update-edit-button-on-learn-page.png)
 
-4. The corresponding article file opens on GitHub. Select ![Edit this file icon.](images/m365-cc-sc-edit-icon.png) **Edit this file**.
+4. The corresponding article file opens on GitHub. Select ![Edit icon.](images/quick-update-github-edit-icon.png) **Edit**.
 
-   ![Edit this document button on a GitHub article file.](images/quick-update-edit-button-on-github-page.png)
+   ![Screenshot of how to select the Edit button on a GitHub article file.](images/quick-update-edit-button-on-github-page.png)
 
-5. The article file opens in a line-numbered editor page where you can make updates.
+5. If a **You need to fork this repository to propose changes** page opens, select **Fork this repository**.
+
+   ![Screenshot of how to select Fork this repository on the You need to fork this repository to propose changes page.](images/quick-update-fork-this-repository-page.png)
+
+6. The article file opens in a line-numbered editor page where you can make updates.
 
    Articles on learn.microsoft.com are formatted using the Markdown language. For help on using Markdown, see [Mastering Markdown](https://guides.github.com/features/mastering-markdown/).
 
    > [!TIP]
-   > Cmdlet reference articles follow a very strict schema with limited formatting options, because the articles are also converted and used for help at the command line (`Get-Help <CmdletName`). Use existing content as a guide. For more information, see [platyPS Schema](https://github.com/PowerShell/platyPS/blob/master/docs/developer/platyPS/platyPS.schema.md).
+   > Cmdlet reference articles follow a very strict schema with limited formatting options, because the articles are also converted and used for help at the command line (`Get-Help <CmdletName>`). Use existing content as a guide. For more information, see [platyPS Schema](https://github.com/PowerShell/platyPS/blob/master/docs/developer/platyPS/platyPS.schema.md).
 
    Select **Preview** to view your changes as you go. Select **Edit** to go back to making updates.
 
    When you're finished making changes, select the green **Commit changes** button.
 
-   ![Select the green Commit changes button on the article editor page.](images/quick-update-editor-page.png)
+   ![Screenshot of how to select the green Commit changes button on the article editor page.](images/quick-update-editor-page.png)
 
-6. In the **Propose changes** dialog that opens, review and/or enter the following values:
+7. In the **Propose changes** dialog that opens, review and/or enter the following values:
    - **Commit message**: This value is required. You can accept the default value ("Update \<filename\>") or you can change it.
    - **Extended description**: This value is optional. For example:
      - An explanation of the changes.
      - @ include the GitHub alias of someone to review and merge your changes.
 
    When you're finished on the **Propose changes** dialog, select the green **Propose changes** button.
 
-   ![Select the green Propose changes button in the Propose changes dialog.](images/quick-update-propose-changes-dialog.png)
+   ![Screenshot of how to select the green Propose changes button in the Propose changes dialog.](images/quick-update-propose-changes-dialog.png)
 
-7. On the **Comparing changes** page that opens, select the green **Create pull request** button.
+8. On the **Comparing changes** page that opens, select the green **Create pull request** button.
 
-   ![Select the green Create pull request button on the Comparing changes page.](images/quick-update-comparing-changes-page.png)
+   ![Screenshot of how to select the green Create pull request button on the Comparing changes page.](images/quick-update-comparing-changes-page.png)
 
-8. On the **Open a pull request** page that opens, review the title and comments, and then select the green **Create pull request** button.
+9. On the **Open a pull request** page that opens, review the title and comments, and then select the green **Create pull request** button.
 
-   ![Select the green Create pull request button on the Open a pull request page.](images/quick-update-open-a-pull-request-page.png)
+   ![Screenshot of how to select the green Create pull request button on the Open a pull request page.](images/quick-update-open-a-pull-request-page.png)
 
-9. That's it. There's nothing more for you to do.
+10. That's it. There's nothing more for you to do.
 
    The article owner (identified in metadata) is notified about the changes to the article. Eventually, the article owner or another party will review, possibly edit, and approve your changes. After your pull request is merged, the article is updated on learn.microsoft.com.
 

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

@@ -177,6 +177,8 @@ Accept wildcard characters: False
 ```
 
 ### -Export
+**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).
+
 The Export switch filters the results by Export compliance search actions. You don't need to specify a value with this switch.
 
 You can't use this switch with the Identity, Preview, or Purge parameters.
@@ -211,7 +213,7 @@ Accept wildcard characters: False
 ```
 
 ### -Organization
-This parameter is available only in the cloud-based organization.
+This parameter is available only in the cloud-based service.
 
 This parameter is reserved for internal Microsoft use.
 

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

@@ -120,6 +120,8 @@ 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).
+
 ### Example 3
 ```powershell
 New-ComplianceSearchAction -SearchName "Remove Phishing Message" -Purge -PurgeType SoftDelete
@@ -134,6 +136,8 @@ 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).
+
 ## PARAMETERS
 
 ### -SearchName
@@ -212,6 +216,8 @@ Accept wildcard characters: False
 ```
 
 ### -EnableDedupe
+This parameter is available only in the cloud-based service.
+
 This parameter is reserved for internal Microsoft use.
 
 ```yaml
@@ -228,6 +234,9 @@ Accept wildcard characters: False
 ```
 
 ### -ExchangeArchiveFormat
+
+**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).
+
 This parameter is functional only in the cloud-based service.
 
 This parameter requires the Export role in Security & Compliance PowerShell. By default, this role is assigned only to the eDiscovery Manager role group.
@@ -257,6 +266,8 @@ Accept wildcard characters: False
 ```
 
 ### -Export
+**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).
+
 This parameter is functional only in the cloud-based service.
 
 This parameter requires the Export role in Security & Compliance PowerShell. By default, this role is assigned only to the eDiscovery Manager role group.
@@ -279,6 +290,8 @@ Accept wildcard characters: False
 ```
 
 ### -FileTypeExclusionsForUnindexedItems
+**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).
+
 The FileTypeExclusionsForUnindexedItems specifies the file types to exclude because they can't be indexed. You can specify multiple values separated by commas.
 
 ```yaml
@@ -351,6 +364,8 @@ Accept wildcard characters: False
 ```
 
 ### -IncludeSharePointDocumentVersions
+**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).
+
 This parameter is available only in the cloud-based service.
 
 The IncludeSharePointDocumentVersions parameter specifies whether to export previous versions of the document when you use the Export switch. Valid values are:
@@ -388,6 +403,8 @@ Accept wildcard characters: False
 ```
 
 ### -NotifyEmail
+**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).
+
 In Security & Compliance PowerShell, this parameter requires the Export role. By default, this is assigned only to the eDiscovery Manager role group.
 
 The NotifyEmail parameter specifies the email address target for the search results when you use the Export switch.
@@ -408,6 +425,8 @@ Accept wildcard characters: False
 ```
 
 ### -NotifyEmailCC
+**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).
+
 In Security & Compliance PowerShell, this parameter requires the Export role. By default, this role is assigned only to the eDiscovery Manager role group.
 
 The NotifyEmailCC parameter specifies the email address target for the search results when you use the Export switch.
@@ -525,6 +544,8 @@ Accept wildcard characters: False
 ```
 
 ### -Report
+**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).
+
 This parameter is functional only in the cloud-based service.
 
 The Report switch specifies the action for the content search is to export a report about the results (information about each item instead of the full set of results) that match the search criteria. You don't need to specify a value with this switch.
@@ -543,6 +564,8 @@ Accept wildcard characters: False
 ```
 
 ### -RetentionReport
+**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).
+
 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.
 
 ```yaml
@@ -577,14 +600,14 @@ Accept wildcard characters: False
 ### -Scenario
 In Security & Compliance PowerShell, this parameter requires the Preview role. By default, this role is assigned only to the eDiscovery Manager role group.
 
-The Scenario parameter specifies the scenario type when you use the Export switch. Valid values are:
+The Scenario parameter specifies the scenario type. Valid values are:
 
 - AnalyzeWithZoom: Prepare the search results for processing in Microsoft Purview eDiscovery Premium.
 - General: Exports the search results to the local computer. Emails are exported to .pst files. SharePoint and OneDrive for Business documents are exported in their native Office formats.
-- GenerateReportsOnly:
-- Inventory:
-- RetentionReports:
-- TriagePreview:
+- GenerateReportsOnly
+- Inventory
+- RetentionReports
+- TriagePreview
 
 ```yaml
 Type: ComplianceSearchActionScenario
@@ -600,6 +623,8 @@ Accept wildcard characters: False
 ```
 
 ### -Scope
+**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).
+
 The Scope parameter specifies the items to include when the action is Export. Valid values are:
 
 - IndexedItemsOnly
@@ -640,6 +665,8 @@ Accept wildcard characters: False
 ```
 
 ### -SharePointArchiveFormat
+**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).
+
 This parameter is functional only in the cloud-based service.
 
 This parameter requires the Export role. By default, this role is assigned only to the eDiscovery Manager role group.
@@ -666,6 +693,10 @@ Accept wildcard characters: False
 ```
 
 ### -ShareRootPath
+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).
+
 {{ Fill ShareRootPath Description }}
 
 ```yaml

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

@@ -12,6 +12,9 @@ ms.reviewer:
 # 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.
 
 Use the Set-ComplianceSearchAction cmdlet to change the export key on export compliance search actions in on-premises Exchange.

images/quick-update-fork-this-repository-page.png

@@ -12,6 +12,8 @@ ms.reviewer: rogupta
 # New-CsExternalAccessPolicy
 
 ## SYNOPSIS
+> [!NOTE]
+> Starting May 5, 2025, Skype Consumer Interoperability with Teams is no longer supported and the parameter EnablePublicCloudAccess can no longer be used.
 
 Enables you to create a new external access policy.
 

images/quick-update-github-edit-icon.png

@@ -12,6 +12,9 @@ ms.reviewer: rogupta
 # Set-CsExternalAccessPolicy
 
 ## SYNOPSIS
+> [!NOTE]
+> Starting May 5, 2025, Skype Consumer Interoperability with Teams is no longer supported and the parameter EnablePublicCloudAccess can no longer be used.
+
 Enables you to modify the properties of an existing external access policy.
 External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who are using custom applications built with [Azure Communication Services](/azure/communication-services/concepts/teams-interop); 3) access Skype for Business Server over the Internet, without having to log on to your internal network; 4) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as Skype; and, 5) communicate with people who are using Teams with an account that's not managed by an organization.