Use Git Credential Managers to Authenticate to Azure Repos
Azure Repos | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | VS 2017 | VS 2015
Git Credential Managers simplify authentication with your Azure DevOps Services/TFS Git repos. Credential Managers let you use the same credentials that you use for the Azure DevOps Services/TFS web portal and support multi-factor authentication through Microsoft Account (MSA) or Azure Active Directory (Azure AD). In addition to supporting multi-factor authentication with Azure DevOps Services, the credential managers also provide support two-factor authentication with GitHub repositories.
Azure DevOps Services provides IDE support for MSA and Azure AD authentication through Team Explorer in Visual Studio, IntelliJ and Android Studio with the Azure Repos Plugin for IntelliJ, and Eclipse (with the Team Explorer Everywhere plug-in). If your environment doesn't have an integration available, configure your IDE with a Personal Access Token or SSH to connect with your to your repos.
Install the Git Credential Manager
Download and run the latest Git for Windows installer, which includes the Git Credential Manager for Windows. Make sure to leave the Git Credential Manager installation option enabled when prompted.
macOS and Linux
We recomend using SSH keys to authenticate to Azure DevOps, not a credential manager.
Review the system and software requirements before installing the credential manager.
On macOS and Linux, there are several install options that use native package managers to install the credential manager. After installing the package for your platform, run the following command to configure Git to use the credential manager :
> git-credential-manager install
Using the Git Credential Manager
When you connect to a Git repo in Azure Repos from your Git client for the first time, the credential manager prompts for your Microsoft Account or Azure Active Directory credentials. If your account has multi-factor authentication enabled, you are prompted to go through that experience as well.
Once authenticated, the credential manager creates and caches a personal access token for future connections to the repo. Git commands that connect to this account won't prompt for user credentials until the token expires or is revoked through Azure DevOps Services/TFS.
You can open up and report issues with the Git Credential Manager for Windows on the project GitHub. Frequently Asked Questions for the Git Credential Manager for Windows are available in the online readme.
Manual installation steps for the Windows Git Credential Manager and the macOS and Linux Git Credential Manager are available. Use these steps to install the credential manager if the recommended steps above are not suitable for your environment.
In addition to providing full source code, we've also documented how the credential manager integrates with Git. Refer to the MSDN blog posts on the macOS and Linux Git Credential Manager and the Windows Credential Manager. There is also an article on the project GitHub with information on the low-level internals of the Git Credential Manager for Windows.