Skip to content

Commit 20fa3cc

Browse files
Merge pull request #281731 from laragoldstein13/docs-editor/container-image-mapping-1721835807
Update container-image-mapping.md
2 parents da0f194 + e7bac00 commit 20fa3cc

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/defender-for-cloud/container-image-mapping.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,9 @@ The following is an example of an advanced query that utilizes container image m
4949
5050
## Map your container image from GitHub workflows to the container registry
5151

52-
1. Add the container image mapping tool to your MSDO workflow:
52+
1. Ensure you have onboarded a [GitHub connector](quickstart-onboard-github.md) to Defender for Cloud.
53+
54+
1. Run the following MSDO workflow:
5355

5456
```yml
5557
name: Build and Map Container Image
@@ -68,7 +70,8 @@ jobs:
6870
- uses: actions/setup-python@v4
6971
with:
7072
python-version: '3.8'
71-
# Set Authentication to Container Registry of Choice
73+
# Set Authentication to Container Registry of Choice.
74+
# The example below is for Azure Container Registry. Amazon Elastic Container Registry and Google Artifact Registry are also supported.
7275
- name: Azure Container Registry Login
7376
uses: Azure/docker-login@v1
7477
with:
@@ -86,8 +89,6 @@ jobs:
8689
- name: Run Microsoft Security DevOps Analysis
8790
uses: microsoft/security-devops-action@latest
8891
id: msdo
89-
with:
90-
include-tools: container-mapping
9192
```
9293
9394
After building a container image in a GitHub workflow and pushing it to a registry, see the mapping by using the [Cloud Security Explorer](how-to-manage-cloud-security-explorer.md):

0 commit comments

Comments
 (0)