Merge pull request #312807 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-08 12:00 UTC

Author: learn-build-service-prod[bot]

articles/defender-for-iot/organizations/ot-virtual-appliances.md

@@ -41,8 +41,19 @@ This section outlines considerations for virtual appliance components, for both
 
 ## OT network sensor VM requirements
 
+The following tables list system requirements for OT network sensors on virtual appliances, and performance measured in our qualification labs.
+
 For all deployments, bandwidth results for virtual machines may vary, depending on the distribution of protocols and the actual hardware resources that are available, including the CPU model, memory bandwidth, and IOPS.
 
+|Hardware profile  |Performance / Monitoring  |Physical specifications  |
+|---------|---------|---------|
+|**C5600**     |   **Max bandwidth**: 2.5 Gb/sec <br>**Max monitored assets**: 12,000      | **vCPU**: 32 <br>**Memory**: 32 GB <br>**Storage**: 5.6 TB (600 IOPS)        |
+|**E1800**     |    **Max bandwidth**: 800 Mb/sec <br>**Max monitored assets**: 10,000      | **vCPU**: 8 <br>**Memory**: 32 GB <br>**Storage**: 1.8 TB (300 IOPS)        |
+|**E1000**     |    **Max bandwidth**: 800 Mb/sec <br>**Max monitored assets**: 10,000      | **vCPU**: 8 <br>**Memory**: 32 GB <br>**Storage**: 1 TB (300 IOPS)        |
+|**E500**     |    **Max bandwidth**: 800 Mb/sec <br>**Max monitored assets**: 10,000      | **vCPU**: 8 <br>**Memory**: 32 GB <br>**Storage**: 500 GB (300 IOPS)        |
+|**L500**     |   **Max bandwidth**: 160 Mb/sec <br>**Max monitored assets**: 1,000      | **vCPU**: 4 <br>**Memory**: 8 GB <br>**Storage**: 500 GB (150 IOPS)        |
+|**L100**     |    **Max bandwidth**: 100 Mb/sec <br>**Max monitored assets**: 800      | **vCPU**: 4 <br>**Memory**: 8 GB <br>**Storage**: 100 GB (150 IOPS)        |
+
 To review system requirements and performance details for OT network sensors on specific virtual appliances, see the [appliance catalog](appliance-catalog/index.yml).
 
 > [!NOTE]

articles/sentinel/ci-cd-custom-content.md

@@ -137,7 +137,7 @@ These options are available through a feature of the PowerShell deployment scrip
 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. 
+> Starting **June 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
 

articles/sentinel/siem-migration.md

@@ -27,7 +27,7 @@ The SIEM Migration experience includes the following features:
 
 ## Prerequisites
 
-- Microsoft Sentinel in Microsoft Defender portal
+- [Microsoft Sentinel in Microsoft Defender portal](/unified-secops/microsoft-sentinel-onboard#onboard-microsoft-sentinel)
 - At least Microsoft Sentinel Contributor permissions in the Microsoft Sentinel workspace
 - <a href="/copilot/security/get-started-security-copilot" target="_blank">Security Copilot</a> enabled in your tenant with at least a [workspace operator role](/copilot/security/authentication#assign-security-copilot-access) assigned
 

articles/sentinel/whats-new.md

@@ -30,11 +30,11 @@ The retired API versions will no longer be supported, and requests using them wi
 
 **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.
+If you're using APIs to create or 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.
 
 **Affected API versions**
 
-The following API versions will be retired on May 1, 2026:
+The following API versions will be retired on June 1, 2026:
 
 <details>
 <summary><strong>Preview API versions (click to expand)</strong></summary>