Azure DevOps

Everything You Need To Know About Unito's Azure DevOps Integration

Connecting Azure DevOps with Unito? Here's what you can expect from this integration.

In this article:

What Unito syncs from Azure DevOps

Unito syncs all native and custom work item types in Azure DevOps projects by linking individual fields from these work items to items in other tools (e.g., Asana tasks, Jira issues, ServiceNow records).

ADO Sync Items

This article applies to Unito users with an enterprise plan for a Unito workspace created after July 23rd, 2025. If you don't meet these criteria, you'll want to consult this guide, instead.

Supported fields for Azure DevOps work items

Unito supports all native and custom work items fields available in your Azure DevOps project.

Additional features

Unito's Azure DevOps integration also supports the following features:

  • External link types: You can sync these with Unito as reference fields.
  • Rich text fields: All rich text type fields are supported.
  • Item types: When building a Unito flow with Azure DevOps, you can choose between two subitem configurations.
    • Work Item (Flat): This doesn't maintain the hierarchy between tools. Every work item is synced as a top-level item. All work items can be synced, regardless of their type or level.
    • Work Item (Hierarchy): This maintains the hierarchy between tools. Rules only apply to top-level work items, and child work items will only be synced if the parent work item can be synced.
  • Attachments: Unito can copy attachments to and from Azure DevOps work items, meaning the whole file will be available in any synced work item as long as it's mapped to an attachment field in your other tool. You can also stream attachments to the description footer of the other tool, adding a clickable link for anyone in the other tool to view it without logging in to ADO. 

Unsupported features for Azure DevOps

Need something this integration doesn't support yet? We can help you work around many of these limitations. Meet with us to find out how.

  • OAuth 2.0: This authentication method will be deprecated entirely in Azure DevOps in 2026. It is still supported in Unito, but we recommend that you use OAuth 2.0 with Entra ID to connect your Azure DevOps account to Unito. This is only supported for accounts linked with an organization. Personal accounts aren't supported.
  • Rich text in comments: Rich text in comments isn't supported by default, but you can activate this by adding this code snippet in your flow's manual options
    { "richTextComments": true }
  • Creating new projects from Unito: This isn't currently supported.
  • Multi-line text custom fields: Multi-line text in custom fields is only available with certain plans on request in plain text format. This is to prevent any formatting from being erased from the source item when syncing two waysContact our team for details.
  • Custom priority values: Not currently supported.
  • Projects and boards: Unito syncs work items from entire Azure DevOps projects, not individual boards. To sync specific items from specific boards, create a custom single-select field on those boards and use it as a filter in your Unito rules.
  • Comment editing: When you edit comments in Azure DevOps, these edits won't be synced over to other projects or other tools. That's because Unito only syncs new comments, not any edits to existing comments.