Merge branch 'main' into users/sdanie/440878

Author: steved0x

docs/artifacts/reference/limits.md

@@ -29,7 +29,7 @@ Azure Artifacts is a highly scalable package management solution that enables de
 
 - **NuGet packages**: limited to 500 MiB per file.
 
-- **Npm packages**: limited to 500 MiB per file.
+- **Npm packages**: limited to 500 MiB per file. Additionally, Azure Artifacts enforces a separate hard limit of 375 KB specifically for the *package.json* file.
 
 - **Maven packages**: limited to 500 MiB per file.
 

docs/boards/github/connect-on-premises-to-github.md

@@ -7,7 +7,7 @@ ms.topic: how-to
 ms.author: chcomley
 author: chcomley
 monikerRange: "<azure-devops"
-ms.date: 07/12/2023
+ms.date: 06/13/2025
 ---
 
 # Connect Azure DevOps Server to GitHub (on-premises)
@@ -16,13 +16,10 @@ ms.date: 07/12/2023
 
 <!--- Supports https://go.microsoft.com/fwlink/?linkid=2095009 --> 
 
-::: moniker range="azure-devops-2020"
 When you connect your Azure DevOps Server project to your GitHub repositories, you support linking between GitHub commits and pull requests to work items. You can use GitHub for software development while using Azure Boards to plan and track your work.  
 
 > [!NOTE]   
-> On-premises Azure DevOps Server 2020 supports integration with GitHub.com and GitHub Enterprise Server repositories. If you want to connect from Azure DevOps Services, see [Connect Azure Boards to GitHub](./connect-to-github.md?preserve-view=true&view=azure-devops).
-
-::: moniker-end
+> Azure DevOps Server supports integration with GitHub.com and GitHub Enterprise Server repositories. To connect from Azure DevOps Services, see [Connect Azure Boards to GitHub](./connect-to-github.md?preserve-view=true&view=azure-devops).
 
 ## Prerequisites 
 
@@ -34,77 +31,70 @@ When you connect your Azure DevOps Server project to your GitHub repositories, y
 
 ## Authentication options
 
-The following authentication options are supported. 
+The following authentication options are supported: 
 
