You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/getting-started/quickstart-sms.md
+36-7
Original file line number
Diff line number
Diff line change
@@ -28,23 +28,52 @@ import TabItem from '@theme/TabItem';
28
28
<Tabs
29
29
defaultValue="gh"
30
30
values={[
31
+
{label: 'Azure DevOps', value: 'ado'},
31
32
{label: 'GitHub', value: 'gh'},
32
33
{label: 'GitLab', value: 'gl'},
33
34
]}
34
35
>
35
36
36
-
<TabItemvalue='gh'>
37
+
<TabItemvalue='ado'>
38
+
39
+
### Prerequisites
40
+
41
+
Admin access to your Azure DevOps organization.
37
42
38
43
### Requirements
39
44
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).
41
46
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
+
<TabItemvalue='gh'>
43
66
44
67
### Prerequisites
45
68
46
69
Admin access to your GitHub organization.
47
70
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
+
48
77
### Add a repository
49
78
50
79
<!-- vale off -->
@@ -63,14 +92,14 @@ Admin access to your GitHub organization.
63
92
</TabItem>
64
93
<TabItemvalue='gl'>
65
94
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
-
70
95
### Prerequisites
71
96
72
97
Admin access to your GitLab organization.
73
98
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).
0 commit comments