Skip to content

Commit 4e2af49

Browse files
committed
Clarify version requirements across FIM documentation - Specify 'Defender for Servers Windows client' in all version requirement mentions - Update file-integrity-monitoring-overview.md, file-integrity-monitoring-enable-defender-endpoint.md, and release-notes.md
1 parent 50ef9b6 commit 4e2af49

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

articles/defender-for-cloud/file-integrity-monitoring-enable-defender-endpoint.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to enable File Integrity Monitoring when you collect data
44
author: Elazark
55
ms.author: elkrieger
66
ms.topic: how-to
7-
ms.date: 06/25/2025
7+
ms.date: 02/24/2026
88
ms.custom: sfi-image-nochange
99
#customer intent: As a security administrator, I want to enable File Integrity Monitoring so that I can detect unauthorized changes to critical files.
1010
---
@@ -19,7 +19,7 @@ After you enable Defender for Servers Plan 2, follow the instructions in this ar
1919
>
2020
> - If you use a previous version of File Integrity Monitoring with the Log Analytics agent (Microsoft Monitoring agent (MMA)) or the Azure Monitor agent (AMA), you can [migrate to the new File Integrity Monitoring experience](migrate-file-integrity-monitoring.md).
2121
> - File Integrity Monitoring powered by Microsoft Defender for Endpoint requires a minimum agent version. [Update the agent](#verify-defender-for-endpoint-client-version) as needed.
22-
> - **Windows (legacy machines/downlevel clients)**: 10.8799 or later.
22+
> - **Windows (legacy machines/downlevel clients)**: Defender for Servers Windows client (MDE agent) version 10.8799 or later.
2323
> - **Linux**: 30.124082 or later.
2424
2525
## Prerequisites

articles/defender-for-cloud/release-notes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,12 +45,12 @@ This article summarizes what's new in Microsoft Defender for Cloud. It includes
4545

4646
February 28, 2026
4747

48-
Due to a pipeline change in Microsoft Defender for Endpoint (MDE), File Integrity Monitoring now requires Microsoft Defender for Endpoint agent version 10.8799 or above for proper functionality on legacy Windows machines (downlevel clients).
48+
Due to a pipeline change in Microsoft Defender for Endpoint (MDE), File Integrity Monitoring now requires the **Defender for Servers Windows client (Microsoft Defender for Endpoint agent) version 10.8799 or above** for proper functionality on legacy Windows machines (downlevel clients).
4949

5050
**Key details:**
5151

5252
- **Affected systems**: Legacy Windows machines (Windows Server 2016, Windows Server 2012 R2, and other downlevel clients)
53-
- **Required version**: MDE agent 10.8799 or later
53+
- **Required version**: Defender for Servers Windows client (MDE agent) 10.8799 or later
5454
- **Impact**: FIM monitoring will not function properly on versions below the minimum requirement
5555

5656
Learn more about [File Integrity Monitoring](file-integrity-monitoring-overview.md) and how to [enable File Integrity Monitoring](file-integrity-monitoring-enable-defender-endpoint.md).

0 commit comments

Comments
 (0)