Connect ServiceNow and AzureDevOps Code-free with Unito

Connect ServiceNow and AzureDevOps Code-free with Unito

Published in Use cases on , last updated .

This tutorial will show you how to connect ServiceNow, Azure DevOps, and your IT management processes with a no-code 2-way integration that anyone can set up quickly. No scripts, no knowledge of programming languages required.

After all, migrating from one IT Management system to another is no simple task for any organization, regardless of size. Though, obviously, the larger your business, the more data there is to maintain, and the harder it is to move everything safely out of a legacy system into a modern IT Management platform such as ServiceNow. Or perhaps your organization is using multiple additional tools such as Jira or Azure DevOps to support work on issues, incidents, and other IT requests such as ITSM.

You can integrate the apps and tools you use for work, but most integration solutions on the market require knowledge of specific scripting languages and take significant time investment to build and maintain. Most, but not all. Unito is a no-code solution for integrating ServiceNow, Azure DevOps, Jira, and many other industry-leading tools. Here’s how it works:

In this article:

Setup in ServiceNow

Connecting ServiceNow to Unito for the first time

All you need to connect ServiceNow to Unito is your:

  • ServiceNow Domain URL: https://INSTANCENAME.service-now.com
  • ServiceNow Username
  • ServiceNow Password

Before you can connect to Unito with a new ServiceNow user, you’ll need to disable the Password reset flag.

Here’s how (click to expand):
  1. Log in to your ServiceNow instance as an administrator.
  2. Navigate to the User Administration > Users section.
  3. Locate the user account that you’ll be using for the Unito integration.
  4. On the user record, set Password needs reset to false.
  5. Save the changes.

Choose a ServiceNow table to sync with Azure DevOps

ServiceNow is vastly configurable in countless ways, but Unito is able to link records from your tables no matter how your instance is configured. But you’ll still need to consider what records precisely you plan to sync. In our demo use case, we’re syncing records from a table called Incidents into Azure DevOps.

Here’s how to find tables in ServiceNow (click to expand)

From your ServiceNow dashboard, select All > System Definition > Tables

Then, narrow down your search to the table you’re looking for. Beside Table select Name (or any other method of finding the right table in your organization). In our case, we searched for Incident:

We’ll keep this information in mind as we build our flow and come back to it later.

Setup in Microsoft Azure DevOps

In Azure DevOps, you must adjust your Organization Settings to make sure that Third-party application access via OAuth is turned on.

  • From your organization, go to Organization Settings > Policies > Third-party application access via OAuth
Learn more about Third-party application access here.

Step 1. Connect a ServiceNow table and Azure DevOps project to Unito

  • Sign up for Unito if you haven’t already!
  • Navigate to the Unito App and select +Create Flow.
  • Select Start Here to connect ServiceNow and Azure DevOps.
  • Then +Choose account to specify the ADO Project and ServiceNow Table you plan on syncing.
  • Click Confirm.
As described above, we chose the table Incident by typing it into the search box.

Step 2. Choose a flow direction for creating new records or work items

Your no-code Unito flow lets you automatically create new ServiceNow records or ADO work items based on your manual activity.

Select a flow direction with one of the three directional arrows to indicate: from ServiceNow to ADO, ADO to ServiceNow, or both.

This is an example of a 2-way flow between ServiceNow and Azure DevOps. If anyone on my team manually creates a new work item or record, it will automatically appear in the other tool with real-time updates as changes are made.

If you choose a one-way flow at this stage, you can still apply 2-way sync to individual fields in Step 4.

Step 3. Filter out unrelated data from syncing by setting rules

Now we can set up rules to determine which trigger events will create new ServiceNow records or Azure DevOps work items.

This is extremely useful for filtering out unrelated data from syncing between your tools. Make sure to apply a rule that filters out work items or records to match your use case.

In this example, Unito will only create work items in Azure DevOps if a record is created in ServiceNow after April 23, 2024, the City (a choice field) is New York, and the Urgency is one or more of the options listed above.

Select Add a new rule to establish rules for each directional flow.

You can apply custom tags or labels to your rules to be even more precise about what kind of data is shared.

In this example, we created a tag in Azure DevOps called production-outage. Only work items with that tag applied will create new records in ServiceNow and stay in sync.

Work items and records that match your rules will stay in sync with Unito. As soon as the rules no longer apply, that item will stop syncing. For example, if the production-outage tag above is removed from a synced work item, Unito will no longer keep it updated unless the tag is added again.

Find out more about setting rules in Unito.

This is where you tell Unito which fields in ServiceNow to link with similar fields in Azure DevOps so that manual changes in one affect the other automatically.

When you first open this screen, you’ll be presented with two options. Select Auto-map to begin with a prebuilt template that can later be modified.

Click + Add mapping to add a new pair of fields to be synced. Then, click Select a field for each tool, and find the appropriate field to map.

Tip: If you aren’t sure where to put data from one tool when it syncs over to the other, you can always add it to the Description Footer.

