An Overview of Unito's Azure DevOps Integration

Ready to start syncing work items with Unito's Azure DevOps integration? Here's what you need to know.

What does this article cover?

Unito can sync Microsoft Azure DevOps (ADO) work items from your projects directly with work items in other tools. By creating a Unito flow, you'll be able to keep your work items in sync bidirectionally with automated updates based on rules set by you.

First, you'll need to go into your ADO account and enable third-party application access via OAuth. Otherwise, you won't be able to see your projects in Unito.

Supported fields in Azure DevOps

The table below lists out all the fields you can sync with our Azure DevOps integration, as well as which fields can be used in rules.

Azure DevOps field One-way  Two-way Rules
Acceptance criteria    
Boolean (custom field)*  
Comment  ✔  
Created at    
Datetime (custom field)*  ✔  
Description   ✔  
Due date  ✔  
Effort  ✔  
Identity (custom field)*  ✔  
Integer (custom field)*  ✔  
Link to issue    
Multi-line text (custom field)**  
Picklist (custom field)*  ✔  
Remaining work  ✔  
State  ✔
Story points  ✔  
Tag  ✔
Target date  ✔  
Text (custom field)*  ✔  
Title  ✔  
Unique identifier    
Updated at    
Work item type  

*Custom fields are only available with certain plans. Visit Unito's pricing page for more information.

**Multi-line text available with certain plans on request. Contact our team for details.

Quick definitions:

    • One-Way: Changes to the field in Azure DevOps will appear in the other synced field but not vice versa.
    • Two-Way: Changes to either synced field will appear in the other.
    • Rules: This work item field can be used as a trigger in your rules to filter work items from syncing with Unito.

What counts as an item in sync?

In Microsoft Azure DevOps, Unito counts every synced work item as an item in sync.

Custom fields

The custom fields supported by our ADO integration are User, Number, Dropdowns, Text (Single line), Boolean, Date Time, and Swimlane

Enable third-party application access via OAuth before syncing

Note: Unito can't access projects in Azure DevOps unless Third-Party Application access via OAuth is toggled. 

To enable it, select Organization Settings, then scroll down to click Policies. From there you should see the off/on switch like this: 

Azure DevOps Organization Settings

If you have multiple DevOps organizations, make sure this setting is turned on across all of them.

Limitations and other things to keep in mind

  • Default work item type: When a new work item is created in Azure DevOps by Unito, it will always be one type of work item, whether that's an Issue, an Epic, a Feature, or a Bug. 

You can set the default item type using a rule or change the item type manually in Azure DevOps after it's created.

  • You can set the default item type using a rule or change the item type manually in Azure DevOps after it's created.

  • Signing up via Azure DevOps: You'll have to use a different tool account — or an email address — to sign up for Unito.

  • Syncing attachments: You won't be able to sync your Azure DevOps attachments to other tools just yet.

Read more about the limitations of Unito's Azure DevOps integration.

If you have any questions or feature requests, please reach out to us with the chat bubble! We'll be happy to help.


Watch a demo of Unito's Azure DevOps integration in action

Follow our step by step guide to connect Azure DevOps to Wrike or watch this demo with Zendesk below:

Got feedback? Submit a Unito feature request to let us know what you'd like to see in the next update to our Azure DevOps integration.