Merge pull request #5295 from rlitinsky/patch-82

Update OS prerequisite for Defender sensor v3.x

Author: padmagit77

defender-for-identity/deploy/prerequisites-sensor-version-3.md

@@ -6,7 +6,7 @@ ms.topic: install-set-up-deploy
 ms.reviewer: rlitinsky
 ---
 
-# Microsoft Defender for Identity sensor v3.x prerequisites (Preview)
+# Microsoft Defender for Identity sensor v3.x prerequisites
 
 This article describes the requirements for installing the Microsoft Defender for Identity sensor v3.x.
 
@@ -41,7 +41,7 @@ The following table summarizes the server requirements and recommendations for t
 
 |Prerequisite / Recommendation |Description  |
 |---------|---------|
-|Operating System|The domain controller must have both:<br> - Windows Server 2019 or later<br> - [June 2025 Cumulative Update](https://support.microsoft.com/en-us/topic/june-10-2025-kb5060526-os-build-20348-3807-4e9453c4-6602-48ea-b349-689cd66dfdb9) or later.|
+|Operating System|The domain controller must have both:<br> - Windows Server 2019 or later<br> - [October 2025 Cumulative Update](https://support.microsoft.com/en-us/topic/october-14-2025-kb5066782-os-build-20348-4294-f4af3c9e-7a60-4d17-a964-cfe1f1dd15f6) or later.|
 |Previous installations| Before activating the sensor on a domain controller, make sure that the domain controller doesn't have Defender for Identity sensor V2.x already deployed.|
 |Specifications|  A domain controller server with a minimum of:<br> - two cores<br>- 6 GB of RAM|
 |Performance| For optimal performance, set the **Power Option** of the machine running the Defender for Identity sensor to **High Performance**.        |
@@ -63,18 +63,18 @@ The following table describes memory requirements on the server used for the Def
 > [!IMPORTANT]
 > When running as a virtual machine, all memory must be allocated to the virtual machine at all times.
 
-## Configure Unified Sensor to support advanced identity detections (Preview)
+## Configure Unified Sensor to support advanced identity detections
 
 Applying the **Unified Sensor RPC Audit** tag enables a new, tested capability on the machine, improving security visibility and unlocking additional identity detections. Once applied, the configuration is enforced on **existing and future devices** that match the rule criteria. The tag itself is visible in the Device Inventory, providing admins with transparency and auditing capabilities.
 
 **Steps to apply the configuration:**
 
 1. In the **Microsoft Defender portal**, navigate to: **System > Settings > Microsoft Defender XDR > Asset Rule Management**.
-1. Select **Create a new rule**
+1. Select **Create a new rule**.
 
- ![Screenshot that shows how to add a new rule.](media/prerequisites-sensor-version-3/new-rule.png)
+    ![Screenshot that shows how to add a new rule.](media/prerequisites-sensor-version-3/new-rule.png)
 
-3. In the side panel:
+1. In the side panel:
 
    1. Enter a **Rule name** and **Description**.
 
@@ -86,17 +86,17 @@ Applying the **Unified Sensor RPC Audit** tag enables a new, tested capability o
 
 1. **Add the tag** `Unified Sensor RPC Audit` to the selected devices.    
 
- ![Screenshot that shows the config tag.](media/prerequisites-sensor-version-3/tag.png)
+    ![Screenshot that shows the config tag.](media/prerequisites-sensor-version-3/tag.png)
 
-5. Select **Next** to review and finish creating the rule and then select **Submit**.
+1. Select **Next** to review and finish creating the rule and then select **Submit**.
 
 ### Updating rules
    Offboarding a device from this configuration can be done **only** from **deleting the asset rule** or **modifying the rule conditions** so the device no longer matches.
 
->[!NOTE]
+> [!NOTE]
 > It may take up to 1 hour for changes to be reflected in the portal.
 
-Learn more about Asset Management Rule [here](/defender-xdr/configure-asset-rules)
+Learn more about Asset Management Rule [here](/defender-xdr/configure-asset-rules).
 
 ## Configure Windows auditing