Merge pull request #279324 from TomJanetscheck/patch-11

Update upcoming-changes.md

Author: prmerger-automator[bot]

articles/defender-for-cloud/upcoming-changes.md

@@ -120,19 +120,19 @@ Will be applied to the following recommendations:
 
 **Announcement date: May 1, 2024**
 
-**Estimated date for change: June 2024**
+**Estimated date for change: August 2024**
 
 As part of the [MMA deprecation and the Defender for Servers updated deployment strategy](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/microsoft-defender-for-cloud-strategy-and-plan-towards-log/ba-p/3883341), all Defender for Servers security features will be provided via a single agent (MDE), or via agentless scanning capabilities, and without dependency on either Log Analytics Agent (MMA) or Azure Monitoring Agent (AMA).
 
 The new version of File Integrity Monitoring (FIM) over Microsoft Defender for Endpoint (MDE) allows you to meet compliance by monitoring critical files and registries in real-time, auditing changes, and detecting suspicious file content alterations.
 
-As part of this release, FIM experience over AMA will no longer be available through the Defender for Cloud portal beginning May 30th. For more information, see [File Integrity Monitoring experience - changes and migration guidance](prepare-deprecation-log-analytics-mma-agent.md#file-integrity-monitoring-experience---changes-and-migration-guidance).
+As part of this release, FIM experience over AMA will no longer be available through the Defender for Cloud portal beginning August 2024. For more information, see [File Integrity Monitoring experience - changes and migration guidance](prepare-deprecation-log-analytics-mma-agent.md#file-integrity-monitoring-experience---changes-and-migration-guidance).
 
 ## Deprecation of system update recommendations
 
 **Announcement date: May 1, 2024**
 
-**Estimated date for change: May 2024**
+**Estimated date for change: July 2024**
 
 As use of the Azure Monitor Agent (AMA) and the Log Analytics agent (also known as the Microsoft Monitoring Agent (MMA)) is [phased out in Defender for Servers](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/microsoft-defender-for-cloud-strategy-and-plan-towards-log/ba-p/3883341), the following recommendations that rely on those agents are set for deprecation:
 
@@ -145,7 +145,7 @@ The new recommendations based on Azure Update Manager integration [are Generally
 
 **Announcement date: May 1, 2024**
 
-**Estimated date for change: May 2024**
+**Estimated date for change: July 2024**
 
 As part of the [MMA deprecation and the Defender for Servers updated deployment strategy](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/microsoft-defender-for-cloud-strategy-and-plan-towards-log/ba-p/3883341), all Defender for Servers security features will be provided via a single agent (MDE), or via agentless scanning capabilities, and without dependency on either Log Analytics Agent (MMA) or Azure Monitoring Agent (AMA).
 
@@ -158,8 +158,6 @@ As part of this, and in a goal to reduce complexity, the following recommendatio
 | Auto provisioning of the Log Analytics agent should be enabled on subscriptions | MMA enablement      |
 | Log Analytics agent should be installed on virtual machines  | MMA enablement      |
 | Log Analytics agent should be installed on Linux-based Azure Arc-enabled machines | MMA enablement      |
-| Guest Configuration extension should be installed on machines | GC  enablement      |
-| Virtual machines' Guest Configuration extension should be deployed with system-assigned managed identity | GC  enablement      |
 | Adaptive application controls for defining safe applications should be enabled on your machines | AAC                 |
 | Adaptive application controls for defining safe applications should be enabled on your machines | AAC  |