Skip to content

Commit 854c2cf

Browse files
authored
add ADO to SMS quickstart (#1955)
1 parent d8d77e7 commit 854c2cf

File tree

1 file changed

+36
-7
lines changed

1 file changed

+36
-7
lines changed

docs/getting-started/quickstart-sms.md

+36-7
Original file line numberDiff line numberDiff line change
@@ -28,23 +28,52 @@ import TabItem from '@theme/TabItem';
2828
<Tabs
2929
defaultValue="gh"
3030
values={[
31+
{label: 'Azure DevOps', value: 'ado'},
3132
{label: 'GitHub', value: 'gh'},
3233
{label: 'GitLab', value: 'gl'},
3334
]}
3435
>
3536
36-
<TabItem value='gh'>
37+
<TabItem value='ado'>
38+
39+
### Prerequisites
40+
41+
Admin access to your Azure DevOps organization.
3742

3843
### Requirements
3944

40-
To enable and use this feature, you must grant Semgrep **Read access** to your code. Steps are provided in [Add repositories to Semgrep Managed Scans](#add-repositories-to-semgrep-managed-scans).
45+
Read access is granted through an access token you generate on Azure DevOps. You can provide this token by [adding Azure DevOps as a source code manager](/deployment/connect-scm#azure-devops-cloud).
4146

42-
Read access is permitted through a private Semgrep app that you create and register yourself. See [Managed Scans > Security](/deployment/managed-scanning/overview#security) for more information on how Semgrep handles your code.
47+
Semgrep recommends setting up and configuring Semgrep with an Azure DevOps service account, not a personal account. Regardless of whether you use a personal or service account, the account must be assigned the **Owner** or **Project Collection Administrator** role for the organization. During setup and configuration, you must provide a personal access token generated by this account. The scopes you must assign to the token include:
48+
49+
- `Project and Team: Read & write`
50+
- `Code: Read`
51+
- `Pull Request Threads: Read & write`
52+
53+
### Add a repository
54+
55+
<!-- vale off -->
56+
1. Sign in to [Semgrep AppSec Platform](https://semgrep.dev/login)
57+
2. Navigate to **Projects**, and click **Scan new project > Semgrep Managed Scan**.
58+
3. In the **Enable Managed Scans for repos** page, select the repositories you want to add to Semgrep Managed Scans.
59+
4. Click **Enable Managed Scans**. The **Enable Managed Scans** dialog appears. By default, Semgrep runs both full and diff-aware scans.
60+
5. Click **Enable**. You are taken to the **Projects** page as your scans begin.
61+
<!-- vale on -->
62+
63+
</TabItem>
64+
65+
<TabItem value='gh'>
4366

4467
### Prerequisites
4568

4669
Admin access to your GitHub organization.
4770

71+
### Requirements
72+
73+
To enable and use this feature, you must grant Semgrep **Read access** to your code. Steps are provided in [Add repositories to Semgrep Managed Scans](#add-repositories-to-semgrep-managed-scans).
74+
75+
Read access is permitted through a private Semgrep app that you create and register yourself. See [Managed Scans > Security](/deployment/managed-scanning/overview#security) for more information on how Semgrep handles your code.
76+
4877
### Add a repository
4978

5079
<!-- vale off -->
@@ -63,14 +92,14 @@ Admin access to your GitHub organization.
6392
</TabItem>
6493
<TabItem value='gl'>
6594

66-
### Requirements
67-
68-
Read access is granted through an access token that you generate on GitLab. You can provide this token by [adding GitLab as a source code manager](/deployment/connect-scm).
69-
7095
### Prerequisites
7196

7297
Admin access to your GitLab organization.
7398

99+
### Requirements
100+
101+
Read access is granted through an access token that you generate on GitLab. You can provide this token by [adding GitLab as a source code manager](/deployment/connect-scm).
102+
74103
### Add a repository
75104

76105
<!-- vale off -->

0 commit comments

Comments
 (0)