> 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/how-the-snyk-security-scan-task-works.md).

# How the Snyk Security Scan task works

How the Snyk Security Scan task runs on each Azure Pipelines build

After the Snyk Security Scan task is added to a pipeline, each time the pipeline runs, the Snyk task performs the following actions:

## **Test**

1. Snyk tests application dependencies or container images for vulnerabilities and open-source license issues or application source code for security vulnerabilities and lists these vulnerabilities and issues.
2. If Snyk finds vulnerabilities or license issues, it does one of the following (based on your configuration):
   * Fails the pipeline
   * Allows the pipeline to continue

## **Monitor**

After the snyk test is complete on the dependencies for an application or a container image, you can run `snyk monitor`. `snyk monitor` saves a snapshot of the Project dependencies in your [snyk.io](https://snyk.io) account, where you can see the dependency tree with all of the issues and be alerted if and when new issues are found in the dependencies.


---

# 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/how-the-snyk-security-scan-task-works.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.