---
title: "Azure DevOps Integration | Orangescrum"
description: "Connect Azure DevOps to Orangescrum. Work items sync both ways with your own field and status mapping, and you can create branches from a task."
canonical: https://www.orangescrum.com/integrations/azure-devops
---

# Azure DevOps Integration | Orangescrum

> For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt).

[Home](/) / [Integrations](/integrations) / Azure DevOps

Azure DevOps

# Azure DevOps Integration for _Work Items and Repos_

Link an Azure DevOps project to an Orangescrum project, keep work items in step in both directions, and start branches and pull requests from the task itself.

Available in[Cloud](/pricing "Cloud - included")Self-HostedOpen Source

[Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=azure-devops)[Book a Demo](https://calendly.com/orangescrum)

Available in the Orangescrum Cloud edition

## What does the Azure DevOps integration do?

The Azure DevOps integration links an Azure DevOps project to an Orangescrum project and keeps work items in step in both directions. You decide how Azure DevOps fields, states, and people map onto Orangescrum ones, then changes made on either side are carried across, driven by Azure DevOps service hooks so they arrive as they happen. It also reaches the repositories in that project, so a developer can create a branch or open a pull request from the Orangescrum task rather than switching tools to do it.

The problem

## Why two trackers _never agree_

Engineering and everyone else use different tools

Work items live in Azure DevOps, the plan and the reporting live somewhere else, and reconciling them is somebody's weekly job.

✓ Two way work item sync keeps one version of the truth.

The field names never line up

Your states and priorities do not match theirs, so a naive sync makes the data worse rather than better.

✓ You define the field, state, and user mapping yourself.

Branches are disconnected from the plan

Nobody can tell which branch or pull request belongs to which piece of work.

✓ Start the branch or pull request from the task.

What you get

## Azure DevOps work items, _in your project plan_

Two way work item sync with mapping you control, plus branch and pull request creation from the task.

-   ### Project linking
    
    Connect your Azure DevOps organisation and link each project to the Orangescrum project that corresponds to it.
    
-   ### Two way work item sync
    
    Work items and Orangescrum tasks are kept in step in both directions, with a lock while an update is applied so the two sides do not fight.
    
-   ### Field and status mapping
    
    Decide how Azure DevOps fields and states map onto your Orangescrum fields and statuses, rather than accepting somebody else's assumption.
    
-   ### User mapping
    
    Match Azure DevOps identities to Orangescrum users, so assignment and history land against the right person.
    
-   ### Service hooks
    
    Orangescrum registers Azure DevOps service hooks, so changes arrive as events rather than waiting for the next poll.
    
-   ### Create a branch from a task
    
    Start a branch in the linked Azure Repos repository directly from the work item.
    
-   ### Create a pull request from a task
    
    Open a pull request from the task, and see the pull requests already associated with it.
    
-   ### Sync activity log
    
    Every sync is recorded, so when something looks wrong you can see what was applied and when.
    

How it works

## How to _connect it_

1

Authorise Azure DevOps

Connect with Microsoft Entra ID, or use a personal access token if that suits your organisation better.

2

Link the projects

Choose which Azure DevOps project corresponds to which Orangescrum project.

3

Map fields, states, and people

Set how work item types, states, and users translate between the two systems before you turn the sync on.

4

Work from either side

Service hooks carry changes across as they happen, and developers create branches and pull requests from the task.

Who it's for

## For organisations on _the Microsoft stack_

Enterprise engineering teams

Developers who stay in Azure DevOps while the wider organisation plans and reports elsewhere.

[Learn more →](/solutions/it-project-management-software)

Programme and portfolio owners

People who need Azure DevOps work rolled into a plan alongside work that never goes near it.

[Learn more →](/program-management-software)

Mixed toolchains

Companies running Azure DevOps in one division and GitHub or GitLab in another.

[Learn more →](/integrations)

Availability

## Which edition includes _what_

Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes.

The Azure DevOps integration is part of the Cloud edition.

| Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition |

| Azure DevOps project linking | ✓ | ✗ | ✗ |
| Two way work item sync | ✓ | ✗ | ✗ |
| Field, state, and user mapping | ✓ | ✗ | ✗ |
| Service hook driven updates | ✓ | ✗ | ✗ |
| Create a branch from a task | ✓ | ✗ | ✗ |
| Create a pull request from a task | ✓ | ✗ | ✗ |
| Sync activity log | ✓ | ✗ | ✗ |
| Azure Pipelines build status | ✗ | ✗ | ✗ |

Frequently asked questions

## Azure DevOps integration _FAQ_

### Does Orangescrum integrate with Azure DevOps?

Yes, in the Cloud edition. You link an Azure DevOps project to an Orangescrum project, work items sync in both directions with the field and status mapping you define, and you can create branches and pull requests in Azure Repos from the task.

### Which edition includes it?

The Cloud edition only. The Azure DevOps plugin is not part of the Self-Hosted edition or the free Community Edition, so if you are self-hosting this is not available to you today.

### Does it show Azure Pipelines build status?

No. This integration covers work items and repositories. It does not read pipelines, builds, or releases, so pipeline status will not appear on the task. Build status on a work item is a Self-Hosted feature and it covers Jenkins, GitHub Actions, GitLab CI, and Bitbucket Pipelines rather than Azure Pipelines.

### Can I control how fields and statuses map?

Yes, and you should set this up before turning the sync on. Work item types, states, and users are mapped explicitly, so your Orangescrum statuses do not have to match Azure DevOps naming for the sync to be meaningful.

### How does authentication work?

Through Microsoft Entra ID, previously called Azure AD, with a personal access token supported as an alternative. Tokens are stored per company rather than shared.

### Does the sync work in both directions?

Yes. A change in Azure DevOps updates the linked Orangescrum task and the reverse also applies. A work item is locked while an update is being written, so simultaneous edits do not overwrite each other silently.

### Does it sync users from Active Directory?

No. It matches existing Azure DevOps identities to existing Orangescrum users so that assignment and history are attributed correctly. It does not create Orangescrum accounts from your directory. For directory-based sign in, look at SAML single sign-on.

### Can I see what the sync actually did?

Yes. Sync activity is logged, so you can look back at what was applied to which work item and when, which is usually the first thing you want when a mapping looks wrong.

## Connect Azure DevOps to your projects

The Azure DevOps integration is included in the Orangescrum Cloud edition. Unlimited users on every plan.

[Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=azure-devops_cta)[Book a Demo](https://calendly.com/orangescrum)

## Related capabilities

[All integrationsSee everything Orangescrum connects to](/integrations)[GitHub integrationRepository and issue sync for GitHub](/integrations/github)[Single sign-onSAML sign in with your identity provider](/single-sign-on)[Program managementRoll delivery work into a portfolio view](/program-management-software)