docs/integrations/azure-devops.md
GitHub Desktop now provides support for Git Credential Manager (GCM), which makes the task of authenticating to Azure DevOps repositories easy and secure. This feature can be enabled by going to File > Options > Advanced on Windows, or GitHub Desktop > Preferences > Advanced on macOS, and then selecting the Use Git Credential Manager checkbox.
When GCM is enabled all credentials for Azure DevOps will be handled, and stored, outside of GitHub Desktop. GCM supports browser authentication and will avoid the need to create personal access tokens (PATs).
Your browser will open to authenticate to your Azure DevOps account using GCM when you go to File > Clone Repository > URL and enter the HTTPS clone URL of the repository.
If you would prefer not to use GCM and need to create a personal access token in Azure DevOps you can follow the steps below.
To authenticate against Azure DevOps repositories you will need to create a personal access token.
Click New token to create a new personal access token. Give it a name, select the organizations you would like the token to apply to, and choose when you would like the token to expire.
3 . Under the Scopes section choose Custom defined and then select Read & Write under the Code section. This will grant GitHub Desktop read and write access to your Azure DevOps repositories.
4 . Click Create to create a new token, and then copy it to your clipboard.
Open GitHub Desktop and go to File > Clone Repository > URL. Enter the Git URL of your Azure DevOps repository. Make sure you enter the correct URL, which should have the following structure:
https://<username>@dev.azure.com/<username>/<project_name>/_git/<repository_name>
You will receive an Authentication Failed error. Enter your Azure DevOps username and paste in the token you just copied to your clipboard. Click Save and Retry to successfully clone the repository to your local machine in GitHub Desktop.