Skip to content

Commit 1cccff3

Browse files
Merge pull request #281194 from dcurwin/wi-285688-mma-retirement-july18-2024
MMA deprecation
2 parents 40277cc + cd5b2ee commit 1cccff3

File tree

1 file changed

+45
-17
lines changed

1 file changed

+45
-17
lines changed

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

Lines changed: 45 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -29,24 +29,52 @@ This article summarizes what's new in Microsoft Defender for Cloud. It includes
2929

3030
## July 2024
3131

32-
|Date | Category | Update|
33-
|--|--|--|
34-
|July 15|Preview|[Binary Drift Public Preview in Defender for Containers](#binary-drift-public-preview-now-available-in-defender-for-containers)|
35-
|July 14|GA|[Automated remediation scripts for AWS and GCP are now GA](#automated-remediation-scripts-for-aws-and-gcp-are-now-ga)|
32+
| Date | Category | Update |
33+
| ------- | --------------- | ------------------------------------------------------------ |
34+
| July 18 | Upcoming update | [Deprecation of MMA-related features as part of agent retirement](#deprecation-of-mma-related-features-as-part-of-agent-retirement) |
35+
| July 15 | Preview | [Binary Drift Public Preview in Defender for Containers](#binary-drift-public-preview-now-available-in-defender-for-containers) |
36+
| July 14 | GA | [Automated remediation scripts for AWS and GCP are now GA](#automated-remediation-scripts-for-aws-and-gcp-are-now-ga) |
3637
| July 11 | Upcoming update | [GitHub application permissions update](#github-application-permissions-update) |
37-
| July 10 | GA | [Compliance standards are now GA](#compliance-standards-are-now-ga) |
38-
| July 9 | Upcoming update | [Inventory experience improvement](#inventory-experience-improvement) |
39-
|July 8 | Upcoming update | [Container mapping tool to run by default in GitHub](#container-mapping-tool-to-run-by-default-in-github) |
38+
| July 10 | GA | [Compliance standards are now GA](#compliance-standards-are-now-ga) |
39+
| July 9 | Upcoming update | [Inventory experience improvement](#inventory-experience-improvement) |
40+
| July 8 | Upcoming update | [Container mapping tool to run by default in GitHub](#container-mapping-tool-to-run-by-default-in-github) |
41+
42+
### Deprecation of MMA-related features as part of agent retirement
43+
44+
July 18, 2024
45+
46+
**Estimated date for change**: August 2024
47+
48+
As part of the [deprecation of the Microsoft Monitoring Agent (MMA) and the updated Defender for Servers deployment strategy](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/microsoft-defender-for-cloud-strategy-and-plan-towards-log/ba-p/3883341), all security features for Defender for Servers will now be provided through a single agent (Defender for Endpoint), or via agentless scanning capabilities. This won't require dependence on either the MMA or Azure Monitoring Agent (AMA).
49+
50+
As we approach the agent's retirement in August 2024, the following MMA-related features will be removed from the Defender for Cloud portal:
51+
52+
- Display of MMA installation status on the **Inventory** and **Resource Health** blades.
53+
- [The capability](quickstart-onboard-machines.md#connect-on-premises-machines-by-using-the-azure-portal) to onboard new non-Azure servers to Defender for Servers via Log Analytics workspaces will be removed from both the **Inventory** and **Getting Started** blades.
54+
55+
> [!NOTE]
56+
> We recommend that current customers, who have onboarded on-premises servers using the [legacy approach](quickstart-onboard-machines.md#connect-on-premises-machines-by-using-the-azure-portal), should now connect these machines via Azure Arc-enabled servers. We also recommend enabling the Defender for Servers Plan 2 on the Azure subscriptions to which these servers are connected.
57+
>
58+
>For those customers who have selectively enabled Defender for Servers Plan 2 on specific Azure VMs through the [legacy approach](quickstart-onboard-machines.md#connect-on-premises-machines-by-using-the-azure-portal), we recommend enabling the Defender for Servers Plan 2 on the Azure subscriptions of these machines. You can then exclude individual machines from the Defender for Servers coverage using the Defender for Servers [per-resource configuration](tutorial-enable-servers-plan.md#enable-defender-for-servers-at-the-resource-level).
59+
>
60+
> These steps will ensure there is no loss of security coverage due to the retirement of the Log Analytics agent.
61+
62+
To maintain security continuity, we advise customers with Defender for Servers Plan 2 to enable [agentless machine scanning](enable-agentless-scanning-vms.md) and [integration with Microsoft Defender for Endpoint](enable-defender-for-endpoint.md) on their subscriptions.
63+
64+
You can use [this custom workbook](https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Workbooks/Defender%20for%20Servers%20Deployment%20Status) to keep track of your Log Analytics Agent (MMA) estate and monitor the deployment status of Defender for Servers across Azure VMs and Azure Arc machines.
65+
66+
For more information, see [Prepare for retirement of the Log Analytics agent](prepare-deprecation-log-analytics-mma-agent.md).
4067

4168
### Binary Drift public preview now available in Defender for Containers
4269

4370
We are introducing the public preview of Binary Drift for Defender for Containers. This feature aids in identifying and mitigating potential security risks associated with unauthorized binaries in your containers. Binary Drift autonomously identifies and sends alerts about potentially harmful binary processes within your containers. Furthermore, it allows the implementation of a new Binary Drift Policy to control alert preferences, offering the ability to tailor notifications to specific security needs.
4471
For more information about this feature, see [Binary Drift Detection](binary-drift-detection.md)
4572

4673
### Automated remediation scripts for AWS and GCP are now GA
74+
4775
July 14, 2024
4876

49-
In March, we released automated remediation scripts for AWS & GCP to Public Preview, that allows you to remediate recommendations for AWS & GCP at scale programmatically.
77+
In March, we released automated remediation scripts for AWS & GCP to Public Preview, that allows you to remediate recommendations for AWS & GCP at scale programmatically.
5078

5179
Today we are releasing this feature to generally available (GA). [Learn how to use automated remediation scripts](/azure/defender-for-cloud/implement-security-recommendations)>
5280

@@ -62,7 +90,7 @@ As part of this update, the GitHub application will require GitHub Copilot Busin
6290

6391
Permissions can be granted in two different ways:
6492

65-
1. In your GitHub organization, navigate to the Microsoft Security DevOps application within **Settings > GitHub Apps** and accept the permissions request.
93+
1. In your GitHub organization, navigate to the Microsoft Security DevOps application within **Settings > GitHub Apps** and accept the permissions request.
6694

6795
1. In an automated email from GitHub Support, select **Review permission request** to accept or reject this change.
6896

@@ -96,14 +124,14 @@ With DevOps security capabilities in Microsoft Defender Cloud Security Posture M
96124

97125
## June 2024
98126

99-
|Date | Category | Update |
100-
|--|--|--|
101-
| June 27 | GA | [Checkov IaC Scanning in Defender for Cloud](#ga-checkov-iac-scanning-in-defender-for-cloud). |
102-
| June 24 | Update | [Change in pricing for multicloud Defender for Containers](#update-change-in-pricing-for-defender-for-containers-in-multicloud) |
103-
| June 20 | Upcoming deprecation | [Reminder of deprecation for adaptive recommendations at Microsoft Monitoring Agent (MMA) deprecation](#deprecation-reminder-of-deprecation-for-adaptive-recommendations).<br/><br/> Estimated deprecation August 2024. |
104-
| June 10 | Preview | [Copilot for Security in Defender for Cloud](#preview-copilot-for-security-in-defender-for-cloud) |
105-
| June 10 | Upcoming update |[SQL vulnerability assessment automatic enablement using express configuration on unconfigured servers](#update-sql-vulnerability-assessment-automatic-enablement).<br/><br/> Estimated update: July 10, 2024. |
106-
| June 3 | Upcoming update |[Changes in identity recommendations behavior](#update-changes-in-identity-recommendations-behavior)<br/><br/> Estimated update: July 10 2024. |
127+
| Date | Category | Update |
128+
| ------- | -------------------- | ------------------------------------------------------------ |
129+
| June 27 | GA | [Checkov IaC Scanning in Defender for Cloud](#ga-checkov-iac-scanning-in-defender-for-cloud). |
130+
| June 24 | Update | [Change in pricing for multicloud Defender for Containers](#update-change-in-pricing-for-defender-for-containers-in-multicloud) |
131+
| June 20 | Upcoming deprecation | [Reminder of deprecation for adaptive recommendations at Microsoft Monitoring Agent (MMA) deprecation](#deprecation-reminder-of-deprecation-for-adaptive-recommendations).<br/><br/> Estimated deprecation August 2024. |
132+
| June 10 | Preview | [Copilot for Security in Defender for Cloud](#preview-copilot-for-security-in-defender-for-cloud) |
133+
| June 10 | Upcoming update | [SQL vulnerability assessment automatic enablement using express configuration on unconfigured servers](#update-sql-vulnerability-assessment-automatic-enablement).<br/><br/> Estimated update: July 10, 2024. |
134+
| June 3 | Upcoming update | [Changes in identity recommendations behavior](#update-changes-in-identity-recommendations-behavior)<br/><br/> Estimated update: July 10 2024. |
107135

108136
### GA: Checkov IaC Scanning in Defender for Cloud
109137

0 commit comments

Comments
 (0)