Microsoft TFS integration with ServiceNow

[Sudharshan Mohi]

Hi Team - We will be proceeding TFS integration with ServiceNow through API which is bi-directional and would like to have below information.

a) What is the prerequisites for integration

b) Best practice for this integration

c) Any documents for reference.

[Community Alums]

Hi @Sudharshan Mohire ,

To read in detail about ServiceNow TFS integration, go to this link: https://www.opshub.com/tfs-integration/tfs-servicenow-integration/

Please find basic details from this video - have watched this while ago. Hopefully this may be helpful.

Tasktop Sync Demo - ServiceNow and TFS Integration - YouTube

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Sudharshan Mohi]

Hi Sandeep - We explored this option but customer is has rejected having integration through Opshub. So this may not be used in our case.

[Gavin Jolly2]

We recently implemented Microsoft Azure DevOps Integration for Agile Development (servicenow.com) to integrate a ServiceNow instance with Azure Devops. The ServiceNow OOTB solution has a few quirks but it works. We currently have 4 open cases with ServiceNow for issues with the solution regarding Images in descriptions.

• If using Agile Devops integration the OOTB mapping provided by ServiceNow is broken and does not work with ADO unless modified
• OOTB ServiceNow tries to make ADO User Stories have an Epic as a parent. In ADO this does not work
• Defects are not mapped
• Business Rules need to be updated to transfer attachments
• OOTB the HTML fields Description and Acceptance Criteria are not mapped
• Description is a string in ServiceNow but Rich Text in ADO. We had to add a u_description HTML field to Epics, Stories and Defects in ServiceNow
• The User account in ADO cannot be an actual user in ServiceNow
• The Bulk import does not import the Description or Acceptance Criteria - This is due to the ADO API ServiceNow uses for performance reasons

[Sudharshan Mohi]

Thanks Gavin. In our current scope we do have bi-driectional communication with respect to Change and Release modules. Do you any specific points to highlight. Also would like to know if REST API is the best approach.