Connect Azure DevOps and SolarWinds Service Desk to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Azure DevOps with SolarWinds Service Desk - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "Completed Build" from Azure DevOps.
Add your action
An action happens after the trigger—such as "Create Asset" in SolarWinds Service Desk.
You’re connected!
Zapier seamlessly connects Azure DevOps and SolarWinds Service Desk, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- Build DefinitionRequired
- Build Status
- ProjectRequired
Try ItTriggerInstant- ProjectRequired
- Repository
- Branch
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
Try ItTriggerInstant- ProjectRequired
- Build DefinitionRequired
ActionWrite
- ProjectRequired
- PathRequired
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
- Contains StringRequired
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
- Changed Field
Try ItTriggerInstant- ProjectRequired
- TypeRequired
- TitleRequired
- Area
- Iteration
- Assigned To
- Description
ActionWrite
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Frequently Asked Questions about Azure DevOps + SolarWinds Service Desk integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Azure DevOps and SolarWinds Service Desk
How does the integration between Azure DevOps and SolarWinds Service Desk work?
The integration works by automatically creating a linked work item in Azure DevOps whenever a new incident or service request is logged in SolarWinds Service Desk. This helps ensure that development teams are immediately informed of issues that may need their attention.
What triggers are available with this integration?
The integration supports triggers like the creation of a new incident, change, or service request in SolarWinds Service Desk. These events can initiate the creation or update of work items in Azure DevOps, allowing for streamlined communication between IT service and development teams.
Can I customize the actions taken when an event is triggered?
Yes, you can customize actions such as creating specific types of work items or assigning them to particular team members. For instance, when an incident is logged in SolarWinds Service Desk, you can configure it to automatically create a bug report assigned to a certain developer in Azure DevOps.
Is it possible to update existing tickets with this integration?
Absolutely, the integration allows updates to existing tickets. For example, status changes in an Azure DevOps work item can trigger updates back to the related ticket in SolarWinds Service Desk, ensuring both systems reflect current progress.
What kind of information can be synchronized between the two platforms?
You can synchronize various pieces of information such as ticket titles, descriptions, comments, attachments, and status updates. This ensures all relevant data is accessible on both platforms without redundant manual entry.
Do I need any special permissions to set up the integration?
To set up the integration, administrative permissions are typically required on both platforms. This ensures that all necessary access rights are available for creating and updating records as needed.
How frequently does data synchronization occur between Azure DevOps and SolarWinds Service Desk?
Data synchronization generally occurs in real-time or near real-time depending on configuration settings. The aim is to minimize latency so that updates reflect almost immediately across systems.