Skip to content

Commit 50c1d03

Browse files
Merge pull request #280270 from laragoldstein13/docs-editor/release-notes-1720463185
Update release-notes.md
2 parents 3b0a8ab + e199f71 commit 50c1d03

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

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

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,19 @@ This article summarizes what's new in Microsoft Defender for Cloud. It includes
2424
<!-- 5. Under the relevant month, add a short paragraph about the new feature. Give the paragraph an H3 (###) heading. Keep the title short and not rambling. -->
2525
<!-- 6. In the Update column, add a bookmark to the H3 paragraph that you created (#<bookmark-name>) .-->
2626

27+
## July 2024
28+
|Date | Category | Update
29+
|--|--|--|
30+
|July 8 | Upcoming update | [Container mapping tool to run by default in GitHub](#container-mapping-tool-to-run-by-default-in-github) |
31+
32+
### Container mapping tool to run by default in GitHub
33+
34+
July 8, 2024
35+
36+
**Estimated date for change: August 12, 2024**
37+
38+
With DevOps security capabilities in Microsoft Defender Cloud Security Posture Management (CSPM), you can map your cloud-native applications from code to cloud to easily kick off developer remediation workflows and reduce the time to remediation of vulnerabilities in your container images. Currently, you must manually configure the container image mapping tool to run in the Microsoft Secuity DevOps action in GitHub. With this change, container mapping will run by default as part of the Microsoft Security DevOps action. [Learn more about the Microsoft Security DevOps action](https://github.com/microsoft/security-devops-action/blob/main/README.md#advanced).
39+
2740
## June 2024
2841

2942
|Date | Category | Update

0 commit comments

Comments
 (0)