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

# Azure DevOps Integration

Bring your Azure DevOps work items onto a board, edit them in Spreo, and turn sticky notes into new work items.

{% hint style="info" %}
The Azure DevOps integration is included in every plan, including the free trial, except Starter.
{% endhint %}

The Azure DevOps integration brings your work items onto a board as live cards, for sprint planning, backlog refinement, or talking through work in a retro. Changes you make to a card on the board are saved back to Azure DevOps, and you can turn sticky notes into new work items.

{% embed url="<https://spreo.io/blog/video/azure-devops.mp4>" %}

### Connect your Azure DevOps account

Each person connects their own Azure DevOps account. No admin setup is needed in Spreo.

* The first time you import work items or edit an Azure DevOps card, Spreo asks you to sign in to Azure DevOps.
* You can also connect ahead of time from Integrations in [Your Settings](https://docs.spreo.io/getting-started/your-settings.md#integrations).

You sign in with the Microsoft work or school account you use for Azure DevOps. Spreo gets the same access your account already has, so it can load your work items and save your edits, but it can't see any project or work item that you can't. If your company only lets admins approve new apps in Microsoft Entra ID, Microsoft asks for an admin's approval the first time someone connects.

This connection is separate from how you sign in to Spreo. For signing in to Spreo with Microsoft, see [Signing In](https://docs.spreo.io/getting-started/signing-in.md) and [Single Sign-On](https://docs.spreo.io/management/single-sign-on.md).

{% hint style="info" %}
Each Spreo organization connects to one Azure DevOps organization. The first person to connect sets it, and everyone else in the Spreo organization must connect to that same Azure DevOps organization. If your Microsoft account can access more than one, Spreo asks you to pick. If you pick a different one from the rest of your team, the connection fails and tells you which organization to use. Contact support if your organization needs to switch.
{% endhint %}

### Import Azure DevOps work items

1. Open **Insert** in the toolbar and choose **Azure DevOps Work Items**.
2. Find your work items. Pick a project, or leave it on **All Projects**, and switch to **Assigned to me** to see only your own. You can also search by title, or type a work item ID such as 1234.
3. Select the work items you want and click **Import**. If you don't select any, Import brings in every work item in the list.

<figure><img src="https://2875185778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwEhLPSRTDuhd61395hZu%2Fuploads%2FqHEHRahnunxnLiz98pyu%2Fazure-devops-insert-menu.webp?alt=media" alt="The Insert menu, with Azure DevOps Work Items below Jira Issues and Linear Issues"><figcaption></figcaption></figure>

<figure><img src="https://2875185778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwEhLPSRTDuhd61395hZu%2Fuploads%2FlvnrsRyqxyuM12Nrpeso%2Fazure-devops-import-window.webp?alt=media" alt="The Import From Azure DevOps window, with eight work items selected and the Import button showing Import (8)"><figcaption></figcaption></figure>

The list shows up to 200 matching work items, most recently changed first. If you can't see the one you want, narrow your search.

The work items are added to your board as Azure DevOps cards. Each card shows the work item's title, type, ID, state and assignee. It also shows the priority, iteration and Story Points or Effort when the work item type has those fields.

### Edit an Azure DevOps card

Double-click the title, type, state or assignee on a card to change it. You can also double-click the priority, iteration, area or a number field such as Story Points, when the card shows it.

For more, click the button in the top right of the card. This opens the work item in a side panel, where you can:

* edit the title and description
* read the work item's comments and add your own
* change the state, priority, assignee, iteration, area and estimate (Story Points, Effort or Size, depending on your process)
* open the work item in Azure DevOps by clicking its type and ID at the top, or open its project by clicking the project name
* copy a link to the work item

<figure><img src="https://2875185778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwEhLPSRTDuhd61395hZu%2Fuploads%2FdE9W8GIxNsyLMjHvmAl1%2Fazure-devops-side-panel.webp?alt=media" alt="An Azure DevOps work item open in the side panel next to its card, showing its description, comments, state, priority, assignee, iteration, area and effort"><figcaption></figcaption></figure>

Opening the side panel also loads the latest version of the work item from Azure DevOps. Descriptions are edited as HTML, which is how Azure DevOps stores them.

### Bulk change Azure DevOps cards

Select several Azure DevOps cards and choose **Bulk Change** from the bar above them. You can assign the work items, or change their priority, type, iteration, area, estimate or state, all at once.

* Type, iteration and area can only be changed together for cards from the same project.
* State can only be changed together for cards of the same work item type in the same project.
* Priority and estimate are only changed on the cards whose work item type has those fields.

### Show more fields on Azure DevOps cards

Select an Azure DevOps card and click **Configure Fields** in the bar above it. Turn fields on or off to show or hide them on every Azure DevOps card on this board. Priority, iteration, Story Points and Effort are shown by default.

The list includes the text, number, date, yes/no, person and path fields of the work items on your board.

### Create work items from sticky notes

1. Select the sticky notes, index cards or task cards you want to turn into work items. You can convert up to 20 at a time.
2. Click **Convert to Azure DevOps Work Items** in the bar above them. This button appears once you've connected your Azure DevOps account.
3. Pick the Azure DevOps project to create the work items in.
4. Choose the work item type, such as User Story, Product Backlog Item, Bug or Task. Work items you create together are all the same type.
5. Check the details. Each note's text becomes a work item title. Index cards and task cards also fill in the description from the card's body.
   * When you're converting several notes, the **Defaults** page sets the assignee, state, iteration, area and priority for all of them. Each note also has its own page, where you can edit its title and description or change those values.
   * If you leave them unset, the state is the work item type's default, and the iteration and area are the project's defaults.
6. Click **Create Work Items**.

Your notes are replaced by Azure DevOps cards in the same place, and any lines connected to them stay connected. If Azure DevOps can't create a work item, Spreo shows the reason and leaves that note on the board.

### Other card options

* **Color**, in the bar above a selected card, colours the card. This only changes the card in Spreo, not the work item in Azure DevOps.
* You can drag Azure DevOps cards into topics and zones, just like sticky notes.

### Delete an Azure DevOps card

Select the card and press Delete. This removes the card from your board. It **does not** delete the work item in Azure DevOps.

### How syncing works

Changes you make to an Azure DevOps card in Spreo are saved to Azure DevOps straight away, and everyone on the board sees them. If Azure DevOps rejects a change, Spreo shows the reason and the card goes back to the value in Azure DevOps. For example, changing a work item's type fails if the new type doesn't have the work item's current state.

Changes made in Azure DevOps show up in Spreo when the board is opened or reloaded, or when you open a card's side panel.

### What you can't do yet

* You can't import from a saved query or with WIQL. Use the project, search and **Assigned to me** filters instead.
* Iteration menus list the iterations of the project's default team.
* The [Spreo MCP server](https://docs.spreo.io/boards/mcp.md) can't search Azure DevOps or create work items. It can place an Azure DevOps card on a board when your assistant gives it the work item ID.

### Who can see and edit Azure DevOps data

* Anyone who can open the board can see the Azure DevOps cards on it, including guests and visitors.
* However, at least one person on the board needs to be connected to Azure DevOps for the work item details to load. Otherwise only the card outlines and work item IDs will be shown.
* Only people who have connected their own Azure DevOps account can edit the work items, and only the work items their Azure DevOps account can access.
* The board only stores which work items are on it. Work item details are loaded from Azure DevOps when the board is opened, and held in memory while the board is in use. Spreo also caches field names, and each project's work item types, states, iterations and areas, for up to an hour so menus open quickly.

To disconnect, go to Integrations in Your Settings and click **Disconnect**. This removes Spreo's access to your Azure DevOps account.

### Azure DevOps Server

The integration works with Azure DevOps Services, the cloud version at dev.azure.com. Get in touch with us if you use Azure DevOps Server on your own servers and want to use it with Spreo.

### Azure DevOps integration feedback

The Azure DevOps integration is new, so tell us what's missing for your team. Talk to us using the support chat in your boards, or email us at <contact@spreo.io>.


---

# 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.spreo.io/boards/azure-devops-integration.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.