If you see a gear icon beside a field, that indicates a choice field, status, drop-down or pick list field. Clicking on the gear will allow you to customize the individual values or statuses of that field to link them with values or statuses in your other tool.

In this case, we’ve aligned the Closed, Resolved and Canceled fields in ServiceNow with the Done state in Azure DevOps. If a work item is marked Done, it will become Closed in ServiceNow. Only the first item in a list of values can sync automatically. So in this case, a record can only be changed to Resolved or Canceled if it is selected manually in ServiceNow.

Find out more about setting field mappings.

Step 5. Launch your ServiceNow Azure DevOps integration

If you’ve followed the steps above, your flow will now: 

  • Add a new work item in Azure DevOps when a record is created in ServiceNow based on the rules you set in Step 3.
  • Create a new record in ServiceNow when you manually add a ADO work item based on your rules.
  • Keep ServiceNow records and ADO work items in sync as long as they match the conditions of your rules.
Here’s a quick snapshot of our synced ServiceNow record and Azure DevOps work item, highlighting a few of the fields that are being kept in sync.

If you have any questions, don’t hesitate to reach out and let us know.

What’s next after you sync ServiceNow and Azure DevOps with Unito?

Resources for ServiceNow users

FAQ: Azure DevOps ServiceNow integration

More about this ServiceNow Azure DevOps integration

ServiceNow and Azure DevOps serve as cornerstone technologies in the world of IT operations and software development respectively.

ServiceNow excels in streamlining service management processes across various departments within an organization, making it invaluable for tasks ranging from incident reporting to asset management, ITSM (IT Service Management), and ITOM.

On the other hand, Azure DevOps provides a comprehensive suite tailored for dev teams, supporting everything from project planning and source code management to deployment at scale.

Together, these platforms create an environment where Agile methodologies thrive and operational efficiencies are heightened across both ITSM and DevOps practices.

The benefits of such an integration cannot be overstated:

  • Enhanced Collaboration: Establishes a bridge between your tech support teams using ServiceNow by connecting them directly with the development teams working within Azure DevOps.
  • Streamlined Processes: Automates interactions such as incident resolutions or pushing updates on development progress back into ticket tracking metrics inside ServiceNow.
  • Real-Time Visibility: Ensures that all stakeholders have access to up-to-date information on issues handling or project status without manual updates or syncs.

By adopting this integration through Unito, companies unlock new realms of productivity without getting tangled in complex scripting or extensive configurations; they merely connect their accounts once then manage everything from a clearly laid-out interface provided by Unito.

What are some examples of use cases for this ADO ServiceNow integration?

This process involves understanding your current pain points and aligning them with the capabilities that the integration offers. Here are just a few typical scenarios where connecting ServiceNow and Azure DevOps could greatly enhance your IT operations:

  • Incident Management Automation: Automatically sync incidents from ServiceNow to Azure DevOps as bugs or tasks. This synchronization ensures developers are immediately aware of issues requiring their attention without manual ticket transfer.
  • Change Request Management: Changes in Azure DevOps can be set up to automatically create or update change requests in ServiceNow. It facilitates better traceability and compliance adherence by logging all changes directly into ServiceNow from Azure DevOps.
  • Development Cycle Speed: Streamline interactions between your IT service management (ITSM) and development teams. When developers resolve issues tracked in Azure DevOps, ServiceNow tickets are automatically created and updated, keeping all stakeholders informed.

Choosing a use case will help focus your integration efforts on areas with substantial benefits. Moreover, prioritizing a scenario that resonates most closely with your team’s needs will maximize the return on investment of deploying such integrations live into your system architecture.

Why sync ServiceNow to ADO?

Before you jump into the technicalities, it’s crucial to have a clear understanding of what you aim to achieve with your integration. Do you want to enhance your incident management process? Or perhaps automate deployment tasks? Identifying your goals early on guides the setup process and helps in focusing only on the necessary functionalities, thus avoiding unnecessary complexities.

  • Simplify Collaboration: By creating a mutual channel for updates between teams.
  • Improve Visibility: Ensuring that team members have access to real-time data across both platforms.
  • Enhance Tracking: Automating task updates reduces manual errors and delays.

Maintain Regular Synchronization

To ensure smooth cooperation between ServiceNow and Azure DevOps, regular synchronization is key. This doesn’t mean constant updates flooding both systems but rather scheduled syncs that keep everyone informed without overwhelming the workflow.

  • Decide on an update frequency that matches the pace of your projects – whether it’s hourly or daily.
  • Use filters to synchronize only relevant data, which will minimize noise and maximize relevance.

Consistent updates encourage transparency within teams and facilitate proactive decision-making with real-time data.

The integration not only enhances collaboration across teams but also optimizes resource utilization, ensuring that key information is always synced and accessible. The ability to push updates from Azure DevOps to ServiceNow and vice versa minimizes the chances of discrepancies, thereby maintaining operational consistency.

Book us for an assessment

Get in touch