System here refers to Azure DevOps Server (TFS)/Azure DevOps Services (VSTS)

  • To continue with the integration you are configuring, it is important that you configure Azure DevOps Server (TFS)/Azure DevOps Services (VSTS) correctly onto OpsHub Integration Manager.
  • In the system configuration page, fill the requisite details.
  • integration


    Sr. No.Field NameWhen field is visible on the System formDescription
    1System NameAlwaysProvide Azure DevOps Server (TFS)/Azure DevOps Services (VSTS) system name
    2Deployment TypeAlwaysChoose the deployment type of server.
    3VersionServer is in On-PremisesPut the version for the Azure DevOps Server (TFS). Refer section 'How to find Azure DevOps Server (TFS)'s version' in appendix to learn how to find version of installed Azure DevOps Server (TFS).
    4Server URLAlwaysIn case of Azure DevOps Server (TFS), set the URL to: http://<host name>:<port no>/tfs; in case of Azure DevOps Services (VSTS) instance, set the URL to: https://<instance name>.visualstudio.com; and for a new Azure DevOps Services (VSTS) instance, set the URL to: https://dev.azure.com/<organization name>.
    5User NameServer is in On-PremisesEnter a primary username with the user domain(if there is any). User must have administrator privileges in Project Administrators user group or Project Collection Administrators user group.
    6User EmailServer is in On-CloudEnter User Email Address. User must have administrator privileges in Project Administrators user group or Project Collection Administrators user group.
    7User PasswordAlwaysIn On-Premises deployed server, enter the primary password and in case of On-Cloud deployment, refer to Alternate Authentication Credentials on Azure DevOps systems.
    8Team Collection NameServer is in On-PremisesFor Azure DevOps Server (TFS), enter the Collection name, for example PrimaryCollection
    9Authentication ModePersonal Access TokenSelect Personal Access Token from the options given in the drop-down menu as the Basic is deprecated.
    10Personal Access TokenAuthentication Mode is Personal Access TokenEnter the Personal Access Token generated for the integration user in the Azure DevOps Services (VSTS). Refer to Personal Access Token section on Azure DevOps Server (TFS) / Azure DevOps Services (VSTS) Pre-requisites page to learn about how to create Personal Access Token.
    11Organization NameServer is in On-CloudProvide Organization name for which project(s) data need to be synchronized. For Azure DevOps Services (VSTS), it would be either DefaultCollection or <instance name> from its instance URL such as https://<instance name>.visualstudio.com. For Azure DevOps Services (VSTS), it would be <organization name> from https://dev.azure.com/<organization name>.
    12Bypass rulesAlwaysSetting Bypass Rules to 'yes' means disabling the rules while writing the changes to the system. This change will allow users to write invalid value(s) to any field in the system. For over writing, 'Changed By', 'Changed Date', etc. fields, enable the Bypass rules. Refer 'Bypass Rule with User Impersonation' in appendix to learn in detail about User Impersonation and ByPass Rule.
    13Service URLAlwaysEnter the service URL where Service is installed. For example: http://localhost:9090/TFSService. Refer to link

    How to find Team Foundation Server’s version

    Please follow given steps to find Azure DevOps Server (TFS) version

  • Open Azure DevOps Server (TFS) Administration Console.
  • You can see the Azure DevOps Server (TFS) instance version detail in right side of panel. Please refer given screenshot for reference.
  • Azure DevOps Server (TFS)
    Bypass Rule with User Impersonation
  • If an integration is configured to Azure DevOps Server (TFS)/Azure DevOps Services (VSTS) from any other system with ‘Bypass Rule’ option enabled, OpsHub Integration Manager will consider the audit revision’s author as the user on the basis of which impersonation is to be performed.
  • Link impersonation will be supported between Azure DevOps Server (TFS)/Azure DevOps Services (VSTS) systems. When two entities are linked then on Azure DevOps Server (TFS)/Azure DevOps Services (VSTS) side, only one entity will contain actual linked added by user while on another entity link will be added by default integration user.
  • Bypass rules also allow Azure DevOps Server (TFS)/Azure DevOps Services (VSTS) system to write any data (valid or invalid ) data into server. OpsHub Integration Manager can create data on past dates as well by enabling this feature.