> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-products/scan-management/managed-scans/manage-scans-faq.md).

# Manage Scans FAQ

## Azure DevOps Scans

To initiate a managed scan in Azure DevOps, it is essential to have an agent pool configured beforehand.

Please refer to the official Azure documentation to continue: [**Create and manage agent pools**](https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops\&tabs=yaml%2Cbrowser)

## Bitbucket Scans

### Enable pipelines in Bitbucket before running a scan

Before running a Xygeni Scan that automatically configures a pipeline in Bitbucket, you must ensure that pipelines are enabled for your repository. You can enable pipelines through the Bitbucket Pipeline settings page:

1. Navigate to your repository in Bitbucket
2. Go to Repository settings
3. Click on "Pipelines" in the settings menu
4. Enable the pipelines feature if it's not already enabled

If pipelines are not enabled, the automatic pipeline configuration will fail, and you won't be able to run scans using this method.


---

# 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.xygeni.io/xygeni-products/scan-management/managed-scans/manage-scans-faq.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.