Skip to content

Commit 525e489

Browse files
Update upcoming-changes.md
update per Tomer
1 parent bd2b494 commit 525e489

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ If you're looking for the latest release notes, you can find them in the [What's
2323
| [Release of containers Vulnerability Assessment powered by Microsoft Defender Vulnerability Management (MDVM) in Defender CSPM](#release-of-containers-vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management-mdvm-in-defender-cspm) | May 2023 |
2424
|[Renaming container recommendations powered by Qualys](#renaming-container-recommendations-powered-by-qualys) | May 2023 |
2525
| [DevOps Resource Deduplication for Defender for DevOps](#devops-resource-deduplication-for-defender-for-devops) | June 2023 |
26-
| [Deprecation of agent-based Container offering in Defender CSPM](#deprecation-of-agent-based-container-offering-in-defender-cspm) | June 2023
26+
| [Replacing agent-based discovery with agentless discovery for containers capabilities in Defender CSPM](#replacing-agent-based-discovery-with-agentless-discovery-for-containers-capabilities-in-defender-cspm) | June 2023
2727

2828
### Deprecation of legacy compliance standards across cloud environments
2929

@@ -115,11 +115,11 @@ If you don't have an instance of a DevOps organization onboarded more than once
115115

116116
Customers will have until June 30, 2023 to resolve this issue. After this date, only the most recent DevOps Connector created where an instance of the DevOps organization exists will remain onboarded to Defender for DevOps. For example, if Organization Contoso exists in both connectorA and connectorB, and connectorB was created after connectorA, then connectorA will be removed from Defender for DevOps.
117117

118-
### Deprecation of agent-based Container offering in Defender CSPM
118+
### Replacing agent-based discovery with agentless discovery for containers capabilities in Defender CSPM
119119

120120
**Estimated date for change: June 2023**
121121

122-
As part of the move to the offering of agentless technology for containers in Defender CSPM , the agent-based offering is set to be deprecated and will stop supporting legacy agent-based instances in June 2023. The agentless container offering will no longer be dependent on the Defender for Containers plan. Affected users should [enable the relevant extensions](concept-agentless-containers.md#onboard-agentless-containers-for-cspm) as soon as possible in order to continue receiving container-related value with the new agentless capability.
122+
With Agentless Container Posture capabilities available in Defender CSPMthe agent-based discovery capabilities are set to be retired in June 2023. If you currently use container capabilities within Defender CSPM, please make sure to [enable the relevant extensions](concept-agentless-containers.md#onboard-agentless-containers-for-cspm) before this date to continue receiving container-related value with the new agentless capabilities such as container-related: attack paths, insights and inventory.
123123

124124
## Next steps
125125

0 commit comments

Comments
 (0)