> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/settings/zones/zones-for-azure-devops.md).

# Zones for Azure Devops

This guide explains how to classify **Azure DevOps** projects and map them to specific zones within **Sprinto**.

***

### **Prerequisites**

Before you start, ensure that:

* You are signed in to the **Sprinto Admin Portal**.
* Your **Azure DevOps** account is connected to Sprinto.
* At least one zone is created in **Settings > Zones**.

***

### **Step 1: Connect Azure DevOps**

To integrate Azure DevOps with Sprinto:

1. Open the **Settings** menu from the left navigation pane.
2. Select **Integrations**.
3. Find and click **Azure DevOps** from the list.
4. Click **Connect** and follow the prompts to authorise Sprinto to access your Azure DevOps account.
5. Once connected, Sprinto automatically retrieves all linked **Azure DevOps organisations (orgs)**.

***

### **Step 2: Access Zone Configuration**

To configure zones for Azure DevOps projects:

1. Go to **Settings > Zones**.
2. Select the zone you want to configure (excluding the **Default Zone**).
3. Under **Change Management**, select **Configure** next to **Azure DevOps**.

***

### **Step 3: Map Organisations and Projects to Zones**

To assign Azure DevOps projects to a zone:

1. In the configuration drawer, you will see a list of **Azure DevOps organisations**.
2. Choose one of the following options:
   * **Assign the entire organisation**: Tick the checkbox next to the organisation name to include all its projects.
   * **Assign specific projects**: Click **Manage** next to the organisation name. Select only the projects you wish to map to the zone.

{% hint style="info" %}
Projects not explicitly mapped to a zone will remain under the **Default Zone**.
{% endhint %}

3. Click **Save** to finalise your selection.

***

### **Step 4: Manage Zone-Based Repositories**

To view repositories classified by zones:

1. Navigate to **Change Management > Azure DevOps**.
2. Use the **Zone filter** at the top of the table to view repositories mapped to specific zones.
3. Repeat these steps for each zone as needed.

***

### **Step 5: Verify Zone Filters on Dashboards**

To check your zone configuration:

1. Go to **Change Management** and open the **Health** dashboard.
2. Apply the **Zone filter** to examine tasks and evidence collection linked to each zone.


---

# 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.sprinto.com/settings/zones/zones-for-azure-devops.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.