Updates all links to original yaml-schema.md

Author: Steve Danielson

docs/extend/develop/add-build-task.md

@@ -540,7 +540,7 @@ Create a new Visual Studio Marketplace service connection and grant access permi
 
 ![Screenshot that shows the Visual Studio Marketplace new service connection pane.](media/new-vs-marketplace-service-connection.png)
 
-Use the following example to create a new pipeline with YAML. Learn more about how to [Create your first pipeline](../../pipelines/create-first-pipeline.md?tabs=javascript%2Cyaml%2Cbrowser%2Ctfs-2018-2) and [YAML schema](../../pipelines/yaml-schema.md?tabs=schema%2Cparameter-schema).
+Use the following example to create a new pipeline with YAML. Learn more about how to [Create your first pipeline](../../pipelines/create-first-pipeline.md?tabs=javascript%2Cyaml%2Cbrowser%2Ctfs-2018-2) and [YAML schema](/azure/devops/pipelines/yaml-schema/).
 
 ```yaml
 trigger: 

docs/get-started/index.yml

@@ -95,7 +95,7 @@ landingContent:
       - linkListType: reference
         links:
           - text: YAML Schema
-            url: ../pipelines/yaml-schema.md
+            url: /azure/devops/pipelines/yaml-schema/
   - title: Set your preferences
     linkLists:
       - linkListType: quickstart

docs/index.yml

@@ -96,7 +96,7 @@ productDirectory:
           text: What is Azure Pipelines?
         - url: ./pipelines/create-first-pipeline.md
           text: Create your first pipeline
-        - url: ./pipelines/yaml-schema.md
+        - url: /azure/devops/pipelines/yaml-schema/
           text: YAML schema  
         - url: ./pipelines/process/variables.md
           text: Define variables

docs/pipelines/agents/pools-queues.md

@@ -114,7 +114,7 @@ To use a private pool with no demands:
 pool: MyPool
 ```
 
