[BULK UPDATE] DocuTune - Rebranding links

Author: alexbuckgit

README.md

@@ -4,6 +4,6 @@ For more information see the [Code of Conduct FAQ](https://opensource.microsoft.
 
 # Content repos
 
-> * For content contributions to `https://docs.microsoft.com/vsts`, work in the /docs folder.
-> * For content contributions to `docs.microsoft.com/vsts/release-notes`, work in the `/release-notes` folder.
+> * For content contributions to `https://learn.microsoft.com/vsts`, work in the /docs folder.
+> * For content contributions to `learn.microsoft.com/vsts/release-notes`, work in the `/release-notes` folder.
 > * Contact Ryan Thompson--`ryanth` (Microsoft alias) or `@thomps23` (GitHub alias) -- for details and training on content contribution or publishing.

docs/boards/github/index.md

@@ -22,7 +22,7 @@ By connecting Azure Boards with GitHub repositories, you enable linking between
 
 <br/> 
 
-> [!VIDEO https://docs.microsoft.com/shows/DevOps-Lab/Introducing-Azure-Boards-to-the-GitHub-Marketplace/player]
+> [!VIDEO https://learn.microsoft.com/shows/DevOps-Lab/Introducing-Azure-Boards-to-the-GitHub-Marketplace/player]
 
 > [!NOTE]   
 > Azure DevOps only supports integation with GitHub repositories or Azure Repos Git repositories. Integration with other Git repositories is not supported.  
@@ -161,4 +161,3 @@ Once you've configured the connection, you can complete the following tasks.
 - [Trigger an Azure Pipelines run from GitHub Actions](../../pipelines/ecosystems/github-actions.md)  
 
 
-

docs/cli/index.md

@@ -74,7 +74,7 @@ Commands:
     feedback         : Displays information on how to provide feedback to the Azure DevOps CLI team.
     invoke           : This command will invoke request for any DevOps area and resource. Please use
                        only json output as the response of this command is not fixed. Helpful docs -
-                       https://docs.microsoft.com/rest/api/azure/devops/.
+                       https://learn.microsoft.com/rest/api/azure/devops/.
     login            : Set the credential (PAT) to use for a particular organization.
     logout           : Clear the credential for all or a particular organization.
 ```

docs/pipelines/agents/agents.md

@@ -575,8 +575,8 @@ To trigger agent update - request body should be empty.
 > 
 ## Learn more
 
-For more information about agents, see the following modules from the [Build applications with Azure DevOps](/learn/paths/build-applications-with-azure-devops/) learning path.
-* [Choose a Microsoft-hosted or self-hosted build agent](/learn/modules/host-build-agent/2-choose-a-build-agent)
-* [Host your own build agent in Azure Pipelines](/learn/modules/host-build-agent/)
+For more information about agents, see the following modules from the [Build applications with Azure DevOps](/training/paths/build-applications-with-azure-devops/) learning path.
+* [Choose a Microsoft-hosted or self-hosted build agent](/training/modules/host-build-agent/2-choose-a-build-agent)
+* [Host your own build agent in Azure Pipelines](/training/modules/host-build-agent/)
 
 ::: moniker-end

docs/pipelines/ecosystems/android.md

@@ -63,7 +63,7 @@ You have a working YAML file (`azure-pipelines.yml`) in your repository that's r
 Gradle is a common build tool used for building Android projects. For more information about your options, see the [Gradle](../tasks/build/gradle.md) task.
 
 ```yaml
-# https://docs.microsoft.com/azure/devops/pipelines/ecosystems/android
+# https://learn.microsoft.com/azure/devops/pipelines/ecosystems/android
 pool:
   vmImage: 'macOS-latest'
 

docs/pipelines/ecosystems/ruby.md

@@ -53,7 +53,7 @@ For the exact versions of Ruby that are preinstalled, refer to [Microsoft-hosted
 Add the [Use Ruby Version](../tasks/tool/use-ruby-version.md) task to set the version of Ruby used in your pipeline. This snippet adds Ruby 2.4 or later to the path and sets subsequent pipeline tasks to use it.
 
 ```yaml
-# https://docs.microsoft.com/azure/devops/pipelines/ecosystems/ruby
+# https://learn.microsoft.com/azure/devops/pipelines/ecosystems/ruby
 pool:
   vmImage: 'ubuntu-latest' # other options: 'macOS-latest', 'windows-latest'
 

docs/pipelines/ecosystems/xamarin.md

@@ -71,7 +71,7 @@ For the exact versions of Xamarin that are preinstalled, refer to [Microsoft-hos
 Create a file named **azure-pipelines.yml** in the root of your repository. Then, add the following snippet to your `azure-pipelines.yml` file to select the appropriate agent pool:
 
 ```yaml
-# https://docs.microsoft.com/azure/devops/pipelines/ecosystems/xamarin
+# https://learn.microsoft.com/azure/devops/pipelines/ecosystems/xamarin
 pool:
   vmImage: 'macOS-10.15' # For Windows, use 'windows-2019'
 ```
@@ -175,7 +175,7 @@ You can build and test your Xamarin.Android app, Xamarin.iOS app, and related ap
 # Xamarin.Android and Xamarin.iOS
 # Build a Xamarin.Android and Xamarin.iOS app.
 # Add steps that test, sign, and distribute the app, save build artifacts, and more:
-# https://docs.microsoft.com/azure/devops/pipelines/ecosystems/xamarin
+# https://learn.microsoft.com/azure/devops/pipelines/ecosystems/xamarin
 
 jobs:
 

docs/pipelines/ecosystems/xcode.md

@@ -56,7 +56,7 @@ For the exact versions of Xcode that are preinstalled, refer to [Microsoft-hoste
 Create a file named **azure-pipelines.yml** in the root of your repository. Then, add the following snippet to your `azure-pipelines.yml` file to select the appropriate agent pool:
 
 ```yaml
-# https://docs.microsoft.com/azure/devops/pipelines/ecosystems/xcode
+# https://learn.microsoft.com/azure/devops/pipelines/ecosystems/xcode
 pool:
   vmImage: 'macOS-latest'
 ```

docs/pipelines/get-started-multiplatform.md

@@ -41,7 +41,7 @@ You're going to add jobs that run on three platforms.
 
 ```yaml
 # Build NodeJS Express app using Azure Pipelines
-# https://docs.microsoft.com/azure/devops/pipelines/ecosystems/javascript?view=azure-devops
+# https://learn.microsoft.com/azure/devops/pipelines/ecosystems/javascript?view=azure-devops
 strategy:
   matrix:
     linux:

docs/pipelines/overview-azure.md

@@ -54,11 +54,11 @@ If you're just getting started, we recommend you review and get started with the
       [DevOps solutions on Azure](https://azure.microsoft.com/solutions/devops/#products)
    :::column-end::: 
    :::column span="3":::
-      Use end-to-end solutions on Azure to implement DevOps practices throughout application planning, development, delivery, and operations. Apply the right combination of DevOps technologies, culture, and processes to enable continual software delivery and better value for customers. Get started with the following learn modules: 
-      - [Deploy applications with Azure DevOps](/learn/paths/deploy-applications-with-azure-devops/)  
-      - [Build applications with Azure DevOps](/learn/paths/build-applications-with-azure-devops/)  
-      - [Deploy and maintain cloud-native apps with GitHub actions and Azure Pipelines](/learn/modules/cna-deploy-maintain/)
-      - [Load test Azure web apps by using Azure DevOps](/learn/modules/load-test-web-app-azure-devops/)
+      Use end-to-end solutions on Azure to implement DevOps practices throughout application planning, development, delivery, and operations. Apply the right combination of DevOps technologies, culture, and processes to enable continual software delivery and better value for customers. Get started with the following Learn modules: 
+      - [Deploy applications with Azure DevOps](/training/paths/deploy-applications-with-azure-devops/)  
+      - [Build applications with Azure DevOps](/training/paths/build-applications-with-azure-devops/)  
+      - [Deploy and maintain cloud-native apps with GitHub actions and Azure Pipelines](/training/modules/cna-deploy-maintain/)
+      - [Load test Azure web apps by using Azure DevOps](/training/modules/load-test-web-app-azure-devops/)
    :::column-end:::
 :::row-end:::
 ---

docs/pipelines/release/azure-key-vault.md

@@ -233,7 +233,7 @@ In order to access our Azure Key Vault, we must first set up a service principal
 1. The text file should contain our secret: *mysecretpassword*.
 
 > [!WARNING]
-> This tutorial is for educational purposes only. For security best practices and how to safely work with secrets, see [Manage secrets in your server apps with Azure Key Vault](/learn/modules/manage-secrets-with-azure-key-vault/).
+> This tutorial is for educational purposes only. For security best practices and how to safely work with secrets, see [Manage secrets in your server apps with Azure Key Vault](/training/modules/manage-secrets-with-azure-key-vault/).
 
 ## Clean up resources
 

docs/pipelines/release/index.md

@@ -33,7 +33,7 @@ semi-automated processes with **approvals** and **on-demand deployments**.
 
 See [Releases in Azure Pipelines](releases.md) to understand releases and deployments and watch the following video to see release pipelines in action.
 
-  > [!VIDEO https://docs.microsoft.com/Events/Microsoft-Azure/Azure-DevOps-Launch-2018/A101/player]
+  > [!VIDEO https://learn.microsoft.com/Events/Microsoft-Azure/Azure-DevOps-Launch-2018/A101/player]
 
 <a name="howrmworks"></a>
 

docs/pipelines/tasks/deploy/app-center-distribute.md

@@ -66,7 +66,7 @@ This example pipeline builds an Android app, runs tests, and publishes the app u
 # Android
 # Build your Android project with Gradle.
 # Add steps that test, sign, and distribute the APK, save build artifacts, and more:
-# https://docs.microsoft.com/azure/devops/pipelines/ecosystems/android
+# https://learn.microsoft.com/azure/devops/pipelines/ecosystems/android
 
 pool:
   vmImage: 'macOS-latest'

docs/report/analytics/analytics-permissions-prerequisites.md

@@ -132,8 +132,8 @@ In addition, consider the following actions:
 
 To report on pipelines and tests results, make sure you add test tasks to the pipeline definition. To learn more, see [Build and release tasks-Test](../../pipelines/tasks/index.md#test). 
 
-If you're just getting started, consider reviewing this learn module, 
-[Run quality tests in your build pipeline by using Azure Pipelines](/learn/modules/run-quality-tests-build-pipeline).
+If you're just getting started, consider reviewing this Learn module, 
+[Run quality tests in your build pipeline by using Azure Pipelines](/training/modules/run-quality-tests-build-pipeline).
 
 ::: moniker-end
 
@@ -147,5 +147,3 @@ If you're just getting started, consider reviewing this learn module,
 
 
 
-
-

docs/report/sql-reports/migration-guide.md

@@ -87,9 +87,9 @@ In addition, users can set permissions for individual shared Analytics views the
 - [Power BI Desktop download page](/power-bi/desktop-what-is-desktop)
 
 **Learn resources**:  
-- [Run quality tests in your build pipeline by using Azure Pipelines](/learn/modules/run-quality-tests-build-pipeline)
-- [Run functional tests in Azure DevOps](/learn/modules/run-functional-tests-azure-pipelines) 
+- [Run quality tests in your build pipeline by using Azure Pipelines](/training/modules/run-quality-tests-build-pipeline)
+- [Run functional tests in Azure DevOps](/training/modules/run-functional-tests-azure-pipelines) 
 
 ## Next steps
 > [!div class="nextstepaction"]
-> [Get Analytics insights comparable to those provided by SQL Reporting Services reports](analytics-insights-comparable-sql-reports.md)
+> [Get Analytics insights comparable to those provided by SQL Reporting Services reports](analytics-insights-comparable-sql-reports.md)

docs/user-guide/work-team-explorer.md

@@ -19,7 +19,7 @@ ms.date: 03/03/2022
 You use Team Explorer to coordinate your code efforts with other team members to develop a software project. In addition, you can manage work and that is assigned to you, your team, or your projects. Team Explorer is a plug-in that installs with Visual Studio and Team Explorer Everywhere is a plug-in that installs with Eclipse. Developers can effectively collaborate using Team Explorer connected to projects hosted on Azure DevOps Services or an on-premises Azure DevOps Server (previously named Team Foundation Server (TFS)).
 
 > [!TIP]
-> You can install the latest version of Visual Studio clients from the [Visual Studio downloads page](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). 
+> You can install the latest version of Visual Studio clients from the [Visual Studio downloads page](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=learn.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017). 
 > 
 > Additional options for connecting to Azure DevOps Services or TFS include:  
 > - [Team Explorer Everywhere](/previous-versions/azure/devops/all/java/download-eclipse-plug-in)

release-notes/2022/includes/pipelines/sprint-209-update.md

@@ -15,7 +15,7 @@ Previously, the Pipelines UI used to show the last commit message when displayin
 
 This message can be confusing, for example, when your YAML pipeline's code lives in a repository different from the one that holds the code it's building. We heard your feedback from the [Developer Community](https://developercommunity.visualstudio.com/content/idea/1030999/enabledisable-appending-the-to-the-title-of-every.html) asking us for a way to enable/disable appending the latest commit message to the title of every pipeline run. 
 
-With this update, we've added a new YAML property, named [`appendCommitMessageToRunName`](https://docs.microsoft.com/azure/devops/pipelines/yaml-schema/pipeline?view=azure-pipelines#pipeline-stages), that lets you do exactly that. By default, the property is set to `true`. When you set it to `false`, the pipeline run will only display the [`BuildNumber`](https://docs.microsoft.com/azure/devops/pipelines/process/run-number?view=azure-devops&tabs=yaml).
+With this update, we've added a new YAML property, named [`appendCommitMessageToRunName`](https://learn.microsoft.com/azure/devops/pipelines/yaml-schema/pipeline?view=azure-pipelines#pipeline-stages), that lets you do exactly that. By default, the property is set to `true`. When you set it to `false`, the pipeline run will only display the [`BuildNumber`](https://learn.microsoft.com/azure/devops/pipelines/process/run-number?view=azure-devops&tabs=yaml).
 
 > [!div class="mx-imgBorder"]
 > ![Example of pipeline run with build number](../../media/209-pipelines-02.png)
@@ -25,7 +25,7 @@ With this update, we've added a new YAML property, named [`appendCommitMessageTo
 
 ### Consumed resources and template parameters in Pipelines Runs Rest API
 
-The extended [Pipelines Runs REST API](https://docs.microsoft.com/rest/api/azure/devops/pipelines/runs/get?view=azure-devops-rest-7.1) now returns more types of artifacts used by a pipeline run and the parameters used to trigger that run. We enhanced the API to return the `container` and `pipeline` resources and the template parameters used in a pipeline run. You can now, for example, write compliance checks that evaluate the repositories, containers, and other pipeline runs used by a pipeline.
+The extended [Pipelines Runs REST API](https://learn.microsoft.com/rest/api/azure/devops/pipelines/runs/get?view=azure-devops-rest-7.1) now returns more types of artifacts used by a pipeline run and the parameters used to trigger that run. We enhanced the API to return the `container` and `pipeline` resources and the template parameters used in a pipeline run. You can now, for example, write compliance checks that evaluate the repositories, containers, and other pipeline runs used by a pipeline.
 
 Here is an example of the new response body.
 
@@ -104,7 +104,7 @@ Here is an example of the new response body.
 
 ### Add support for string split function in YAML template expressions
 
-YAML pipelines provide you convenient ways to reduce code duplication, such as [looping through `each` value of a list](https://docs.microsoft.com/azure/devops/pipelines/process/expressions?view=azure-devops#each-keyword) or property of an object. 
+YAML pipelines provide you convenient ways to reduce code duplication, such as [looping through `each` value of a list](https://learn.microsoft.com/azure/devops/pipelines/process/expressions?view=azure-devops#each-keyword) or property of an object. 
 
 Sometimes, the set of items to iterate through is represented as a string. For example, when the list of environments to deploy to is defined by the string `integration1, integration2`.
 
@@ -126,7 +126,7 @@ jobs:
 
 ### Do not sync tags when fetching a Git repository
 
-The [checkout task](https://docs.microsoft.com/azure/devops/pipelines/yaml-schema/steps-checkout?view=azure-pipelines) uses `--tags` option in fetching the contents of a Git repository. This causes the server to fetch all tags as well as all objects that are pointed to by those tags. This increases the time to run the task in a pipeline - particularly if you have a large repository with a number of tags. Furthermore, the checkout task syncs tags even when you enable the shallow fetch option, thereby possibly defeating its purpose. To reduce the amount of data fetched or pulled from a Git repository, we have now added a new option to the task to control the behavior of syncing tags. This option is available both in classic and YAML pipelines. 
+The [checkout task](https://learn.microsoft.com/azure/devops/pipelines/yaml-schema/steps-checkout?view=azure-pipelines) uses `--tags` option in fetching the contents of a Git repository. This causes the server to fetch all tags as well as all objects that are pointed to by those tags. This increases the time to run the task in a pipeline - particularly if you have a large repository with a number of tags. Furthermore, the checkout task syncs tags even when you enable the shallow fetch option, thereby possibly defeating its purpose. To reduce the amount of data fetched or pulled from a Git repository, we have now added a new option to the task to control the behavior of syncing tags. This option is available both in classic and YAML pipelines. 
 
 #### [YAML](#tab/yaml/)
 
@@ -177,4 +177,4 @@ To help you better identify which pipelines are using the ubuntu-18.04 image, we
 * November 4, 22:00 UTC - November 5, 04:00 UTC
 * November 11, 04:00 UTC - November 11, 10:00 UTC
 * November 18, 06:00 UTC - November 18, 12:00 UTC
-* November 25, 08:00 UTC - November 25, 14:00 UTC
+* November 25, 08:00 UTC - November 25, 14:00 UTC