refresh, remove/redirect

Author: chcomley

.openpublishing.redirection.json

@@ -439,6 +439,11 @@
       "source_path": "docs/user-guide/service-limits.md",
       "redirect_url": "/azure/devops/integrate/concepts/rate-limits",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/integrate/concepts/cross-origin-resource-sharing.md",
+      "redirect_url": "/azure/devops/integrate/how-to/call-rest-api?view=azure-devops#cross-origin-resource-sharing-cors",
+      "redirect_document_id": false
     }
   ]
 }

docs/integrate/concepts/cross-origin-resource-sharing.md

@@ -8,7 +8,7 @@ ms.topic: conceptual
 monikerRange: '<= azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 11/09/2023
+ms.date: 11/10/2023
 ---
 
 # .NET client libraries
@@ -199,4 +199,7 @@ For version 16.143.1 of our NuGet packages, we support NetStandard 2.0. These pa
 
 ### Microsoft.TeamFoundationServer.ExtendedClient package doesn't have NetStandard support
 
-The [Microsoft.TeamFoundationServer.ExtendedClient](https://www.nuget.org/packages/Microsoft.TeamFoundationServer.ExtendedClient) currently doesn't support a NetStandard compliant version. This package includes our older SOAP object model, which we replaced by our newer REST object model.  At this point, we're no longer investing in the older SOAP object model, and have no plans to create a NetStandard version of it.
+The [Microsoft.TeamFoundationServer.ExtendedClient](https://www.nuget.org/packages/Microsoft.TeamFoundationServer.ExtendedClient) doesn't support a NetStandard compliant version. 
+
+> [!IMPORTANT]
+> This package includes our older SOAP object model, which we replaced by our newer REST object model. We're no longer investing in the older SOAP object model, and have no plans to create a NetStandard version of it.

docs/integrate/concepts/dotnet-client-libraries.md

@@ -1,7 +1,7 @@
 ---
-title: Integration best practices with REST APIs
+title: Integration best practices
 titleSuffix: Azure DevOps Services 
-description: Best practices for integrating Azure DevOps Services with REST APIs.
+description: Best practices for integrating Azure DevOps Services.
 ms.subservice: azure-devops-ecosystem
 ms.assetid: 9E1F3FD7-E1C1-44D9-B265-5368B3BD621E
 ms.custom: content-health, FY22Q3, freshness
@@ -13,7 +13,7 @@ ms.date: 11/09/2023
 
 <!--- Supports FWLINK:  https://go.microsoft.com/fwlink/?LinkId=692096   --> 
 
-# Best integration practices with REST APIs
+# Best integration practices
 
 [!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
 
@@ -29,7 +29,7 @@ Don't add work items into Azure DevOps for the sake of having them all in one pl
 
 ## Batch your changes
 
-Doing single operations is slow and expensive, which is the leading cause for performance issues and rate limiting. Batch your changes into a single call. For more informaiton, see our [batch documentation](/previous-versions/azure/devops/integrate/previous-apis/wit/batch) and [sample code](/previous-versions/azure/devops/integrate/previous-apis/wit/samples).
+Doing single operations is slow and expensive, which is the leading cause for performance issues and rate limiting. Batch your changes into a single call. For more information, see our [batch documentation](/previous-versions/azure/devops/integrate/previous-apis/wit/batch) and [sample code](/previous-versions/azure/devops/integrate/previous-apis/wit/samples).
 
 ## Limit your revisions
 

docs/integrate/concepts/integration-bestpractices.md

@@ -7,16 +7,17 @@ ms.topic: conceptual
 monikerRange: 'azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 03/25/2022
+ms.date: 11/10/2023
 ---
 
-# Service hooks in Azure DevOps
+# Service hooks in Azure DevOps Services REST APIs
 
 [!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
 
-When you use the [Subscriptions](../../service-hooks/overview.md#create-a-subscription) REST APIs, you can programmatically create a subscription that performs an action on an external (consumer) service when a specific event occurs in a project. For example, you can create a subscription to notify your service when a build fails.
+When you use the [Subscription](../../service-hooks/overview.md#create-a-subscription) REST APIs, you can programmatically create a subscription that performs an action on an external (consumer) service when a specific event occurs in a project. For example, you can create a subscription to notify your service when a build fails.
 
 Supported events:
+
 - Build completed
 - Code pushed (for Git projects)
 - Pull request create or updated (for Git projects)

docs/integrate/concepts/service-hooks.md

@@ -7,26 +7,33 @@ ms.assetid: 6dc7f977-4b62-4bd6-b77a-1c6cade1ffa8
 monikerRange: '<= azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 10/20/2020
+ms.date: 11/10/2023
 ---
 
-# Use the Cross-platform CLI for Azure DevOps using personal access tokens (PATs)
+# Use the Cross-platform CLI for Azure DevOps using personal access tokens
 
 [!INCLUDE [version-lt-eq-azure-devops](../../../includes/version-lt-eq-azure-devops.md)]
 
-- You can download the latest version of **Node.js source code**, from the [Node.js source code downloads page](https://nodejs.org/en/download/)
+Use personal access tokens (PATs) with the cross-platform CLI for Azure DevOps.
+
+> [!IMPORTANT]
+> We don't recommend using basic authentication. For Azure DevOps Services, see [Sign in with a PAT](../../../cli/log-in-via-pat.md).
+
+## Prerequisites
+
+- Download the latest version of **Node.js source code**, from the [Node.js source code downloads page](https://nodejs.org/en/download/)
 - Install the **Cross-platform CLI for Azure DevOps**
   - Install **tfx-cli** using `npm`, a component of Node.js by running:
 
    ```no-highlight
     npm i -g tfx-cli 
    ```
 
-    For more information about **tfx-cli**, see the [Node CLI for Azure DevOps on GitHub](https://github.com/Microsoft/tfs-cli).
+   For more information about **tfx-cli**, see the [Node CLI for Azure DevOps on GitHub](https://github.com/Microsoft/tfs-cli).
 
 ## Personal access token
 
-Start by creating a personal access token and paste it into the sign in command.
+Create a personal access token and paste it into the sign-in command.
 
 ```
 ~$ tfx login
@@ -37,23 +44,22 @@ Copyright Microsoft Corporation
 Logged in successfully
 ```
 
-Examples of valid URLs are:
+See the following examples of valid URLs:
 
 - `https://marketplace.visualstudio.com`
 - `https://youraccount.visualstudio.com/DefaultCollection`
 
 ## Configure for Basic authentication
 
-> [!IMPORTANT]
-> Basic authentication is not recommended.  Turning on IIS basic authentication causes various issues, and you should 
-> use [personal access tokens (PATs)](../../../organizations/accounts/use-personal-access-tokens-to-authenticate.md) instead.  For example, if you turn on IIS basic authentication, GIT command line stops working.
+> [!WARNING]
+> We don't recommend basic authentication. Turning on IIS basic authentication causes various issues, and you should use [personal access tokens (PATs)](../../../organizations/accounts/use-personal-access-tokens-to-authenticate.md) instead.  For example, if you turn on IIS basic authentication, GIT command line stops working.
 
 Follow these steps to enable basic auth for your Azure DevOps instance:
 
 > [!WARNING]
-> Basic authentication sends usernames and passwords in plaintext. You should consider [configuring Azure DevOps Server to use SSL](/azure/devops/server/admin/setup-secure-sockets-layer) in order to enable secure communication when using basic auth.
+> Basic authentication sends usernames and passwords in plaintext. Consider [configuring Azure DevOps Server to use SSL](/azure/devops/server/admin/setup-secure-sockets-layer) to enable secure communication when using basic auth.
 
-1. Install the `Basic Authentication` feature for IIS in Server Manager
+1. Install the `Basic Authentication` feature for IIS in Server Manager.
 
    > [!div class="mx-imgBorder"]  
    > ![Screenshot of configure basic authentication feature.](./media/configureBasicAuthFeature.png)
@@ -67,7 +73,7 @@ Follow these steps to enable basic auth for your Azure DevOps instance:
 
 ## tfx sign in with Basic authentication
 
-Now you can start to use `tfx` against your server. You'll want to sign in before issuing commands.
+Now you can start to use `tfx` against your server. Sign in before you issue commands.
 
 1. Enter the following command:
 
@@ -76,7 +82,7 @@ Now you can start to use `tfx` against your server. You'll want to sign in befor
    ```
 
 2. Add your service url.
-3. Add your username. Use `domain\user` (e.g. fabrikam\peter). If you are working on a workgroup machine, use `machinename\user`.
+3. Add your username. Use `domain\user` (for example, fabrikam\peter). If you're working on a workgroup machine, use `machinename\user`.
 4. Add your password. Enter the password for the username that you previously entered.
 
 **You can now use any other tfx command.**

docs/integrate/get-started/auth/tfs-basic-auth.md

@@ -8,23 +8,25 @@ ms.topic: conceptual
 monikerRange: '<= azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 03/05/2021
+ms.date: 11/10/2023
 ---
 
 # Choose the right authentication mechanism
 
 [!INCLUDE [version-lt-eq-azure-devops](../../../includes/version-lt-eq-azure-devops.md)]
 
-For applications that interface with Azure DevOps Services, you must authenticate to gain access to resources like REST APIs. We understand that Azure DevOps Services offers many different ways to authenticate your application. This article provides guidance to help you choose the right authentication for your application. The following table outlines the recommended authentication mechanism for different application types. See the following basic descriptions, examples, and code samples to get you started.
+For applications that interface with Azure DevOps Services, you must authenticate to gain access to resources like REST APIs. This article provides guidance to help you choose the right authentication mechanism for your application. 
+
+The following table outlines the recommended authentication mechanism for various application types. See the following basic descriptions, examples, and code samples to get you started.
 
 | Type of application | Description | Example |Authentication mechanism | Code samples |
 |---------------------|-------------|---------|-------------------------|--------|
- Interactive client-side (REST) | Client application, that allows user interaction, calling [Azure DevOps Services REST APIs](/rest/api/azure/devops) | Console application enumerating projects in an organization | [Microsoft Authentication Library (MSAL)](/azure/active-directory/develop/msal-overview) | [sample](https://github.com/microsoft/azure-devops-auth-samples/tree/master/ManagedClientConsoleAppSample) |
-| Interactive client-side (Client library) | Client application, that allows user interaction, calling Azure DevOps Services Client libraries | Console application enumerating bugs assigned to the current user |  [Client libraries](../../concepts/dotnet-client-libraries.md) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/ClientLibraryConsoleAppSample) |
+ Interactive client-side (REST) | Client application that allows user interaction calling [Azure DevOps Services REST APIs](/rest/api/azure/devops) | Console application enumerating projects in an organization | [Microsoft Authentication Library (MSAL)](/azure/active-directory/develop/msal-overview) | [sample](https://github.com/microsoft/azure-devops-auth-samples/tree/master/ManagedClientConsoleAppSample) |
+| Interactive client-side (Client library) | Client application that allows user interaction calling Azure DevOps Services Client libraries | Console application enumerating bugs assigned to the current user |  [Client libraries](../../concepts/dotnet-client-libraries.md) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/ClientLibraryConsoleAppSample) |
 | Interactive JavaScript | GUI-based JavaScript application | AngularJS single page app displaying project information for a user | [Microsoft Authentication Library for JavaScript (MSAL JS)](https://github.com/AzureAD/microsoft-authentication-library-for-js#microsoft-authentication-library-for-javascript-msaljs) | [sample](https://github.com/microsoft/azure-devops-auth-samples/tree/master/JavascriptWebAppSample) |
 | Personal access token (PAT) | Bearer token to access your own resources  | Use your PAT in place of your password. | [PATs](../../../organizations/accounts/use-personal-access-tokens-to-authenticate.md)
 | Non-interactive client-side | Headless text only client-side application | Console app displaying all bugs assigned to a user | [Device Profile](/azure/active-directory/develop/v2-oauth2-device-code) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/DeviceProfileSample) |
-| Interactive client-side app targeting Azure DevOps | Client application, that allows user interaction, authenticates Azure DevOps users | Console application allowing Azure DevOps users to see assigned bugs |  [Client Library (Interactive and Windows authentication)](../client-libraries/samples.md#authenticating) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/DualSupportClientSample) |
+| Interactive client-side app targeting Azure DevOps | Client application that allows user interaction authenticates Azure DevOps users | Console application allowing Azure DevOps users to see assigned bugs |  [Client Library (Interactive and Windows authentication)](../client-libraries/samples.md#authenticating) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/DualSupportClientSample) |
 | Interactive web | GUI-based web application that requires user consent | Custom Web dashboard displaying build summaries |[Azure DevOps OAuth](./oauth.md) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/OAuthWebSample) |
 | Service Principals or Managed Identities | Application with access to organization's Azure DevOps resources | Azure function to create work items |[Service principals and managed identities](./service-principal-managed-identity.md)| [sample](https://github.com/microsoft/azure-devops-auth-samples/tree/master/ServicePrincipalsSamples) |
 | Azure DevOps Server application | Azure DevOps Server app using the Client OM library | Azure DevOps Server extension displaying team bug dashboards | [Client Libraries](../../concepts/dotnet-client-libraries.md) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/ClientLibraryConsoleAppSample) |
@@ -35,12 +37,12 @@ To learn more about how we store your credentials, see [Credential storage for A
 
 #### Enabling IIS Basic Authentication invalidates using PATs for Azure DevOps Server
 
-Learn more about [using IIS Basic Authentication with Azure DevOps on-premises](iis-basic-auth.md).
+For more information, see [Using IIS Basic Authentication with Azure DevOps on-premises](iis-basic-auth.md).
 
 ## Frequently asked questions (FAQs)
 
 #### Q: Why can't one of my service accounts access the Azure DevOps REST API?
-A: Your service account may not have "materialized." Since signing in isn't possible with a service account that doesn't have interactive signing in permissions, check out [this work-around](https://github.com/microsoft/azure-devops-dotnet-samples/blob/main/ClientLibrary/Quickstarts/dotnet/MaterializeUserQuickStarts/Program.cs).
+A: Your service account might not have "materialized." Since signing in isn't possible with a service account that doesn't have interactive signing in permissions, check out [this work-around](https://github.com/microsoft/azure-devops-dotnet-samples/blob/main/ClientLibrary/Quickstarts/dotnet/MaterializeUserQuickStarts/Program.cs).
 
 #### Q: I'm making an interactive client-side application. Should I use [Azure DevOps Services Client Libraries](../../concepts/dotnet-client-libraries.md) or [Azure DevOps Services REST APIs](/rest/api/azure/devops)?
 A: We recommend using Azure DevOps Services Client Libraries over REST APIs when accessing Azure DevOps Services resources. They're simpler and more easily maintained when version changes to our REST endpoints occur. If functionality is missing from the client libraries, [MSAL](/azure/active-directory/develop/msal-overview) is the best authentication mechanism to use with our REST APIs.

docs/integrate/get-started/authentication/authentication-guidance.md

@@ -5,7 +5,7 @@ description: How to use the Azure DevOps OAuth 2.0 implementation for existing w
 monikerRange: 'azure-devops'
 ms.author: chcomley
 author: chcomley
-ms.date: 10/17/2023
+ms.date: 11/10/2023
 ---
 
 # Use Azure DevOps OAuth 2.0 to create a web app
@@ -45,7 +45,7 @@ The settings for each app that you register are available from your profile `htt
 
 ### 2. Authorize your app
 
-1. If your user hasn't yet authorized your app to access their organization, call the authorization URL. It calls you back with an authorization code, if the user approves the authorization.
+1. If your user didn't authorize your app to access their organization, call the authorization URL. It calls you back with an authorization code, if the user approves the authorization.
 
 ```no-highlight
 https://app.vssps.visualstudio.com/oauth2/authorize
@@ -238,7 +238,7 @@ A: Check that you set the content type to application/x-www-form-urlencoded in y
 
 ### Q: I get an HTTP 401 error when I use an OAuth-based access token, but a PAT with the same scope works fine. Why?
 
-A: Verify that **Third-party application access via OAuth** hasn't been disabled by your organization's admin at `https://dev.azure.com/{your-org-name}/_settings/organizationPolicy`.
+A: Verify that **Third-party application access via OAuth** wasn't disabled by your organization's admin at `https://dev.azure.com/{your-org-name}/_settings/organizationPolicy`.
 In this scenario, the flow to authorize an app and generate an access token works, but all REST APIs return only an error, such as `TF400813: The user "<GUID>" is not authorized to access this resource.`
 
 ### Q: Can I use OAuth with the SOAP endpoints and REST APIs?