Servicenow Integration with Azure Devops for migrating update sets

[JRY]

Hi all,

I am seeking guidance on integrating ServiceNow with Azure for migrating update sets across different ServiceNow environments. Specifically, I would like to understand the required steps and best practices for this integration.

I have already installed the Microsoft Azure DevOps Pipeline plugin, generated an access token on Azure, and updated it in the Microsoft Azure DevOps Pipeline Connection. However, I need assistance in determining the next steps to complete the setup successfully.

Is there a process document available, or could someone provide insights into the necessary configurations and workflows? Any guidance or documentation would be greatly appreciated.

Thanks,

JRY

[Mahathi]

Hi @JRY ,

Not sure if you have already tried ServiceNow Documentation and Official Microsoft Documentations.

Sharing links for reference: 
https://www.servicenow.com/docs/bundle/utah-devops/page/product/enterprise-dev-ops/task/config-dev-o...

https://learn.microsoft.com/en-us/azure/devops/pipelines/release/approvals/servicenow?view=azure-dev...

I am also sharing a link i found in Linkedin with a video, this might be helpful: 

https://www.linkedin.com/pulse/servicenow-azure-devops-integration-step-guide-zigiwave/

If my answer helped in any way, please mark it as ✅Correct & 👍Helpful

Regards,
Mahathi

[Vishal36]

Hi @JRY,

Btw, I’m curious—why are you going with a plugin? You may want to consider the below points:

• One-Way Sync Only: The plugin syncs only from ServiceNow to ADO. What if you need to sync back fields like status updates or comments from ADO to ServiceNow?
• Low data richness: Will comments, attachments, links, inline images, and rich text formatting be preserved? For example, if a ServiceNow incident includes an inline image—like an error screenshot that’s critical for troubleshooting—will it appear the same way in ADO?
• Pipeline complexity and sync delay: Syncing relies on pipelines, which can cause delays. What if you need real-time updates, like a critical incident in ServiceNow reflecting in ADO instantly? Managing pipelines adds extra complexity.
• Dependency on Azure environment: Since the plugin relies on Azure DevOps, any issues or changes in Azure could impact your sync process. How will you ensure continuity if Azure faces downtime or changes?
• Scalability issues: Can it handle multiple ServiceNow instances and growing project demands, or will it slow down as your team expands?

Here, you can use OpsHub’s [ServiceNow and Microsoft partner] free edition. It can sync comments, attachments/Inline images, links bidirectionally, without much technical knowledge. You can also look at Snow ADO sync for more information.

Hope this helps! 

Thanks

[Mathieu Lepoutr]

Dear @JRY 

You might want to look into Exalate—it can help manage integrations like this between ServiceNow and Azure DevOps with more control over syncing update sets and workflows.