> For the complete documentation index, see [llms.txt](https://docs.oobeya.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oobeya.io/integrations/all-integrations/scm-addons/azure-devops-integration.md).

# Azure DevOps Integration

{% hint style="info" %}
Oobeya **Azure DevOps addon** is compatible with both Azure DevOps Services (cloud) and Azure DevOps Server (TFS2017, TFS2018, TFS2019).
{% endhint %}

## **1. Create Azure DevOps Personal Access Token**

1\. Navigate to **User Settings** and click **"Personal Access Tokens"**.&#x20;

![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGIlBSTjQtZxUoFwUx4%2Fuploads%2FhmDVE5PtAmUpx0mUOg2i%2Ffile.png?alt=media)

2\. Click the ***"New Token"*** button and select ***read*** permissions for the connection.&#x20;

The required permissions are:

* Build – *Read*
* Code – *Read*&#x20;
* Project and Team – *Read*&#x20;
* Pull Request Threads – *Read*
* Release – *Read*
* Test Management – *Read*&#x20;
* Work Items – *Read*&#x20;

![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGIlBSTjQtZxUoFwUx4%2Fuploads%2FnK8bOYmMxQfrGHpgDJbL%2Ffile.png?alt=media)

3\. Copy and save the *access token* to use it on the Oobeya data source connection.

## **2. Install Azure DevOps Addon on Oobeya** :jigsaw:&#x20;

1. Log in to [Oobeya](https://oobeya.io/) with an *Administrator* account.
2. Navigate to **Integrations** and select the **Azure DevOps** addon and then click the **"Install"** button.&#x20;

![](/files/YRw5y235Eu1XxTBzZQIY)

## **3. Add A New Data Source** :electric\_plug:&#x20;

1.Navigate to **Data Sources**, select Azure DevOps to add a new data source.&#x20;

![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGIlBSTjQtZxUoFwUx4%2Fuploads%2FXV9PrLMKFQrLNfJNFUwl%2Ffile.png?alt=media)

2\. Click the **"New Data Source"** button and fill in the form using the Personal *Access Token* which was created on Azure DevOps settings in the first step.&#x20;

**Data Source Name:** A custom name for your data source (e.g., "Oobeya Azure Data Source").&#x20;

**Server URL:** Your Azure DevOps organization’s URL (e.g., <https://dev.azure.com/{your-organization})&#x20>;

**Token:** The Personal Access Token you retrieved earlier.

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

3\. Click the **"Test Connection"** button to verify the connection.

## **Ready to Connect** :rocket:&#x20;

Now Oobeya is connected with your own Azure DevOps to get the real-time statistics of your code repositories to track each development activity.

## **Next Steps** :dart:&#x20;

* [Add a new Widget](/dashboards/adding-a-new-widget.md)
* [Create a new Gitwiser Analysis](/gitwiser-repo-analytics/settings-for-git-analytics/initialize-development-analytics.md)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.oobeya.io/integrations/all-integrations/scm-addons/azure-devops-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
