Skip to content

Commit 6f25b3a

Browse files
authored
Merge pull request #228293 from ElazarK/WI64589-cli-tool
fixed up devops faq
2 parents 159add0 + 71f68d4 commit 6f25b3a

File tree

3 files changed

+25
-20
lines changed

3 files changed

+25
-20
lines changed

articles/defender-for-cloud/devops-faq.md

Lines changed: 25 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Defender for DevOps FAQ
33
description: If you're having issues with Defender for DevOps perhaps, you can solve it with these frequently asked questions.
44
ms.topic: reference
5-
ms.date: 01/26/2023
5+
ms.date: 02/23/2023
66
---
77

88
# Defender for DevOps frequently asked questions (FAQ)
@@ -22,22 +22,21 @@ If you're having issues with Defender for DevOps these frequently asked question
2222
- [Is Exemptions capability available and tracked for app sec vulnerability management](#is-exemptions-capability-available-and-tracked-for-app-sec-vulnerability-management)
2323
- [Is continuous, automatic scanning available?](#is-continuous-automatic-scanning-available)
2424
- [Is it possible to block the developers committing code with exposed secrets](#is-it-possible-to-block-the-developers-committing-code-with-exposed-secrets)
25-
- [I am not able to configure Pull Request Annotations](#i-am-not-able-to-configure-pull-request-annotations)
26-
- [What are the programing languages that are supported by Defender for DevOps?](#what-are-the-programing-languages-that-are-supported-by-defender-for-devops)
27-
- [I'm getting the There's no CLI tool error in Azure DevOps](#im-getting-the-theres-no-cli-tool-error-in-azure-devops)
28-
25+
- [I'm not able to configure Pull Request Annotations](#im-not-able-to-configure-pull-request-annotations)
26+
- [What programming languages are supported by Defender for DevOps?](#what-programming-languages-are-supported-by-defender-for-devops)
27+
- [I'm getting an error that informs me that there's no CLI tool](#im-getting-an-error-that-informs-me-that-theres-no-cli-tool)
2928

3029
### I'm getting an error while trying to connect
3130

32-
When selecting the *Authorize* button, the presently signed-in account is used, which could be the same email but different tenant. Make sure you have the right account/tenant combination selected in the popup consent screen and Visual Studio.
31+
When you select the *Authorize* button, the account that you're logged in with is used. That account can have the same email but may have a different tenant. Make sure you have the right account/tenant combination selected in the popup consent screen and Visual Studio.
3332

34-
The presently signed-in account can be checked [here](https://app.vssps.visualstudio.com/profile/view).
33+
You can [check which account is signed in](https://app.vssps.visualstudio.com/profile/view).
3534

3635
### Why can't I find my repository
3736

38-
Only TfsGit is supported on Azure DevOps service.
37+
The Azure DevOps service only supports `TfsGit`.
3938

40-
Ensure that you've [onboarded your repositories](/azure/defender-for-cloud/quickstart-onboard-devops?branch=main) to Microsoft Defender for Cloud. If you still can't see your repository, ensure that you're signed in with the correct Azure DevOps organization user account. Your Azure subscription and Azure DevOps Organization need to be in the same tenant. If the user for the connector is wrong, you need to delete the connector that was created, sign in with the correct user account and re-create the connector.
39+
Ensure that you've [onboarded your repositories](/azure/defender-for-cloud/quickstart-onboard-devops?branch=main) to Microsoft Defender for Cloud. If you still can't see your repository, ensure that you're signed in with the correct Azure DevOps organization user account. Your Azure subscription and Azure DevOps Organization need to be in the same tenant. If the user for the connector is wrong, you need to delete the previously created connector, sign in with the correct user account and re-create the connector.
4140

4241
### Secret scan didn't run on my code
4342

@@ -47,7 +46,7 @@ In addition to onboarding resources, you must have the [Microsoft Security DevOp
4746

4847
If no secrets are identified through scans, the total exposed secret for the resource shows `Healthy` in Defender for Cloud.
4948

50-
If secret scan isn't enabled (meaning MSDO isn't configured for your pipeline) or a scan isn't performed for at least 14 days, the resource will show as `N/A` in Defender for Cloud.
49+
If secret scan isn't enabled (meaning MSDO isn't configured for your pipeline) or a scan isn't performed for at least 14 days, the resource shows as `N/A` in Defender for Cloud.
5150

5251
### I don’t see generated SARIF file in the path I chose to drop it
5352

@@ -63,7 +62,7 @@ Azure DevOps repositories only have the total exposed secrets available and will
6362

6463
For a previously unhealthy scan result to be healthy again, updated healthy scan results need to be from the same build definition as the one that generated the findings in the first place. A common scenario where this issue occurs is when testing with different pipelines. For results to refresh appropriately, scan results need to be for the same pipeline(s) and branch(es).
6564

66-
If no scanning is performed for 14 days, the scan results would be revert to N/A.
65+
If no scan is performed for 14 days, the scan results revert to `N/A`.
6766

6867
### I don’t see Recommendations for findings
6968

@@ -87,34 +86,40 @@ Learn more about [Microsoft Privacy Statement](https://go.microsoft.com/fwLink/?
8786

8887
### Is Exemptions capability available and tracked for app sec vulnerability management?
8988

90-
Exemptions are not available for Defender for DevOps within Microsoft Defender for Cloud.
89+
Exemptions aren't available for Defender for DevOps within Microsoft Defender for Cloud.
9190

9291
### Is continuous, automatic scanning available?
9392

9493
Currently scanning occurs at build time.
9594

9695
### Is it possible to block the developers committing code with exposed secrets?
9796

98-
The ability to block developers from committing code with exposed secrets is not currently available.
97+
The ability to block developers from committing code with exposed secrets isn't currently available.
9998

100-
### I am not able to configure Pull Request Annotations
99+
### I'm not able to configure Pull Request Annotations
101100

102101
Make sure you have write (owner/contributor) access to the subscription.
103102

104-
### What are the programing languages that are supported by Defender for DevOps?
103+
### What programming languages are supported by Defender for DevOps?
105104

106105
The following languages are supported by Defender for DevOps:
107106

108107
- Python
109-
- Java Script
110-
- Type Script
108+
- JavaScript
109+
- TypeScript
111110

112-
### I'm getting the There's no CLI tool error in Azure DevOps
111+
### I'm getting an error that informs me that there's no CLI tool
113112

114-
If when running the pipeline in Azure DevOps, you receive the following error:
113+
When you run the pipeline in Azure DevOps, you receive the following error:
115114
"no such file or directory, scandir 'D:\a\_msdo\versions\microsoft.security.devops.cli'".
116115

117-
This error occurs if you are missing the dependency of `dotnet6` in the pipeline's YAML file. DotNet6 is required to allow the Microsoft Security DevOps extension to run. Include this as a task in your YAML file to eliminate the error.
116+
:::image type="content" source="media/devops-faq/error-in-run.png" alt-text="Screenshot that shows an error that states there's no CLI tool." lightbox="media/devops-faq/error-in-run.png":::
117+
118+
This error can be seen in the extensions job as well.
119+
120+
:::image type="content" source="media/devops-faq/error-in-job.png" alt-text="Screenshot that shows the job's extension where the error is visible." lightbox="media/devops-faq/error-in-job.png":::
121+
122+
This error occurs if you're missing the dependency of `dotnet6` in the pipeline's YAML file. DotNet6 is required to allow the Microsoft Security DevOps extension to run. Include this as a task in your YAML file to eliminate the error.
118123

119124
You can learn more about [Microsoft Security DevOps](https://marketplace.visualstudio.com/items?itemName=ms-securitydevops.microsoft-security-devops-azdevops).
120125

790 KB
Loading
205 KB
Loading

0 commit comments

Comments
 (0)