ServiceNow-Azure DevOps Connector: The Options Compared Side by Side
A ServiceNow-Azure DevOps connector turns ServiceNow records into Azure DevOps work items, sending status updates and comments back. This guide compares seven connector types side by side.
If you need a breakdown of the specifics of integrating ServiceNow and Azure DevOps (e.g., use cases and what can actually be synced between them), check out Unito’s ServiceNow-Azure DevOps integration guide.
ServiceNow-Azure DevOps connectors compared
| Connector | Direction | Who configures it | Real-time or batch | Records it pairs | Work notes, comments, attachments support | Pricing model | Who maintains it |
| Exalate | One-way or two-way | A ServiceNow or Azure DevOps admin | Real-time | Incidents, change requests, problems and custom entities, with Azure DevOps work items | Scripts decide which journal entries go out; attachments sync | Per item in sync; ServiceNow integrations only available with Pro and Enterprise plans | Exalate updates its connectors; your admin rewrites any Groovy scripts an API change breaks |
| Getint | One-way or two-way | An admin, with no code | Three-minute updates on Tools and Systems plans, near-real-time on Custom plan | Incidents, change requests, tasks and bugs, with Azure DevOps work items | Attachments and comments sync | Per number of events | Getint updates its connectors; your admin fixes mappings that break |
| Zapier | One-way per Zap | Anyone | Trigger-based, intervals vary per plan | One ServiceNow table per trigger, with Azure DevOps work items | No dedicated comment or work note step; a ServiceNow attach-file action exists | Per task; ServiceNow app requires a paid plan | Zapier updates its app integrations; whoever built the Zaps fixes the ones that break |
| Unito | Two-way by default, or one-way | A ServiceNow admin connects a service account; anyone builds the flow | Real-time | With Advanced Sync: any table the account can read and write, with any Azure DevOps work item type | Public comments and work notes, both ways; attachments copied | Per item in sync | Unito |
| Workato | One-way per recipe | Whoever builds the recipes, often an integration team | Real-time and batch triggers | ServiceNow records with Azure DevOps work items | Upload work item attachment action; comments supported | Credit-based | Workato updates its connectors; whoever built the recipes fixes the ones that break |
| ServiceNow Integration Hub Spoke | One-way by default; two-way requires a flow each way | A ServiceNow developer, in Flow Designer | Event-driven flows, plus Azure DevOps service hook triggers | Any record your flow reads, with Azure DevOps Boards work items | Add Attachment action; comment mapping is whatever your flow writes | Subscription-based on top of a ServiceNow plan | ServiceNow updates the spoke; your team maintains flows |
| Custom build | Custom to your build | Your engineers | Whatever you build | Anything each tool’s API exposes | Depends on what you build | Engineering time, hosting, maintenance | Your engineers |
The 7 best ServiceNow-Azure DevOps connectors
Exalate
Exalate is a two-way sync platform that moves data back and forth between tools, such as ServiceNow and Azure DevOps. You can set up Exalate by installing the app in each tool, starting the connection in one system, and approving it in the other. It can sync standard and custom work items, comment threads, and user mentions.
More advanced users can write and deploy Groovy scripts that can execute almost any rule, including syncing custom fields, restricting syncing to internal comments, and more. Exalate also includes an AI assistant, Aida, which can draft scripts from a plain-language description. Exalate is ISO 27001:2022 certified and can run in the cloud, on Docker, or on premises.
Exalate’s scripts are powerful, but they’re code. That means someone has to build and maintain them. Scripts require either technical skill to write them or experience managing AI tools if Aida writes them. That usually means only a few people on your team know how to manage and troubleshoot your Exalate integrations.
Pricing for Exalate has two factors: items in sync and available integrations. The Starter and Scale plans have items-in-sync limits of 25 and 100, respectively. The Pro plan has custom items-in-sync limits, while Enterprise plans have no limit. Azure DevOps is available with all plans, but ServiceNow is only available with Pro and Enterprise plans.
Best for: Integration teams with admins who can code in Groovy or manage AI tools that do.
Getint
Getint is a no-code integration platform that connects ServiceNow and Azure DevOps, plus 17 other tools. It supports both one-way and two-way connections, linking ServiceNow records with Azure DevOps work items, mapping fields and moving comments and attachments between them. Getint also has a migration mode for teams that only need to move historical records over once.
An admin can connect both apps in Getint, picking the ServiceNow table and Azure DevOps project they need to sync, mapping fields and statuses, then choosing integration direction. No coding necessary.
Getint has three pricing plans: Tools, Systems, and Custom. The plans vary in cost and integration availability. The Tools plan is $250 a month and includes integrations for ClickUp, monday.com, Asana, HubSpot, GitHub, Zendesk, Wrike, and GitLab. The Systems plan is $480 a month and also includes integrations for Jira, Azure DevOps, ServiceNow, and Salesforce. The Custom plan includes all integrations, custom setup and deployment, and has custom pricing.
Best for: Admins who need no-code, two-way connections or one-time migrations from the same platform.
Zapier
Zapier is a one-way automation platform with integrations for thousands of apps, including ServiceNow and Azure DevOps. Users build Zaps, each with a trigger in one tool and an action in the other. For example, a Zap could automatically trigger a build in Azure DevOps whenever a specific field in ServiceNow is updated.
You can build a Zap in minutes with no code and no technical skills. Zapier also offers templates that cover popular trigger and action pairings for ServiceNow and Azure DevOps. Each Zap performs a single action, like creating a single work item type or updating a single field when a trigger fires. Zaps are easier to build and deploy than many other integrations.
That said, Zaps have their drawbacks. They only move data in one direction, meaning using Zapier for complex workflows involves chaining multiple Zaps to handle item creation, updates, and comments—especially if you want to do this in both directions. That involves a longer setup time, more maintenance, and troubleshooting to prevent infinite loops and conflicts.
Best for: Simple handoffs that don’t require complex builds or back-and-forth data flow.
Unito
Unito is a no-code, two-way sync platform with over 60 integrations for tools like ServiceNow, Azure DevOps, Salesforce, Jira, and more. Unito users can build flows that connect one type of ServiceNow record with one type of Azure DevOps work item (e.g., ServiceNow incidents and Azure DevOps tasks). Deep rules give users control over what gets synced and when work items get synced, while deep field mappings send data where it needs to go. The ServiceNow-Azure DevOps integration page lists every supported object and field type.
Two-way sync is the default for Unito flows, but users can also build one-way flows or set flow direction for individual field mappings (i.e., some are one-way and others are two-way) to match a workflow’s needs. Unito supports standard and custom fields, comments, attachments, and hierarchies (e.g., Azure DevOps epics, features, requirements, tasks). Business users can set up Unito flows with no code and no technical background.
Some features are only available with Unito’s Enterprise plans, like premium connectors, advanced syncing capabilities, and a dedicated integration consultant.
Best for: Seamless collaboration between ServiceNow and Azure DevOps, powered by integrations anyone can build.
Workato
Workato is an enterprise automation platform built around recipes. A trigger in one app is followed by actions in others. Its ServiceNow-Azure DevOps connector supports both real-time and batch triggers, as well as actions that create and update records and upload attachments. A recipe could, for example, create an Azure DevOps bug whenever a support agent escalates a ServiceNow record.
Workato has over 1,200 connectors and its recipes can branch, transform data, and affect multiple systems as they execute. That allows integration teams to run ServiceNow-Azure DevOps logic alongside other automations.
Each Workato recipe goes in one direction. Keeping a ServiceNow record and an Azure DevOps work item in sync as teams work requires a recipe for each direction (i.e., one to push data from ServiceNow to ADO and one to push data from ADO to ServiceNow).
Best for: Organizations with an integration team that already runs Workato for other systems.
ServiceNow Integration Hub Spoke
ServiceNow’s Integration Hub is a platform that allows developers and engineers to set up automations between ServiceNow and other tools using spokes. Some are pre-built, meaning you only need to pay a subscription fee to access them and start using the integration. The Integration Hub also allows developers to build their own custom spokes with JavaScript and ServiceNow’s APIs.
The Integration Hub is a powerful platform that features over 180 pre-built spokes, including Azure DevOps. The integrations you build with these spokes are highly customizable, allowing for two-way sync and deep field support.
That said, deploying even pre-built spokes can take months, especially if you’re trying to replicate the functionality of true two-way sync platforms. If you have a team dedicated to deploying, managing, and customizing the Integration Hub, then this can be a strong option. Otherwise, it might take more resources to manage than you have available.
Best for: ServiceNow-centric organizations that already pay for an Integration Hub subscription and have a ServiceNow developer.
Custom build
Both ServiceNow and Azure DevOps have REST APIs, meaning that software developers and engineers can build integrations between them from scratch or with platforms that can access these APIs. Custom builds give teams full control over what an integration does and where the data it handles is hosted. A custom integration can match a workflow exactly, rather than forcing a team to adapt its workflows to pre-built integrations.
The main drawback of this method? It’s resource-intensive. Building an integration requires time and effort from in-house engineers or significant budget spend to hire contractors. Costs scale rapidly with either approach, consuming resources that could go to other projects. These costs don’t end when the build’s finished, either. When a custom-built integration breaks, your team (or your hired contractors) has to fix it. With pre-built integrations, vendors maintain and update integrations when APIs, rate limits, and authentication requirements change. When you take these fixes on, they add up over time.
Best for: Organizations with a dedicated integration team and requirements no vendor can meet.
Integration Hub spoke or third-party connector?
When integrating ServiceNow and Azure DevOps, this is the first question a ServiceNow admin needs to answer. Why use a third-party connector when the Integration Hub exists?
For an organization with multiple workflows centering on ServiceNow and a dedicated ServiceNow developer, the Integration Hub might be enough to manage integrations with Azure DevOps. It requires an extra subscription, which is no different from using a third-party connector; at that point, it’s about comparing the costs involved with each option.
But deploying Integration Hub spokes can take weeks, if not months, and maintenance is usually your responsibility. Many third-party connectors take less time to deploy, with maintenance being the vendor’s responsibility.
The question essentially becomes how much deployment and maintenance you want to handle yourself. If you want deeper customization, at the cost of more troubleshooting and longer deployment, then the Integration Hub might be preferable. But if you want a platform that can handle non-ServiceNow integrations and takes less time to deploy, then a third-party connector is preferable.
What about other built-in integrations?
The Integration Hub isn’t the only built-in option for integrating ServiceNow and Azure DevOps. ServiceNow admins might also consider:
- Agile Development 2.0: This allows you to build an agile software development environment right into ServiceNow, integrated with Jira or Azure DevOps. That allows software development planning to happen in ServiceNow while execution happens in Azure DevOps.
- DevOps Change Velocity: This connects boards, repos, and pipelines from Azure DeVOps to ServiceNow change management. It doesn’t specifically sync change requests with work items. Rather, it gives all teams more visibility into a single pipeline, kept aligned across tools.
These built-in integrations have very specific purposes, which can make them great options for these workflows. That said, they have similar limitations to the Integration Hub, and the decision process should be relatively the same with them.
How do work notes and comments cross between ServiceNow and Azure DevOps?
ServiceNow has two kinds of journal entries: work notes and comments. Work notes are meant for internal communication, like when agents collaborate on a support ticket. Comments are meant for all other types of communication, and callers or requesters can see them. Azure DevOps has no such distinction; any comment that lands in it is visible to everyone who has access to the project. That means every integration has to make two decisions:
- Which ServiceNow journal entries go out to Azure DevOps?
- Where do comments from Azure DevOps land when they reach ServiceNow?
Most teams choose to only sync work notes from ServiceNow to Azure DevOps, meaning engineers don’t see customer-facing comments. Then, any replies from Azure DevOps become work notes, meaning customers and requesters don’t see them.
Not all integrations can support this distinction, however. Unito allows users to build rules that filter out either public comments or work notes, and inbound comments become work notes by default. Exalate scripts allow you to differentiate between public comments and work notes when you integrate ServiceNow with Azure DevOps. Automation platforms like Zapier, however, may not have the depth to make this distinction.
Which ServiceNow-Azure DevOps connector fits each job?
| Job to be done | Sync direction | Start with | Watch out for |
| Incident-to-bug escalation: an agent sends an incident to engineering as a bug | Two-way: the incident goes to Azure DevOps, and state plus engineering replies come back | A two-way sync tool that pairs incidents with bugs | Incident Priority is calculated from Impact and Urgency, so map Azure DevOps priority to Urgency. Map closing states to Resolved, not Closed, so auto-close doesn’t strand the bug |
| Change requests tied to a release: a change waits on what ships | Mostly Azure DevOps to ServiceNow: release or pipeline progress updates the change, and approval comes back | DevOps Change Velocity if pipelines should wait for approval; a two-way sync tool if each change pairs with a feature or user story | CAB approval and Azure DevOps states rarely line up. Don’t map “Closed” to “Closed” on both sides |
| Problem records into the backlog: root-cause work lands with engineering | Mostly ServiceNow to Azure DevOps, with fix status and root cause back | A connector that reads the Problem table; check each vendor’s table list, since not every pair page names problems | One problem often links many incidents. Decide whether those incidents travel too or stay in ServiceNow |
| Keeping work notes out of engineering’s view (or customer comments out of the backlog) | Two-way, with filtered journal entries | A tool that filters by entry type: Unito rules, Exalate scripts, or a spoke flow or custom build that you write | Azure DevOps has no private comments, so anything sent lands in the open Discussion. Check where engineering replies land by default |
What a custom ServiceNow-Azure DevOps connector costs to keep alive
“With Celigo, we would have to write all the code and then there’s a ton of work to maintain it. Whereas with Unito, it was as simple as clicking to connect fields between Jira and Wrike.” – Boveda case study
A custom connector doesn’t just cost a significant amount of time, effort, and money to build. It also incurs costs to maintain and troubleshoot.
Built-in or third-party connectors don’t require maintenance and troubleshooting; vendors typically take care of that for you. With custom connectors, you have to maintain and troubleshoot them through API changes, rate limit updates, and similar issues. If a tool you’re integrating releases new fields or you use custom objects extensively, then you need to build these capabilities into your connector over time. With a third-party connector, that kind of maintenance is done after hours, meaning it won’t impact your work or your budget. Additionally, when a custom-built connector breaks, it’s on you to fix it.
There’s another hidden cost most don’t consider. What happens when the engineer who built the connector leaves? A custom ServiceNow-Azure DevOps connector won’t fail the exact day that engineer leaves. It might take weeks or months. Something changes in ServiceNow or Azure DevOps, breaking the integration. An authentication token expires and no one knows how to refresh it. No matter what fails, the result is still the same. ServiceNow updates stop reaching Azure DevOps, and teams only find out when a customer calls in for an update and gets an outdated answer.
The cost then falls on whoever has to try to fix the broken connector. An engineer spends weeks going through code before they can change a single line. Meanwhile, support agents are back to manually copying updates between ServiceNow and Azure DevOps until the connector is back online.
Even when you build a custom connector through a vendor, if that connector requires significant scripting or coding work, you’re paying more than just a monthly subscription or yearly contract fee.
FAQ: ServiceNow-Azure DevOps connector
How do you keep change and problem records in sync between ServiceNow and Azure DevOps?
Use a connector that reads ServiceNow’s Change Request and Problem tables, then pair each table with one Azure DevOps work item type. Change requests usually pair with a feature or user story tied to a release, and problems with a bug. Exalate names both tables on its pair page, and Unito’s Advanced Sync reads any table its account can access. For pipeline-driven change approval, ServiceNow’s DevOps Change Velocity is the native option.
Can ServiceNow requests sync to Azure Boards?
Yes. Requested items (RITMs) live in their own ServiceNow table, so any connector that reads that table can create Azure Boards work items from them. Exalate shows catalog requests creating Azure DevOps work items. Unito’s Advanced Sync keeps the link between a request and its requested items. Zapier can watch the table too, but each Zap moves data in one direction.
How can ServiceNow tickets reach Azure DevOps without exposing internal comments?
ServiceNow splits journal entries into work notes, which only agents see, and additional comments, which the requester sees. Azure DevOps has one open Discussion per work item, so the connector has to filter what goes out. Unito rules can send only public comments or only work notes, and Exalate scripts can filter outgoing comments. Unito lands replies from engineering as work notes by default.
Which ITSM-to-DevOps tools sync attachments and comments in real time?
Exalate and Unito both sync comments and attachments between ServiceNow and Azure DevOps in real time. Getint syncs attachments, with a 3-minute update time on its self-serve plans and close to real time on its Custom plan. Zapier checks ServiceNow at your plan’s interval and has no dedicated comment step. With the Integration Hub spoke, timing and content depend on the flows your team builds.
Is a ServiceNow-Azure DevOps connector bidirectional?
Some offer two-way sync, which updates the ServiceNow record and the Azure DevOps work item from either side. Exalate, Getint and Unito work this way. Zapier and Workato run one direction per Zap or recipe, so two-way means building a flow each way and stopping them from looping. The Integration Hub spoke is two-way only if your team builds a flow in each direction.