You are viewing the documentation of TeamCity 2018.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Learn more about authentication in Azure DevOps.



The following authentication options are available in Azure DevOps.


Personal Access Tokens

To use access tokens, you need to create a personal access token in your Azure DevOps account, where you have to set some Code access scope in your repositories and use it when configuring a VCS root.

UsernameLeave blank for TFVC, any value for Git, e.g. username
PasswordEnter your personal access token created earlier

Required Access Scope

TFS subsystemScopes
TFVCAll scopes
GitCode (read) / Code (read and write) for versioned settings
Work ItemsWork items (read)
Commit StatusCode (status)

Alternate Authentication Credentials

To use the login/password pair authentication, you have to enable alternate credentials in your Azure DevOps account, where you can set a secondary username and password to use when configuring a VCS root.

NTLM/Kerberos on Linux and Mac OS X
NTLM/Kerberos on Linux and Mac OS X

NTLM/Kerberos on Linux and macOS

To use this authentication method, check that your machine includes Kerberos libraries and that the authentication is properly configured. If you encounter any issues, please check the steps described in the Microsoft documentation.

For more details on this, please see [this post|http://blogs.msdn.com/b/buckh/archive/2013/01/07/how-to-connect-to-tf-service-without-a-prompt-for-liveid-credentials.aspx] or [this document|https://tfs.visualstudio.com/en-us/learn/code/use-git-and-vs-with-tfs].