Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr

mberdugo · mberdugo · commit 5cf4faaee718 · 2026-03-05T17:35:18.000+02:00
diff --git a/articles/azure-netapp-files/ransomware-configure.md b/articles/azure-netapp-files/ransomware-configure.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/24/2026
+ms.date: 03/05/2026
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -28,7 +28,8 @@ Advanced ransomware protection's alert mechanisms enable you to stay vigilant in
 * Attack reports are retained for 30 days.  
 * Ransomware threat notifications are sent in the Azure Activity log.  
 * It’s recommended that you enable no more than five volumes per Azure region with advanced ransomware protection to mitigate performance issues. 
-* It's recommended you increase QoS capacity by 5 to 10 percent due to potential performance impacts of advanced ransomware protection. The scale of the impact can vary based on the configurations across your Azure NetApp Files deployment.  
+* It's recommended you increase QoS capacity by 5 to 10 percent due to potential performance impacts of advanced ransomware protection. The scale of the impact can vary based on the configurations across your Azure NetApp Files deployment.
+* If your volumes have workloads with a high level of encryption and deletion, it may increase the possibility of false positives. It is recommended not to enable advanced ransomware protection on these volumes.
 
 ## Supported regions 
 
@@ -127,7 +128,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
     :::image type="content" source="./media/ransomware-configure/ransomware-threats.png" alt-text="Screenshot of ransomware threats." lightbox="./media/ransomware-configure/ransomware-threats.png":::
 
-1. If you know the files are **not** an active threat, mark the files as a **False positive**. 
+1. If you know the files are **not** an active threat, mark the active threat as a **False positive**. 
 
     If you believe the files are a threat, select **Threat**. You can then [revert the volume](snapshots-revert-volume.md) based on the last snapshot captured before the threat.
 1. Once you've resolved the threat, you can view archived ransomware reports on the same page. Reports are archived for 30 days. 
diff --git a/articles/migrate/set-discovery-scope.md b/articles/migrate/set-discovery-scope.md
@@ -18,6 +18,11 @@ This article describes how to limit the scope of discovery for servers in VMware
 
 When you set up the appliance, it connects to vCenter Server and starts discovery. Before you connect the appliance to vCenter Server, you can limit discovery to vCenter Server datacenters, clusters, a folder of clusters, hosts, a folder of hosts, or individual servers. To set the scope, you assign permissions on the account that the appliance uses to access the vCenter Server.
 
+Watch the following video to learn how to discover on-premises servers running in a VMware environment as part of your migration to Azure. 
+
+
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=edbc7f22-2ba1-44cd-a534-465dfd426a14]
+
 ## Before you start
 
 If you haven't set up a vCenter Server user account that Azure Migrate uses for discovery, do that now for [assessment](tutorial-discover-vmware.md#prepare-vmware) or [agentless migration](migrate-support-matrix-vmware-migration.md#agentless-migration).
diff --git a/articles/sentinel/ci-cd-custom-content.md b/articles/sentinel/ci-cd-custom-content.md
@@ -28,7 +28,6 @@ For more information on Sentinel content, see [About Microsoft Sentinel content
 > [!IMPORTANT]
 > The Microsoft Sentinel **Repositories** feature is currently in **PREVIEW**. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for more legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
-
 ## How Microsoft Sentinel repositories work
 
 You can deploy these Microsoft Sentinel custom content types from an external source control repository you connect to Microsoft Sentinel:
@@ -133,6 +132,13 @@ Once the workflow or pipeline is triggered, the deployment supports the followin
 
 These options are available through a feature of the PowerShell deployment script called from the workflow or pipeline. For more information on how to implement these customizations, see [Customize repository deployments](ci-cd-custom-deploy.md#customize-your-connection-configuration).
 
+## Manage Microsoft Sentinel repositories using the API
+
+For information on managing Microsoft Sentinel repositories using the API, see the [Source Control](/rest/api/securityinsights/source-control) and [Source Controls](/rest/api/securityinsights/source-controls) actions in the Microsoft Sentinel REST API.
+
+> [!IMPORTANT]
+> Starting **May 1, 2026**, older API versions used by Microsoft Sentinel repositories will no longer be supported. If you are using APIs to create and manage repository connections, transition to API version **2025-09-01**, **2025-06-01**, or **2025-07-01-preview** before June 1, 2026 to avoid service disruption. Existing repository connections aren't affected. 
+
 ## Next steps
 
 Get more examples and step by step instructions on deploying Microsoft Sentinel repositories.
diff --git a/articles/sentinel/whats-new.md b/articles/sentinel/whats-new.md
@@ -18,6 +18,75 @@ The listed features were released in the last six months. For information about
 
 [!INCLUDE [reference-to-feature-availability](includes/reference-to-feature-availability.md)]
 
+## March 2026
+
+- [Call to action: update older Microsoft Sentinel content as code (Sentinel repositories) API versions before June 2026](#call-to-action-update-older-microsoft-sentinel-content-as-code-sentinel-repositories-api-versions-before-june-2026)
+
+### Call to action: update older Microsoft Sentinel content as code (Sentinel repositories) API versions before June 2026
+
+Starting **June 1, 2026**, older API versions used by [Microsoft Sentinel repositories](ci-cd-custom-content.md) will no longer be supported. This change impacts all [Source Control](/rest/api/securityinsights/source-control) and [Source Controls](/rest/api/securityinsights/source-controls) actions in the Microsoft Sentinel REST API for the affected API versions.
+
+The retired API versions will no longer be supported, and requests using them will fail. Existing repository connections created with those APIs aren't affected, and the repositories will continue to operate.
+
+**Required action**
+
+If you're using APIs to create or manage repository connections, transition to API version **2025-06-01** or **2025-07-01-preview** before May 1, 2026 to avoid service disruption.
+
+**Affected API versions**
+
+The following API versions will be retired on May 1, 2026:
+
+<details>
+<summary><strong>Preview API versions (click to expand)</strong></summary>
+
+- 2021-03-01-preview
+- 2021-09-01-preview
+- 2021-10-01-preview
+- 2022-01-01-preview
+- 2022-04-01-preview
+- 2022-05-01-preview
+- 2022-06-01-preview
+- 2022-07-01-preview
+- 2022-08-01-preview
+- 2022-09-01-preview
+- 2022-10-01-preview
+- 2022-11-01-preview
+- 2022-12-01-preview
+- 2023-02-01-preview
+- 2023-03-01-preview
+- 2023-04-01-preview
+- 2023-05-01-preview
+- 2023-06-01-preview
+- 2023-07-01-preview
+- 2023-08-01-preview
+- 2023-09-01-preview
+- 2023-10-01-preview
+- 2023-11-01-preview
+- 2023-12-01-preview
+- 2024-01-01-preview
+- 2024-04-01-preview
+- 2024-10-01-preview
+- 2025-01-01-preview
+- 2025-04-01-preview
+- 2025-07-01-preview
+
+</details>
+
+<details>
+<summary><strong>Stable API versions (click to expand)</strong></summary>
+
+- 2023-11-01
+- 2024-03-01
+- 2024-09-01
+- 2025-03-01
+
+</details>
+
+**Recommended API versions to use:**
+- **2025-09-01** (stable)
+- **2025-06-01** (stable)
+- **2025-07-01-preview** (preview)
+
 ## February 2026
 
 ### Microsoft Sentinel UEBA behaviors layer is now generally available