-For more information, see the [YAML schema](../yaml-schema.md) for [pools](../yaml-schema.md#pool).
+For more information, see the [YAML schema](/azure/devops/pipelines/yaml-schema) for [pools](/azure/devops/pipelines/yaml-schema/pool).
 
 # [Classic](#tab/classic)
 

docs/pipelines/artifacts/pypi.md

@@ -24,7 +24,7 @@ With Azure Pipelines, you can publish your Python packages to Artifacts feeds, p
 - script: 'pip install twine'
 ```
 
-See [script shortcut](../yaml-schema.md#script) for more details.
+See [script shortcut](/azure/devops/pipelines/yaml-schema/steps-script) for more details.
 
 #### [Classic](#tab/classic/)
 

docs/pipelines/build/ci-build-git.md

@@ -37,7 +37,7 @@ A common workflow with Git is to create temporary branches from your main branch
 #### [YAML](#tab/yaml/)
 ::: moniker range=">=azure-devops-2020"
 
-Unless you specify a [trigger](../yaml-schema.md#push-trigger) in your YAML file, a change in any of the branches will trigger a build. Add the following snippet to your YAML file in the `main` branch. This will cause any changes to `main` and `feature/*` branches to be automatically built.
+Unless you specify a [trigger](/azure/devops/pipelines/yaml-schema/trigger) in your YAML file, a change in any of the branches will trigger a build. Add the following snippet to your YAML file in the `main` branch. This will cause any changes to `main` and `feature/*` branches to be automatically built.
 
 ```yaml
 trigger:

docs/pipelines/build/includes/variables-hosted.md

@@ -485,7 +485,7 @@ Note: This variable yields a value that is invalid for build use in a build numb
 <br/><br/>
 This variable is agent-scoped, and can be used as an environment variable in a script and as a parameter in a build task, but not as part of the build number or as a version control tag. 
 <br /><br />
-If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="../../yaml-schema.md#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
+If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="/azure/devops/pipelines/yaml-schema/resources-pipelines-pipeline#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
 </td>
 
 <td>No</td>
@@ -497,7 +497,7 @@ If you are triggering a YAML pipeline using <code>resources</code>, you should u
 <br/><br/>
 This variable is agent-scoped, and can be used as an environment variable in a script and as a parameter in a build task, but not as part of the build number or as a version control tag. 
 <br /><br />
-If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="../../yaml-schema.md#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
+If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="/azure/devops/pipelines/yaml-schema/resources-pipelines-pipeline#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
 </td>
 <td>No</td>
 </tr>
@@ -508,7 +508,7 @@ If you are triggering a YAML pipeline using <code>resources</code>, you should u
 <br/><br/>
 This variable is agent-scoped, and can be used as an environment variable in a script and as a parameter in a build task, but not as part of the build number or as a version control tag. 
 <br /><br />
-If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="../../yaml-schema.md#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
+If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="/azure/devops/pipelines/yaml-schema/resources-pipelines-pipeline#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
 </td>
 <td>No</td>
 </tr>
@@ -519,7 +519,7 @@ If you are triggering a YAML pipeline using <code>resources</code>, you should u
 <br/><br/>
 This variable is agent-scoped, and can be used as an environment variable in a script and as a parameter in a build task, but not as part of the build number or as a version control tag.
 <br /><br />
-If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="../../yaml-schema.md#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
+If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="/azure/devops/pipelines/yaml-schema/resources-pipelines-pipeline#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
 </td>
 <td>No</td>
 </tr>
@@ -530,7 +530,7 @@ If you are triggering a YAML pipeline using <code>resources</code>, you should u
 <br/><br/>
 This variable is agent-scoped, and can be used as an environment variable in a script and as a parameter in a build task, but not as part of the build number or as a version control tag. 
 <br /><br />
-If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="../../yaml-schema.md#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
+If you are triggering a YAML pipeline using <code>resources</code>, you should use the <a href="/azure/devops/pipelines/yaml-schema/resources-pipelines-pipeline#the-pipeline-resource-metadata-as-predefined-variables">resources variables</a> instead. 
 </td>
 <td>No</td>
 </tr>

docs/pipelines/customize-pipeline.md

@@ -312,4 +312,4 @@ Or, to grow your CI pipeline to a CI/CD pipeline, include a [deployment job](../
 
 To learn more about the topics in this guide see [Jobs](../pipelines/process/phases.md), [Tasks](../pipelines/process/tasks.md), [Catalog of Tasks](../pipelines/tasks/index.md), [Variables](../pipelines/process/variables.md), [Triggers](../pipelines/build/triggers.md), or [Troubleshooting](../pipelines/troubleshooting/troubleshooting.md).
 
-To learn what else you can do in YAML pipelines, see [YAML schema reference](yaml-schema.md).
+To learn what else you can do in YAML pipelines, see [YAML schema reference](/azure/devops/pipelines/yaml-schema/).

docs/pipelines/ecosystems/deploy-linux-vm.md

@@ -191,7 +191,7 @@ For more guidance, follow the steps mentioned in [Build your Node.js app with gu
     ```
 2. Select specific sets of VMs from the environment to receive the deployment by specifying the **tags** that you've defined for each VM in the environment.
 
-   For more information, see the [complete YAML schema for deployment job](../yaml-schema.md?tabs=schema#deployment-job).
+   For more information, see the [complete YAML schema for deployment job](/azure/devops/pipelines/yaml-schema/jobs-deployment).
 
 3. Specify either `runOnce` or `rolling` as a deployment strategy. 
 
@@ -278,4 +278,4 @@ The **Deployments** view provides complete traceability of commits and work item
 - [Variables](../process/variables.md)
 - [Triggers](../build/triggers.md)
 - [Troubleshooting](../troubleshooting/troubleshooting.md).
-- [YAML schema reference](../yaml-schema.md).
+- [YAML schema reference](/azure/devops/pipelines/yaml-schema).

docs/pipelines/ecosystems/dotnet-core.md

@@ -148,7 +148,7 @@ pool:
   vmImage: 'ubuntu-18.04' # examples of other options: 'macOS-10.15', 'windows-2019'
 ```
 
-See [Microsoft-hosted agents](../agents/hosted.md) for a complete list of images and [Pool](../yaml-schema.md#pool) for further examples.
+See [Microsoft-hosted agents](../agents/hosted.md) for a complete list of images and [Pool](/azure/devops/pipelines/yaml-schema/pool) for further examples.
 
 The Microsoft-hosted agents don't include some of the older versions of the .NET Core SDK. 
 They also don't typically include prerelease versions. If you need these kinds of SDKs on Microsoft-hosted agents, add the [UseDotNet@2](../tasks/tool/dotnet-core-tool-installer.md) task to your YAML file.

docs/pipelines/ecosystems/python.md

@@ -308,7 +308,7 @@ To authenticate with `twine`, use the [Twine Authenticate task](../tasks/package
     pythonUploadServiceConnection: '<twine service connection from external organization>'
 ```
 
-Then, add a custom [script](../yaml-schema.md#script) that uses `twine` to publish your packages.
+Then, add a custom [script](/azure/devops/pipelines/yaml-schema/steps-script) that uses `twine` to publish your packages.
 
 ```yaml
 - script: |

docs/pipelines/get-started/multi-stage-pipelines-experience.md

@@ -173,7 +173,7 @@ Learn more about configuring pipelines in the language of your choice:
 
 Learn more about building [Azure Repos](../repos/azure-repos-git.md) and [GitHub](../repos/github.md) repositories.
 
-To learn what else you can do in YAML pipelines, see [Customize your pipeline](../customize-pipeline.md), and for a complete reference see [YAML schema reference](../yaml-schema.md).
+To learn what else you can do in YAML pipelines, see [Customize your pipeline](../customize-pipeline.md), and for a complete reference see [YAML schema reference](/azure/devops/pipelines/yaml-schema).
 
 
 

docs/pipelines/includes/create-first-pipeline-next-steps.md

@@ -24,7 +24,7 @@ For details about building GitHub repositories, see [Build GitHub repositories](
 
 To lean how to publish your Pipeline Artifacts, see [Publish Pipeline Artifacts](../publish-pipeline-artifact.md).
 
-To find out what else you can do in YAML pipelines, see [YAML schema reference](../yaml-schema.md).
+To find out what else you can do in YAML pipelines, see [YAML schema reference](/azure/devops/pipelines/yaml-schema).
 
 ### Clean up
 

docs/pipelines/index.yml

@@ -95,7 +95,7 @@ landingContent:
       - linkListType: reference
         links:
           - text: YAML schema
-            url: yaml-schema.md
+            url: /azure/devops/pipelines/yaml-schema/
           - text: Predefined variables
             url: ./build/variables.md
           - text: Release & artifacts variables

docs/pipelines/library/task-groups.md

@@ -19,7 +19,7 @@ monikerRange: '>= tfs-2017'
 ::: moniker-end
 
 > [!NOTE]
-> Task groups are not supported in YAML pipelines. Instead, in that case you can use templates. See [YAML schema reference](../yaml-schema.md#step-templates).
+> Task groups are not supported in YAML pipelines. Instead, in that case you can use templates. See [YAML schema reference](/azure/devops/pipelines/yaml-schema/steps-template).
 
 A *task group* allows you to encapsulate a sequence of tasks, already defined
 in a build or a release pipeline, into a single reusable task that can be

docs/pipelines/migrate/from-jenkins.md

@@ -37,7 +37,7 @@ an Azure Pipelines YAML configuration. The two are conceptually similar,
 supporting "configuration as code" and allowing you to check your configuration
 into your version control system. Unlike Jenkins, however, Azure Pipelines
 uses the industry-standard [YAML to configure the build
-pipeline](../yaml-schema.md).
+pipeline](/azure/devops/pipelines/yaml-schema).
 
 The concepts between Jenkins and
 Azure Pipelines and the way they're configured are similar. A Jenkinsfile

docs/pipelines/policies/permissions.md

@@ -239,7 +239,7 @@ Task group permissions follow a hierarchical model. Defaults for all the permiss
 ### Set task group permissions at the project-level
 
 > [!NOTE]
-> Task groups are not supported in YAML pipelines. Instead, in that case you can use templates. See [YAML schema reference](../yaml-schema.md#step-templates).
+> Task groups are not supported in YAML pipelines. Instead, in that case you can use templates. See [YAML schema reference](/azure/devops/pipelines/yaml-schema/steps-template).
 
 
 1. Open **Pipelines** > **Task groups** in your project. 

docs/pipelines/process/demands.md

@@ -54,7 +54,7 @@ pool:
 > [!NOTE]
 > Checking for the existence of a capability (exists) and checking for a specific string in a capability (equals) are the only two supported operations for demands.
 
-For more information and examples, see [YAML schema - Demands](../yaml-schema.md#demands).
+For more information and examples, see [YAML schema - Demands](/azure/devops/pipelines/yaml-schema/pool).
 
 # [Classic](#tab/classic)
 

docs/pipelines/process/deployment-jobs.md

@@ -85,7 +85,7 @@ Deployment jobs use the `$(Pipeline.Workspace)` system variable.
 
 `preDeploy`: Used to run steps that initialize resources before application deployment starts. 
 
-`deploy`: Used to run steps that deploy your application. Download artifact task will be auto injected only in the `deploy` hook for deployment jobs. To stop downloading artifacts, use `- download: none` or choose specific artifacts to download by specifying [Download Pipeline Artifact task](../yaml-schema.md#download).
+`deploy`: Used to run steps that deploy your application. Download artifact task will be auto injected only in the `deploy` hook for deployment jobs. To stop downloading artifacts, use `- download: none` or choose specific artifacts to download by specifying [Download Pipeline Artifact task](/azure/devops/pipelines/yaml-schema/steps-download).
 
 `routeTraffic`: Used to run steps that serve the traffic to the updated version. 
 

docs/pipelines/process/environments-virtual-machines.md

@@ -114,7 +114,7 @@ jobs:
           - script: echo "Hello world"
 ```
 
-To learn more about deployment jobs, see the [YAML schema](../yaml-schema.md?tabs=schema#deployment-job).
+To learn more about deployment jobs, see the [YAML schema](/azure/devops/pipelines/yaml-schema/jobs-deployment).
 
 ## Add and manage tags
 
@@ -192,4 +192,4 @@ When you retry a stage, it reruns the deployment on all VMs and not just failed
 
 - [About environments](environments.md)
 - [Learn about deployment jobs](deployment-jobs.md)
-- [YAML schema reference](../yaml-schema.md)
+- [YAML schema reference](/azure/devops/pipelines/yaml-schema)

docs/pipelines/process/includes/parameter-data-types.md

@@ -14,13 +14,13 @@ ms.date: 02/28/2020
 | `boolean` | `true` or `false`
 | `object` | any YAML structure
 | `step` | a single step
-| `stepList` | sequence of [steps](../../yaml-schema.md#steps)
+| `stepList` | sequence of [steps](/azure/devops/pipelines/yaml-schema/steps)
 | `job` | a single job
-| `jobList` | sequence of [jobs](../../yaml-schema.md#job)
+| `jobList` | sequence of [jobs](/azure/devops/pipelines/yaml-schema/jobs-job)
 | `deployment` | a single deployment job
-| `deploymentList` | sequence of deployment [jobs](../../yaml-schema.md)
+| `deploymentList` | sequence of deployment jobs
 | `stage` | a single stage
-| `stageList` | sequence of [stages](../../yaml-schema.md)
+| `stageList` | sequence of stages
 
 The step, stepList, job, jobList, deployment, deploymentList, stage, and stageList data types all use standard YAML schema format. This example includes string, number, boolean, object, step, and stepList. 
 

docs/pipelines/process/phases.md

@@ -879,7 +879,7 @@ When you specify one of the `clean` options, they are interpreted as follows:
 > [!NOTE]
 > Depending on your agent capabilities and pipeline demands, each job may be routed to a different agent in your self-hosted pool. As a result, you may get a new agent for subsequent pipeline runs (or stages or jobs in the same pipeline), so **not** cleaning is not a guarantee that subsequent runs, jobs, or stages will be able to access outputs from previous runs, jobs, or stages. You can configure agent capabilities and pipeline demands to specify which agents are used to run a pipeline job, but unless there is only a single agent in the pool that meets the demands, there is no guarantee that subsequent jobs will use the same agent as previous jobs. For more information, see [Specify demands](demands.md).
 
-In addition to workspace clean, you can also configure cleaning by configuring the **Clean** setting in the pipeline settings UI. When the **Clean** setting is **true** it is equivalent to specifying `clean: true` for every [checkout](../yaml-schema.md#checkout) step in your pipeline. To configure the **Clean** setting:
+In addition to workspace clean, you can also configure cleaning by configuring the **Clean** setting in the pipeline settings UI. When the **Clean** setting is **true** it is equivalent to specifying `clean: true` for every [checkout](/azure/devops/pipelines/yaml-schema/steps-checkout) step in your pipeline. To configure the **Clean** setting:
 
 1. Edit your pipeline, choose **...**, and select **Triggers**.
 

docs/pipelines/process/resources.md

@@ -766,4 +766,4 @@ When you use the [Download Pipeline Artifacts task](../tasks/utility/download-pi
 * [Define variables](variables.md)
 * [Create and target an environment](environments.md)
 * [Use YAML pipeline editor](../get-started/yaml-pipeline-editor.md)
-* [YAML schema reference](../yaml-schema.md)
+* [YAML schema reference](/azure/devops/pipelines/yaml-schema)

docs/pipelines/process/tasks.md

@@ -29,7 +29,7 @@ To run the same set of tasks in parallel on multiple agents, or to run some task
 By default, all tasks run in the same context, whether that's on the [host](phases.md) or in a [job container](container-phases.md).
 You may optionally use [step targets](#step-target) to control context for an individual task.
 
-Learn more about how to specify properties for a task with the [YAML schema](../yaml-schema.md#task). 
+Learn more about how to specify properties for a task with the [built-in tasks](../tasks/index.md). 
 
 ::: moniker-end
 
@@ -193,9 +193,6 @@ steps:
   condition: succeededOrFailed()
 ```
 
-> [!NOTE]
-> For the full schema, see [YAML schema for `task`](../yaml-schema.md#task).
-
 
 ### Conditions
 

docs/pipelines/release/integrate-jenkins-pipelines-cicd.md

@@ -172,4 +172,4 @@ Now a new CD release will be triggered every time your Jenkins CI job is complet
 * [Artifacts](artifacts.md)
 * [Stages](../process/stages.md)
 * [Triggers](triggers.md)
-* [YAML schema reference](../yaml-schema.md)
+* [YAML schema reference](/azure/devops/pipelines/yaml-schema)

docs/pipelines/repos/azure-repos-git.md

@@ -197,7 +197,7 @@ To configure this setting, navigate to **Pipelines**, **Settings** at either **O
 > [!IMPORTANT]
 > **Limit job authorization scope to referenced Azure DevOps repositories** is enabled by default for new organizations and projects created after May 2020.
 
-When **Limit job authorization scope to referenced Azure DevOps repositories** is enabled, your YAML pipelines must explicitly reference any Azure Repos Git repositories you want to use in the pipeline as a [checkout step](../yaml-schema.md#checkout) in the job that uses the repository. You won't be able to fetch code using scripting tasks and git commands for an Azure Repos Git repository unless that repo is first explicitly referenced.
+When **Limit job authorization scope to referenced Azure DevOps repositories** is enabled, your YAML pipelines must explicitly reference any Azure Repos Git repositories you want to use in the pipeline as a [checkout step](/azure/devops/pipelines/yaml-schema/steps-checkout) in the job that uses the repository. You won't be able to fetch code using scripting tasks and git commands for an Azure Repos Git repository unless that repo is first explicitly referenced.
 
 There are a few exceptions where you don't need to explicitly reference an Azure Repos Git repository before using it in your pipeline when **Limit job authorization scope to referenced Azure DevOps repositories** is enabled.