-::: moniker range="azure-devops-2020"
-- [PAT](#server-github-ent-pat)
+- [GitHub PAT](#server-github-ent-pat)
 - [GitHub credentials](#server-github-ent-credentials)
 
 > [!NOTE] 
 > OAuth isn't supported for Azure DevOps Server 2020.  
-::: moniker-end
 
 <a id="github-oauth"></a>
 <a id="github-pat"></a>
 <a id="server-github-ent-oauth-register"></a>
 
 ## Connect Azure DevOps Server to GitHub Enterprise Server
 
-::: moniker range="azure-devops-2020"
 You can connect up to 250 GitHub repositories to an Azure Boards project. 
 
+::: moniker range="azure-devops-2020"
 > [!NOTE]   
-> Connection to more than 100 GitHub repositories requires Azure DevOps Server 2020.1 update or later version.  
-> Connection to GitHub.com repositories requires Azure DevOps Server 2020.1.1 Patch 2 or later version.
+> - Connection to more than 100 GitHub repositories requires Azure DevOps Server 2020.1 update or later version.  
+> - Connection to GitHub.com repositories requires Azure DevOps Server 2020.1.1 Patch 2 or later version.
 ::: moniker-end 
 
- 
-
 1. Open the web portal for your Azure DevOps Server.   
 
 2. Select the :::image type="icon" source="../../media/icons/project-icon.png" border="false"::: Azure DevOps logo to open  **Projects**, and then choose the Azure Boards project you want to configure to connect to your GitHub Enterprise repositories.
 
-::: moniker range="azure-devops-2020"
-
 3. Select **Project settings** > **GitHub connections**.   
 
-   :::image type="content" source="media/github-ent/open-project-settings-github-connections-2020-1.png" alt-text="Screenshot of open Project Settings>GitHub connections.":::  
+   :::image type="content" source="media/github-ent/open-project-settings-github-connections-2020-1.png" alt-text="Screenshot of open Project Settings, GitHub connections.":::  
 
-4.	If it's the first time making a connection from the project, choose the authentication method you want to use to make the connection: 
+4.	If it's your first time making a connection from the project, choose the authentication method you want to use to make the connection: 
 
-	- **Personal Access Token**, for details see [Connect using a Personal Access Token](#github-ent-pat). 
-	- **GitHub credentials**, see [Connect using GitHub credentials](#server-github-ent-credentials).
+	- **GitHub Personal Access Token**: For details, see [Connect using a GitHub PAT](#github-ent-pat). 
+	- **GitHub credentials**: For details, see [Connect using GitHub credentials](#server-github-ent-credentials).
 
 	:::image type="content" source="media/github-ent/connect-github-account-first-time.png" alt-text="Screenshot of first time connecting with GitHub credentials.":::
 
 	Otherwise, select :::image type="icon" source="../../media/icons/add-light-icon.png" border="false"::: **New connection**, and the select your authentication method from the **New Connection** dialog.
-::: moniker-end
 
 <a id="server-github-ent-pat"></a> 
 <a id="github-ent-pat"></a> 
 
-#### Connect with a Personal Access Token  
+## Connect Azure DevOps Server with a GitHub Personal Access Token  
 
-1.	To create a PAT, see [Creating a personal access token](https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line).
+1.	To create a GitHub PAT, see [Create a GitHub PAT](https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line).
 
 	> [!TIP]  
 	> When you create your GitHub PAT, make sure that you include these scopes: `repo, admin:repo_hook, read:user, user:email`. 
 
 1.	Enter the URL for your GitHub Enterprise server and the **Personal access token** credentials recognized by that server. And then select **Connect**.
 
-   :::image type="content" source="media/github-ent/ads-add-ghe-pat.png" alt-text="Screenshot of sign in with PAT.":::
+    :::image type="content" source="media/github-ent/ads-add-ghe-pat.png" alt-text="Screenshot of sign in with GitHub PAT.":::
 
 <a id="server-github-ent-credentials"></a>
 
-#### Connect with GitHub credentials   
+## Connect Azure DevOps Server with GitHub credentials   
 
 1.	Enter the URL for your GitHub Enterprise server and the administrator account credentials recognized by that server. And then choose **Connect**.
 
-   :::image type="content" source="media/github-ent/ads-add-ghe-user-name.png" alt-text="Screenshot of sign in with GitHub credentials."::: 
+    :::image type="content" source="media/github-ent/ads-add-ghe-user-name.png" alt-text="Screenshot of sign in with GitHub credentials."::: 
 
 2. The dialog lists all repositories for which you have GitHub administration rights. You can toggle between **Mine** and **All** to determine if others appear, and then check the ones that you want to add. Choose **Save** when you're done.
 
-   :::image type="content" source="media/github-ent/ads-add-ghe-repositories.png" alt-text="Screenshot of repositories to select to add."::: 
+    :::image type="content" source="media/github-ent/ads-add-ghe-repositories.png" alt-text="Screenshot of repositories to select to add."::: 
 
 3. To connect to a GitHub account or organization from Azure Boards for the first time, you also install the Azure Boards app for GitHub. Complete the integration by following the procedures outlined in [Confirm the connection](connect-to-github.md#confirm-connection). 
 
@@ -113,7 +103,7 @@ You can connect up to 250 GitHub repositories to an Azure Boards project.
 The Azure Boards-GitHub integration relies on various authentication protocols to support the connection. Changes to a user's permission scope or authentication credentials can cause revocation of the GitHub repositories connected to Azure Boards. 
 
 For an overview of the integration that the Azure Boards app for GitHub supports, see [Azure Boards-GitHub integration](index.md).  
-
+<!--
 #### Supported authentication options
 
 The following authentication options are supported based on the GitHub platform you want to connect to.  
@@ -170,33 +160,27 @@ The following authentication options are supported based on the GitHub platform
 :::row-end:::
  
 [!INCLUDE[temp](../includes/github-platform-support.md)]
-
-#### Resolve access issues
-
-::: moniker range=">= azure-devops-2020"
+-->
 
 When the Azure Boards connection to GitHub no longer has access, it shows an alert status in the user interface with a red-X. Hover over the alert and it indicates that the credentials are no longer valid. To correct the problem, remove the connection and recreate a new connection.
 
 :::image type="content" source="media/troubleshoot/failed-connection.png" alt-text="Screenshot of failed connection.":::
-
-::: moniker-end
 
-
 Consider the following resolutions:  
 
 - **If the connection is using OAuth**:
-  - The Azure Boards application had its access denied for one of the repositories.
+  - The Azure Boards application had access denied for one of the repositories.
   - GitHub might be unavailable/unreachable. This unavailability could be because of an outage in either service or an infrastructure/network issue on-premises. You can check service status from the following links:
       - [GitHub](https://status.github.com)  
       - [Azure DevOps](https://status.dev.azure.com/)
 
 	Delete and recreate the connection to the GitHub repository. This recreated connection causes GitHub to prompt to reauthorize Azure Boards.   
 
-- **If the connection is using a PAT:**
-  - The PAT  was revoked or the required permission scopes changed and are insufficient.
+- **If the connection is using a GitHub PAT:**
+  - The GitHub PAT was revoked or the required permission scopes changed and are insufficient.
   - The user perhaps lost administrative permissions on the GitHub repository.  
 
-	Recreate the PAT and ensure the scope for the token includes the required permissions: `repo, read:user, user:email, admin:repo_hook`. For more information, see [Best practices for using PATs](../../organizations/accounts/use-personal-access-tokens-to-authenticate.md#best-practices-for-using-pats).
+	Recreate the GitHub PAT and ensure the scope for the token includes the required permissions: `repo, read:user, user:email, admin:repo_hook`.
 
 <a id="update-wits"></a>
 

docs/boards/integrations/boards-teams.md

@@ -60,7 +60,7 @@ After the app installs, you see a welcome message in the Teams conversation pane
 
 :::image type="content" source="media/integrations-teams/welcome-message.png" alt-text="Screenshot of the Welcome message in the conversation pane.":::
 
-### Azure Pipelines app commands
+### Azure Boards app commands
 
 You can use the following `@azure boards` commands to interact with the Azure Boards app in your Teams channel.
 

docs/integrate/get-started/rest/samples.md

@@ -2,13 +2,14 @@
 title: REST API samples
 description: REST API samples for Azure DevOps, including personal access tokens (PATs).
 ms.assetid: 9E17A266-051F-403F-A285-7F21D9CC52F0
+ai-usage: ai-assisted
 ms.subservice: azure-devops-ecosystem
 ms.topic: conceptual
 ms.custom: devx-track-dotnet
 monikerRange: '<= azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 03/21/2025
+ms.date: 06/12/2025
 ---
 
 # REST API samples for Azure DevOps
@@ -17,26 +18,30 @@ ms.date: 03/21/2025
 
 Most samples in this article use personal access tokens (PATs). While PATs are a compact example for authentication, we don't recommend using them for production applications. There are many other authentication mechanisms available, including Microsoft Authentication Library, OAuth, and Session tokens. For more information to gauge which is best suited for your scenario, see [Authentication guidance](../authentication/authentication-guidance.md).
 
-For more information, see [Azure DevOps Services REST API Reference](/rest/api/azure/devops/?view=azure-devops-rest-7.2&preserve-view=true) and [Get started with REST APIs](../../how-to/call-rest-api.md).
+For more information, see [Azure DevOps REST API Reference](/rest/api/azure/devops/?view=azure-devops-rest-7.2&preserve-view=true) and [Get started with REST APIs](../../how-to/call-rest-api.md).
 
-## Personal access tokens
+## Authentication
 
-Authenticate with Azure DevOps when you use the REST APIs or .NET Libraries. 
+Authenticate with Azure DevOps when using the REST APIs or .NET Libraries by following these steps:
 
-Get started with these samples and [create a PAT](../../../organizations/accounts/use-personal-access-tokens-to-authenticate.md).
+- **Create a PAT:**  
+  Start with these samples and [create a personal access token (PAT)](../../../organizations/accounts/use-personal-access-tokens-to-authenticate.md).
 
-> [!NOTE]
-> We don't recommend using PATs. For more secure authentication mechanisms, see [Authentication guidance](../authentication/authentication-guidance.md).
+  [!INCLUDE [use-microsoft-entra-reduce-pats](../../../includes/use-microsoft-entra-reduce-pats.md)]
 
-To provide the PAT through an HTTP header, first convert it to a Base64 string. The following example shows how to convert to Base64 using C#. You can provide the resulting string as an HTTP header in the following format:
+- **Use Basic Authentication with a PAT:**  
+  1. Convert your PAT to a Base64-encoded string in the format `username:PAT` (the username can be empty).
+  2. Add the encoded string to the `Authorization` HTTP header.
 
-``
-Authorization: Basic BASE64USERNAME:PATSTRING
-``
+  **Example using Basic Authentication with curl:**
 
-## REST API
+   ```bash
+   curl -u :{yourPAT} https://dev.azure.com/{organization}/_apis/projects?api-version=7.2-preview.1
+   ```
 
-See the following example of getting a list of projects for your organization via REST API. 
+## GET request samples
+
+The following C# and curl requests return a JSON response containing the list of all projects in a specified organization:
 
 ```cs
 using System.Net.Http;
@@ -69,7 +74,40 @@ using (var client = new HttpClient())
         //var value = response.Content.ReadAsStringAsync().Result;
     }   
 }
+```
+
+
+```curl 
+-u username:PAT https://dev.azure.com/{organization}/_apis/projects?api-version=6.0
+```
+
+## POST request sample
+
+The following curl request creates a new work item of the "Task" type in a specified project:
+
+```curl 
+-u username:PAT -X POST -H "Content-Type: application/json" \
+-d '{"fields": {"System.Title": "New Work Item"}}' \
+https://dev.azure.com/{organization}/{project}/_apis/wit/workitems/$Task?api-version=6.0
+```
+
+## PUT request sample
+
+The following curl request updates an existing work item by changing its state to "In Progress":
+
+```curl
+ -u username:PAT -X PATCH -H "Content-Type: application/json-patch+json" \
+-d '[{"op": "add", "path": "/fields/System.State", "value": "In Progress"}]' \
+https://dev.azure.com/{organization}/{project}/_apis/wit/workitems/{id}?api-version=6.0
+```
+
+## DELETE request sample
+
+The following curl request deletes an existing work item from a specified project:
 
+```curl 
+-u username:PAT -X DELETE \
+https://dev.azure.com/{organization}/{project}/_apis/wit/workitems/{id}?api-version=6.0
 ```
 
 ## .NET Client Libraries
@@ -79,7 +117,7 @@ Here, we're using two of the .NET Client Libraries. Make sure you reference the
 - [Microsoft.TeamFoundationServer.Client](https://www.nuget.org/packages/Microsoft.TeamFoundationServer.Client/)
 - [Microsoft.Visual Studio.Services.Client](https://www.nuget.org/packages/Microsoft.VisualStudio.Services.Client/)
 
-See the following example of getting a list of projects for your organization via .NET Client Libraries.
+The following example gets a list of projects for your organization via .NET Client Libraries:
 
 ```cs
 using Microsoft.TeamFoundation.Core.WebApi;