Merge pull request #8086 from MicrosoftDocs/users/chcomley/pat-entra-repos-round-2

Entra emphasis over PATs - Repos round 2

Author: JillGrant615

docs/repos/git/go-install.md

@@ -1,17 +1,19 @@
 ---
-title: Go install support
+title: Use Go install command support with Azure Repos Git
 titleSuffix: Azure Repos
-description: Learn how to use Go install command with Azure Repos Git
+description: Learn how to use the Go install command with Azure Repos Git repositories using SSH keys, Microsoft Entra ID tokens, or personal access tokens for authentication.
+ai-usage: ai-assisted
 ms.service: azure-devops-repos
 ms.topic: conceptual
-ms.date: 02/26/2025
-monikerRange: '>= azure-devops-2020'
+ms.date: 07/02/2025
+monikerRange: '<= azure-devops'
 ms.subservice: azure-devops-repos-git
+# customer-intent: As a Go developer, I want to use the go install command to download packages from Azure Repos Git repositories so I can manage dependencies in my Go projects with proper authentication.
 ---
 
-# Go install command support in Azure Repos Git
+# Use Go install command support in Azure Repos Git
 
-[!INCLUDE [version-gt-eq-2019](../../includes/version-gt-eq-2019.md)]
+[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
 Go is an open-source programming language, also referred to as Golang. 
 In Go, you can use the `install` command to download and install packages and dependencies. 
@@ -20,9 +22,6 @@ With `go install`, you're able to download packages with their dependencies name
 You can also use the `import` key word inside a go file to specify the import path, using the 
 same syntax described in the following sections.
 
-> [!NOTE]
-> The feature documented in this article requires Azure DevOps Server 2019 Update 1 or later version. 
-
 ## Go install with public projects
 
 If your Azure Repos Git repo is in a [public project](../../organizations/projects/about-projects.md), you can use `go install` using the web repo url in the following format. For version, you can use `latest` or a specific version.
@@ -42,10 +41,10 @@ go install dev.azure.com/<organization>/<project>/_git/<repo>.git/subfolder1/sub
 
 ## Go install with private projects
 
-If your Azure DevOps Git repo is private, you can either use SSH or authenticate with a Personal Access Token (PAT) for HTTPS.
+If your Azure Repos Git repository is private, you can authenticate using SSH keys, Microsoft Entra ID tokens (recommended), or Personal Access Tokens (PATs).
 
 > [!IMPORTANT]
-> To access private Azure Repos Git repositories using go install, you must first set the environment variable `GOPRIVATE=dev.azure.com`. You can set this environment variable locally before building or running.
+> To access private Azure Repos Git repositories using `go install`, you must first set the environment variable `GOPRIVATE=dev.azure.com`. You can set this environment variable locally before building or running.
 
 ### SSH
 
@@ -70,9 +69,44 @@ go install dev.azure.com/<organization>/<project>/<repo>.git
 
 ### HTTPS
 
-To use HTTPS with `go install`, you must create a PAT as described in [Authenticate access with personal access tokens](../../organizations/accounts/use-personal-access-tokens-to-authenticate.md). This PAT requires only the **Code (read)** [scope](../../integrate/get-started/authentication/oauth.md#scopes).
+To use HTTPS with `go install`, you can authenticate using either Microsoft Entra ID tokens (recommended) or Personal Access Tokens (PATs).
+
+#### Microsoft Entra ID tokens (recommended)
+
+Microsoft Entra ID tokens provide better security and are the recommended authentication method. You can obtain these tokens through:
+
+- **Azure CLI** (for development/testing):
+   ```bash
+   az account get-access-token --resource 499b84ac-1321-427f-aa17-267ca6975798 --query "accessToken" --output tsv
+   ```
+
+- **Service Principal** (for production/automated scenarios):
+   - Register an application in Microsoft Entra ID
+   - Create a client secret for the application
+   - Grant the application appropriate permissions in Azure DevOps
+   - Use the service principal credentials to obtain tokens programmatically
+
+For more information, see [Microsoft Entra authentication](../../integrate/get-started/authentication/entra.md).
+
+After you obtain the Microsoft Entra ID token, add this entry to your `.gitconfig` file:
+
+```
+[url "https://<user>:<token>@dev.azure.com/<organization>/<project>/_git/<repo>"]
+	insteadOf = https://dev.azure.com/<organization>/<project>/_git/<repo>
+```
+
+The `<user>` part can be any nonempty string; we suggest using `entra` or your username.
+
+> [!TIP]
+> **Get a one-time Microsoft Entra token from Azure CLI**: You can quickly obtain a Microsoft Entra ID token for Git operations using the Azure CLI, which is useful for development and testing scenarios. When generating tokens on behalf of a service principal, make sure to [sign in as the service principal](/cli/azure/authenticate-azure-cli) first.
+> 
+> **Token management**: Microsoft Entra ID tokens have expiration times, so you might need to refresh them periodically. For automated workflows, consider using service principals with appropriate token refresh mechanisms.
+
+#### Personal Access Tokens (alternative)
+
+If you prefer to use PATs, create a PAT as described in [Authenticate access with personal access tokens](../../organizations/accounts/use-personal-access-tokens-to-authenticate.md). This PAT requires only the **Code (read)** [scope](../../integrate/get-started/authentication/oauth.md#scopes).
 
-After you create the PAT, add this entry to your.gitconfig file:
+After you create the PAT, add this entry to your `.gitconfig` file:
 
 ```
 [url "https://<user>:<token>@dev.azure.com/<organization>/<project>/_git/<repo>"]

docs/repos/git/import-git-repository.md

@@ -1,16 +1,17 @@
 ---
-title: Import a Git repo into your project
+title: Import a Git repository into a project
 titleSuffix: Azure Repos
-description: Import a repo from GitHub, GitLab, or Bitbucket into your project in Azure DevOps.
+description: Import a Git repository from GitHub, GitLab, Bitbucket, or other locations into your Azure DevOps project using secure authentication methods including Microsoft Entra ID tokens.
 ms.assetid: 5439629e-23fd-44f1-a345-f00a435f1430
 ms.service: azure-devops-repos
-ms.topic: quickstart
+ms.topic: how-to
 monikerRange: '<= azure-devops'
-ms.date: 02/14/2025
+ms.date: 07/02/2025
 ms.subservice: azure-devops-repos-git
+# customer-intent: As a developer, I want to import an existing Git repository from GitHub, GitLab, or other providers into Azure DevOps so I can consolidate my source code and use Azure DevOps features for my project.
 ---
 
-# Import a Git repo
+# Import a Git repository to a project
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
@@ -20,32 +21,34 @@ This article shows you how to import an existing Git repo from GitHub, Bitbucket
 
 [!INCLUDE [azure-repos-prerequisites](includes/azure-repos-prerequisites.md)]
 
+## Import into a new repo  
+
+Do the following steps to import into a new repo:
+
 > [!NOTE]
 > When the import of the repository is completed, Azure DevOps sets the **Default** branch for that imported repository. If the imported repository contains a branch named `main`, it gets set as the default branch, otherwise the first branch (in alphabetical order) of the imported repository gets set as **Default**.
 
-## Import into a new repo  
+1. In your browser, sign in to your organization and select **Repos** > **Files**.
 
-1. Select **Repos**, **Files**.
-
-   ![View your branches](media/repos-navigation/repos-files.png)
+   ![Screenshot shows view of branches.](media/repos-navigation/repos-files.png)
 
 2. From the repo drop-down, select **Import repository**.
 
-   ![Manage repositories](media/repo-mgmt/import-repository.png)
+   ![Screenshot shows Manage repositories screen.](media/repo-mgmt/import-repository.png)
 
-3. If the source repo is publicly available, just [enter the clone URL](clone.md#clone_url) of the source repository and a name for your new Git repository.
+3. [Enter the clone URL](clone.md#clone_url) of the source repository and a name for your new Git repository.
 
-   If the source repository is private but can be accessed using basic authentication (username-password, personal access token, etc.),  select **Requires authorization** and enter your credentials. SSH authentication isn't supported, but you can manually import a repository that uses SSH authentication by following the steps in [Manually import a repo using git CLI](#manual-import-git-cli).
+  ![Screenshot shows Import Repository Dialog with publicly available sample repo URL.](media/Import-Repo/ImportRepoDialog.png)
 
-   ![Import Repository Dialog](media/Import-Repo/ImportRepoDialog.png)
+4. Select **Import a repository**.
 
-::: moniker-end
+The repo gets imported.
 
 ## Import into an existing empty repo 
 
 On the **Files** page of the empty Git repository, select **Import** and [enter the clone URL](clone.md#clone_url). Provide credentials if the source repository requires authentication. 
 
-![Import Repository into an existing repository](media/Import-Repo/ImportRepofromEmptyRepo.png)
+![Screenshot shows Import Repository into an existing repository.](media/Import-Repo/ImportRepofromEmptyRepo.png)
 
 > [!NOTE]
 > The import feature disables automated linking for work items mentioned in a commit comment since the work item IDs in the destination project might not be the same as ones in the source project. Automatic linking for work items mentioned in a commit can be re-enabled by navigating to **Settings**, **Version Control**,  selecting your repository, and choosing **Options**. For more information on linking commits with work items, see [Link work items to commits](share-your-code-in-git-vs.md#link-work-items)
@@ -56,8 +59,7 @@ On the **Files** page of the empty Git repository, select **Import** and [enter
 
 You can use [az repos import](/cli/azure/repos/import#az-repos-import-create) to import a repository to your Azure DevOps project.  
 
-> [!NOTE]
-> You must first create the repository in Azure DevOps before you can import a Git repository. Also, the repository you create must be empty. To create a repo, see [Create your Git repo in Azure Repos](share-your-code-in-git-cmdline.md#create-your-git-repo-in-azure-repos).
+You must first create the repository in Azure DevOps before you can import a Git repository. Also, the repository you create must be empty. To create a repo, see [Create your Git repo in Azure Repos](share-your-code-in-git-cmdline.md#create-your-git-repo-in-azure-repos).
 
 ```azurecli
 az repos import create --git-source-url
@@ -81,7 +83,7 @@ az repos import create --git-source-url
 |`org`, `organization`| Azure DevOps organization URL. You can configure the default organization by using `az devops configure -d organization=<ORG_URL>`. **Required** if not configured as default or picked up via git config. Example: `https://dev.azure.com/MyOrganizationName/`.|
 |`project`, `p`|Name or ID of the project. You can configure the default project using `az devops configure -d project=<NAME_OR_ID>`. **Required** if not configured as default or picked up via git config. 
 |`repository`| Name or ID of the repository to create the import request in.  |
-|`requires-authorization`| Flag to indicate if the source git repository is private. If you require authentication, then generate an authentication token on the source repo and set the environment variable `AZURE_DEVOPS_EXT_GIT_SOURCE_PASSWORD_OR_PAT` to the value of the token. Then the import request includes authentication. |
+|`requires-authorization`| Flag to indicate if the source git repository is private. If you require authentication, then generate an authentication token on the source repo and set the environment variable `AZURE_DEVOPS_EXT_GIT_SOURCE_PASSWORD_OR_PAT` to the value of the token. For enhanced security, we recommend using Microsoft Entra ID tokens when possible. Then the import request includes authentication. |
 |`subscription`| Name or ID of subscription. You can configure the default subscription using `az account set -s <NAME_OR_ID>`.|
 |`user-name`| User name to specify when the git repository is private.|
 
@@ -152,7 +154,6 @@ az repos import create --git-source-url https://github.com/fabrikamprime/fabrika
 
 ## Manually import a repo using git CLI
 
-The import repo feature was introduced in the 2017 Update 1. You can also follow these steps to manually import a repo into an Azure DevOps Services repo by replacing "TFS" with Azure Repos in the following steps.
 
 1. Clone the source repo to a temporary folder on your computer using the `bare` option, as shown in the following command line example, and then navigate to the repo's folder. When cloning using the `bare` option, the folder name includes the `.git` suffix. In this example, `https://github.com/contoso/old-contoso-repo.git` is the source repo to be manually imported.
 
@@ -170,7 +171,7 @@ The import repo feature was introduced in the 2017 Update 1. You can also follow
     ```
     
    > [!WARNING]
-   > Using `--mirror` overwrites all branches in the target repo which includes deleting any branches not in the source repo.
+   > Using `--mirror` overwrites all branches in the target repo, which includes deleting any branches not in the source repo.
 
 4. If the source repository has LFS objects, then fetch them, and copy them from the source repo to the target repo.
 
@@ -191,15 +192,31 @@ Although imports are most often successful, the following conditions might cause
 
 * [What if my Source repository is behind two-factor authentication?](#q-what-if-my-source-repository-is-behind-two-factor-authentication)
 * [What if my source repository doesn't support multi_ack?](#multiack)
-* [Can I import from previous versions of Team Foundation Server?](#q-can-i-import-from-previous-versions)
+* [Can I import from previous on-premises versions?](#q-can-i-import-from-previous-versions)
 * [Can I use MSA-based credentials?](#q-can-i-use-msa-based-credentials)
 * [Can I import from TFVC?](#q-can-i-import-from-tfvc)
 * [What if my source repository contains Git LFS objects?](#q-what-if-my-source-repository-contains-git-lfs-objects)
 
 ### Q: What if my source repository is behind two-factor authentication?
 
 A: The import service uses REST APIs to validate and trigger import and can't work directly with repositories that require two-factor authentication.
-Most Git hosting providers like [GitHub](https://help.github.com/articles/creating-an-access-token-for-command-line-use/) and [Azure DevOps Services](../../organizations/accounts/use-personal-access-tokens-to-authenticate.md) support personal tokens which can be supplied to the import service. 
+
+Most Git hosting providers support authentication tokens that can be supplied to the import service:
+
+**Microsoft Entra ID tokens (recommended):** Microsoft Entra ID tokens provide better security and are the recommended authentication method. You can obtain these tokens through:
+
+- **Azure CLI** (for development/testing):
+   ```bash
+   az account get-access-token --resource 499b84ac-1321-427f-aa17-267ca6975798 --query "accessToken" --output tsv
+   ```
+
+- **Service Principal** (for production/automated scenarios):
+   - Register an application in Microsoft Entra ID
+   - Create a client secret for the application
+   - Grant the application appropriate permissions in Azure DevOps
+   - Use the service principal credentials to obtain tokens programmatically
+
+**Personal Access Tokens (alternative):** [GitHub](https://help.github.com/articles/creating-an-access-token-for-command-line-use/) and [Azure DevOps](../../organizations/accounts/use-personal-access-tokens-to-authenticate.md) also support personal access tokens. 
 
 <a id="multiack"></a>
 
@@ -211,13 +228,12 @@ This failure can happen when creating import request or while import is in progr
 
 ### Q: Can I import from previous versions?
 
-A: If the source Git repository is in a TFS version earlier than TFS 2017 RTM, then import fails.
-This happens because of a contract mismatch between the latest Azure DevOps and previous versions.
- 
+A: If the source Git repository is in an on-premises version earlier than 2017 RTM, then the import fails, due to a contract mismatch between the latest Azure DevOps and previous versions.
+
 ### Q: Can I use MSA-based credentials?
 
-A: Unfortunately, MSA (Microsoft Account, formerly Live ID) based credentials don't work. Import service relies on basic authentication to communicate with the source repository. If the username / password you're using aren't basic auth then authentication and import fail.
-One way to check if the username / password you're using are basic auth or not is to try using Git to clone your repository using the following format
+A: Unfortunately, MSA (Microsoft Account) based credentials don't work. Import service relies on basic authentication to communicate with the source repository. If the username and password you're using aren't basic auth, then authentication and import fail.
+One way to check whether the username / password you're using are basic auth is to try using Git to clone your repository using the following format:
 
 ```
 git clone https://<<username>>:<<password>>@<<remaining clone Url>>