Skip to content

Commit

Permalink
Merge branch 'katiehorne/tec-256-new-docs-sms-for-ado' of https://git…
Browse files Browse the repository at this point in the history
…hub.com/semgrep/semgrep-docs into katiehorne/tec-256-new-docs-sms-for-ado
  • Loading branch information
khorne3 committed Jan 21, 2025
2 parents 53e040a + 2f9f718 commit 20f2c70
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions docs/deployment/managed-scanning/azure.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,19 +20,20 @@ Add Azure DevOps repositories to your Semgrep organization in bulk without addin
## Prerequisites and permissions

- Semgrep Managed Scanning requires repositories hosted by Azure DevOps Services. It currently doesn't support Azure DevOps Server.
- Semgrep recommends setting up and configuring Semgrep Managed Scanning with an Azure DevOps service account instead of 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.
- Semgrep recommends setting up and configuring Semgrep Managed Scanning 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 the account. This token must be granted the **Project and Team: Read & write** scope.
- Once you have Managed Scanning fully configured, you can update the token to one with a more limited scope, specifically **Project and Team: Read**.
- Once you have Managed Scanning fully configured, you can update the token to **Project and Team: Read**, a more limited scope.

## Enable Managed Scanning and scan your first repository
## Enable Managed Scans and scan your first repository

<!-- vale off -->
1. In Semgrep AppSec Platform, click **<i class="fa-solid fa-folder-open"></i> Projects**.
2. Click **Scan new project > Semgrep Managed Scan**.
3. Select **Azure Devops** as your source code manager.
4. On the **Add to Azure DevOps Pipeline** page, provide the following information, then click **Connect** to proceed:
4. On the **Add to Azure DevOps Pipeline** page, provide the following information:
1. Your **Access token**. See [User personal access tokens](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate) for token generation information. Ensure you set the Azure DevOps SCM name to `organization_name/project_name`.
2. The name of your **Azure DevOps Project**.
5. Click **Connect** to proceed.
<!-- vale on -->

You have finished setting up a Semgrep managed scan. Click **Back to Managed Scans** to see your projects.
Expand Down

0 comments on commit 20f2c70

Please sign in to comment.