Azure DevOps + ServiceNow
Connect Azure DevOps and ServiceNow to Unify Dev and IT Operations
Automate the handoff between engineering workflows and IT service management so every team works from the same source of truth.
Why integrate Azure DevOps and ServiceNow?
Azure DevOps and ServiceNow cover two worlds that need to talk constantly but usually don't — not without friction. Engineering teams track sprints, bugs, and deployments in Azure DevOps while IT and support teams manage incidents, change requests, and SLAs in ServiceNow. When these platforms run in silos, information gets lost in handoffs, resolution times balloon, and compliance suffers. Integrating Azure DevOps with ServiceNow through tray.ai closes that gap by automating the bidirectional flow of data between development and operations.
Automate & integrate Azure DevOps & ServiceNow
Use case
Incident-to-Work Item Escalation
When a high-priority incident is raised in ServiceNow, tray.ai automatically creates a linked work item or bug in Azure DevOps, pre-populated with incident details, severity, and affected services. Engineers begin working immediately without waiting for a manual handoff, and the Azure DevOps work item ID is written back to the ServiceNow incident for full traceability.
Use case
Change Request Approval Gating for Deployments
Before a release pipeline in Azure DevOps can deploy to production, tray.ai checks ServiceNow for an approved change request tied to that release. If no approved CR exists, the pipeline pauses and a new change request is automatically created and routed for approval. The pipeline only resumes once ServiceNow confirms the approved status.
Use case
Deployment Status Sync to ServiceNow CMDB
Every successful deployment in Azure DevOps triggers a tray.ai workflow that updates the corresponding Configuration Item in the ServiceNow CMDB with the new software version, deployment timestamp, and pipeline run details. The CMDB stays current without anyone on the ops team touching it manually.
Use case
Bug Triage from ServiceNow Problem Records
When a Problem record is raised in ServiceNow following a recurring incident, tray.ai automatically creates a linked Bug work item in Azure DevOps with full problem details and affected CI information. Engineers can triage and fix the root cause while ServiceNow Problem Managers track progress through synchronized status updates flowing back automatically.
Use case
Sprint Completion Notifications and SLA Reporting
When an Azure DevOps sprint closes, tray.ai compiles completed work items related to open ServiceNow incidents and problems, then updates those records and sends a summary to ITSM stakeholders. Service managers can immediately see which engineering deliverables resolved outstanding service issues — no chasing required.
Use case
Automated Rollback Incident Creation
When Azure DevOps detects a failed release or triggers a rollback, tray.ai immediately raises a ServiceNow incident with the pipeline failure details, impacted environment, and a link to the failed run. The incident is automatically assigned to the on-call team and a post-incident review task is created so nothing gets quietly dropped.
Use case
Developer Onboarding and Access Request Automation
When a new developer is added to an Azure DevOps organization or project, tray.ai triggers a ServiceNow Service Catalog request to provision the required tools, access rights, and equipment. Status updates from the ServiceNow fulfillment workflow feed back into an onboarding tracking board in Azure DevOps, so engineering managers always know where things stand.
Get started with Azure DevOps & ServiceNow integration today
Azure DevOps & ServiceNow Challenges
What challenges are there when working with Azure DevOps & ServiceNow and how will using Tray.ai help?
Challenge
Bidirectional Data Sync Without Infinite Loops
When changes in Azure DevOps trigger updates in ServiceNow and vice versa, naive integrations create feedback loops where each update fires another webhook event endlessly. This gets particularly bad when syncing status fields, comments, and priority across both platforms.
How Tray.ai Can Help:
tray.ai has built-in loop detection and conditional branching logic that stamps records with a sync source identifier. Workflows check whether an update came from the integration before triggering outbound actions, breaking the loop cleanly without custom code or middleware.
Challenge
Inconsistent Field Mapping and Data Schemas
Azure DevOps work item types — Epics, Features, User Stories, Bugs, Tasks — don't map one-to-one to ServiceNow record types such as Incidents, Problems, Change Requests, and Tasks. Priority scales, state labels, and custom fields differ significantly between the two platforms.
How Tray.ai Can Help:
tray.ai's data mapping tools and JSONPath operators let teams define precise transformation logic that translates Azure DevOps work item types and field values into their ServiceNow equivalents. Lookup tables and conditional logic handle priority normalization and custom field mapping without writing code.
Challenge
Managing Authentication and Permission Boundaries
Azure DevOps uses Personal Access Tokens and OAuth scoped to organizations and projects, while ServiceNow uses OAuth 2.0 or basic authentication tied to service accounts with role-based permissions. Keeping secure, long-lived credentials for both platforms in an integration context is operationally messy.
How Tray.ai Can Help:
tray.ai stores credentials for both Azure DevOps and ServiceNow in an encrypted, centralized credential vault with role-based access controls. Token refresh is handled automatically for OAuth connections, and tray.ai supports service account authentication for ServiceNow without exposing credentials in workflow configurations.
Challenge
Handling High-Volume Incident and Pipeline Event Bursts
During major outages or large CI/CD release waves, ServiceNow can generate hundreds of incidents simultaneously while Azure DevOps fires dozens of pipeline events within minutes. An integration that can't handle this volume will drop events, create duplicate records, or time out.
How Tray.ai Can Help:
tray.ai's event queue and scalable workflow execution engine handle burst traffic by processing events asynchronously and in parallel. Deduplication logic within workflows prevents duplicate work items or incidents from being created even when the same event fires multiple times during a surge.
Challenge
Compliance Auditing and End-to-End Traceability
Regulated industries need a complete, auditable trail linking every production deployment in Azure DevOps to an approved change record in ServiceNow and any resulting incidents. Assembling that trail manually across two platforms is slow and error-prone, especially when an auditor is waiting.
How Tray.ai Can Help:
tray.ai logs every workflow execution with full input and output payloads, timestamps, and step-level detail. Combined with bidirectional record linking written into both platforms, compliance and audit teams get a complete, queryable history of how every deployment, change request, and incident relates to one another — accessible directly within tray.ai without touching either source system.
Start using our pre-built Azure DevOps & ServiceNow templates today
Start from scratch or use one of our pre-built Azure DevOps & ServiceNow templates to quickly solve your most common use cases.
Azure DevOps & ServiceNow Templates
Find pre-built Azure DevOps & ServiceNow solutions for common use cases
Template
ServiceNow Incident to Azure DevOps Bug — Auto-Create and Sync
Automatically creates a Bug work item in Azure DevOps whenever a ServiceNow incident exceeds a defined priority threshold, syncing status and comments bidirectionally until the bug is resolved and the incident is closed.
Steps:
- Trigger on new or updated ServiceNow incident where priority is P1 or P2
- Create a linked Bug work item in the designated Azure DevOps project with mapped fields
- Write the Azure DevOps work item ID back to the ServiceNow incident as a related record
- Poll for status changes in Azure DevOps and sync updates back to the ServiceNow incident
- Close the ServiceNow incident automatically when the Azure DevOps bug reaches Resolved state
Connectors Used: Azure DevOps, ServiceNow
Template
Azure DevOps Release Pipeline — ServiceNow Change Request Gate
Pauses an Azure DevOps release pipeline pending an approved ServiceNow change request, automatically creating the CR if one doesn't exist, and resuming the deployment only after ServiceNow approval is confirmed.
Steps:
- Trigger on Azure DevOps release pipeline reaching a pre-deployment approval gate
- Query ServiceNow for an existing approved change request linked to the release
- If no approved CR exists, create a new Standard or Normal change request in ServiceNow
- Poll ServiceNow for approval status on a scheduled interval
- Approve the Azure DevOps pipeline gate and resume deployment once CR is approved
Connectors Used: Azure DevOps, ServiceNow
Template
Deployment Event to ServiceNow CMDB Version Update
Updates the relevant ServiceNow CMDB configuration item with new version and deployment metadata every time an Azure DevOps pipeline completes a successful production deployment.
Steps:
- Trigger on successful Azure DevOps pipeline run targeting the production environment
- Extract service name, version number, and deployment timestamp from the pipeline payload
- Query ServiceNow CMDB to locate the matching Configuration Item by service name
- Update the CI record with the new version, deployment date, and pipeline run URL
Connectors Used: Azure DevOps, ServiceNow
Template
ServiceNow Problem Record to Azure DevOps Bug Triage Workflow
Creates and tracks a Bug work item in Azure DevOps whenever a Problem record is opened in ServiceNow, keeping both records in sync throughout the root-cause investigation and fix cycle.
Steps:
- Trigger on new Problem record creation in ServiceNow
- Create a Bug work item in Azure DevOps with problem description, affected CI, and priority
- Link the ServiceNow Problem record to the Azure DevOps work item using external references
- Sync status updates from Azure DevOps back to the ServiceNow Problem record
- Mark the ServiceNow Problem as Resolved when the Azure DevOps bug is closed
Connectors Used: Azure DevOps, ServiceNow
Template
Azure DevOps Failed Deployment to ServiceNow Incident and Post-Incident Task
Automatically raises a ServiceNow incident and a linked post-incident review task whenever an Azure DevOps release pipeline fails or a rollback is initiated, so no failed deployment goes untracked.
Steps:
- Trigger on Azure DevOps pipeline failure or rollback event
- Create a high-priority ServiceNow incident with pipeline failure details and environment name
- Assign the incident to the on-call assignment group via ServiceNow on-call schedule
- Create a linked ServiceNow task for post-incident review with a defined due date
Connectors Used: Azure DevOps, ServiceNow
Template
New Azure DevOps Project — ServiceNow Service Catalog Provisioning
Triggers a ServiceNow Service Catalog fulfillment request to provision environments, access, and tooling whenever a new project is created in Azure DevOps, and tracks fulfillment progress back in the DevOps platform.
Steps:
- Trigger on new project creation event in Azure DevOps
- Submit a ServiceNow Service Catalog request for environment and access provisioning
- Monitor ServiceNow request fulfillment status via polling
- Post fulfillment status updates as comments on the Azure DevOps project wiki or a tracking work item
- Notify the project lead when all provisioning tasks are completed in ServiceNow
Connectors Used: Azure DevOps, ServiceNow