# Azure Devops

## Integration Setup

To configure the Azure integration, follow these steps (either during the onboarding wizard, or once you have access to the Gomboc platform):

1. In Azure, create a [Personal Access Token](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate) that has a **Code (Read & Write)** permissions and the name of the organization is was scoped to.
   1. *Note that we do not currently support the option "All accessible organizations". If you need to provide access to multiple organizations, please create a separate integration for each one.*
2. Go to Settings > Integrations > Azure

<div align="left" data-full-width="false"><figure><img src="/files/frJFpeWUlty0UlCG6lSx" alt="" width="375"><figcaption></figcaption></figure></div>

2. Insert the token and org name you have created in step 1

<div align="left"><figure><img src="/files/lMK7nUh8WIYLWjDG4WSd" alt="" width="375"><figcaption></figcaption></figure></div>

3\. Click "Integrate" to complete the initial SCM integration

## Webhooks

In order for Gomboc.AI to keep the updated status of any PR's we create for you, you must include a webhook. In order to create a proper webhook, please follow these steps:

1. Go to our portal ([app.gomboc.ai](https://app.gomboc.ai)), click on your account icon on the top right > Settings

<div align="left"><figure><img src="/files/7ZY9UZR7dwlwkeXwkqhX" alt="" width="90"><figcaption></figcaption></figure></div>

2. Create a 'Personal' or 'API' token.
   1. Use a **Personal token** when you will be the only one using the token,
   2. Use an **API token** with the appropriate roles if the token will be used within the webhook, or expect multiple people to use the token.

<figure><img src="/files/jOh1krC6zVZXTI6kXdUB" alt=""><figcaption></figcaption></figure>

3. Be sure to copy the created token, and start to set up the Azure Devops webhook. Within your project settings, create a 'Web Hooks' service.

<figure><img src="/files/WR5ElJzEmLL4fBUqoWdD" alt=""><figcaption></figcaption></figure>

4. The trigger should be specified 'Pull Request Updated'. No additional filters will be required.

<div align="left"><figure><img src="/files/795yksxjsZ18yHZmRnyd" alt="" width="563"><figcaption></figcaption></figure></div>

5. Within the 'Actions' settings, you will need the following values
   1. URL: <https://scan.app.gomboc.ai/webhook/azdo>
   2. HTTP headers: X-Gomboc-Authorization: \<Token copied from the Gomboc settings>

<div align="left"><figure><img src="/files/ZhP5m5KnTvnhOywWFT0s" alt="" width="382"><figcaption></figcaption></figure></div>

6. Once completed, you can press finish and proceed to creating the pipeline or start to create pull requests through the portal.

## CI/CD

See [Azure Devops Pipelines](/integrations/continuous-integration-ci-build-systems/azure-devops-pipelines.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gomboc.ai/integrations/source-code-management-scm/azure-devops.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.