> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations/azure-pipelines-integration/install-the-snyk-extension-for-your-azure-pipelines.md).

# Install the Snyk extension for your Azure pipelines

How to install the Snyk extension for Azure Pipelines from the Visual Studio Marketplace

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Install the Snyk extension for your Azure pipelines

To start using the Snyk task as part of your pipeline build, from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=Snyk.snyk-security-scan), install the extension into your Azure DevOps instance for your Organization.

### Prerequisites for installing Snyk extension for Azure pipelines

* Create a Snyk account at [https://snyk.io/](https://snyk.io).
* Ensure you are an owner or administrator of this account.

### Steps for installing the Snyk extension for Azure pipelines

1. Log in to your Snyk account.
2. Token:
   1. For **free plans**, navigate to your **General Account Settings** and find, copy, and save your personal API token.
   2. For **paid plans**, navigate to the Organization where you want to integrate; then navigate to **Settings** to create a new service account token. Copy and save the new service account token.
3. Access your Azure DevOps account and navigate to the **Extensions** > **Browse marketplace**.
4. Search for the **Snyk Security Scan** extension and click **Get it free**.
5. Create a new **Service Connection** in your Project using **Project Settings** > **Pipelines** > **Service Connections**.
6. Select the **Snyk Authentication** service connection:
   1. In the Snyk Authentication service connection form, enter the **Snyk API Token or Snyk PAT**.
   2. Click **Save**, ensuring the new service connection appears in your list of service connections.

<figure><img src="https://558411700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEEjSXQQu36y0vmFV8zf%2Fuploads%2Fgit-blob-3b65137b95f6bd6e2e22a711a096c7d9b4b1a24f%2Fap_-_search.jpg?alt=media" alt="Create your first service connection"><figcaption><p>Create your first service connection</p></figcaption></figure>

<figure><img src="https://558411700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEEjSXQQu36y0vmFV8zf%2Fuploads%2Fgit-blob-56cabd77f4727460a9a8bdbefc7320a0f2917d7b%2FAzure-authentication-connection-setup.png?alt=media" alt="New Snyk authentication service connection" width="389"><figcaption><p>New Snyk authentication service connection</p></figcaption></figure>

{% hint style="info" %}
If you are hosted in a region other than `SNYK-US-01`, see the section [Regional API endpoints](/developer-tools/integrations/snyk-ci-cd-integrations/azure-pipelines-integration/regional-api-endpoints.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/developer-tools/integrations/snyk-ci-cd-integrations/azure-pipelines-integration/install-the-snyk-extension-for-your-azure-pipelines.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.