---
title: Azure DevOps
slug: docs/azure-devops
docTags: 
createdAt: 2026-09-21T07:54:41.125Z
---

Connect an Azure DevOps organization to Archbee with a personal access token, then sync its repositories to doc spaces. You need permission to create tokens in the Azure DevOps organization and permission to edit team integrations in Archbee.

1. Open the token page for your organization at [\_usersSettings/tokens](https://dev.azure.com/ionutmaracineanu/_usersSettings/tokens), and select **New Token**.
2. Grant the token full access or include at least:
   - Code (read & write)
   - Project (read)
   - Service hooks (read & write)
3. Copy the token. Azure DevOps shows it once, and you cannot read it again after you close the dialog.

![](https://api.archbee.com/api/optimize/bNBm7nPJgXjbjLyfbHNh2/DohQmdNRYZyDF08Vyi-Pv_image.png)

1. In Archbee, open [Settings → Integrations](https://app.archbee.com/settings/team-integrations) and select **Azure DevOps**.
2. In **Organization**, enter the organization name. This is the `{organization}` part of `https://dev.azure.com/{organization}`.
3. In **Personal access token**, paste the token you copied.
4. Select **Connect**. Archbee reads the organization's repositories and lists them grouped by project.

![](https://api.archbee.com/api/optimize/bNBm7nPJgXjbjLyfbHNh2/QZxkzhs8JXTrSOiDMUX0k_image.png)

If the list is empty, check that the token has the Code (read) scope and that the organization has Git repositories. To replace an expired token, return to the same screen and use the **Update the personal access token** form.

:::hint{type="info"}
This integration works similarly to the GitHub integration. For more information about the two-way sync functionality and repository configuration, see [Set up the repository](docId\:fsqc31Wq96DYg7y-vml_H) 
:::