Adding version includes to articles with no version header (#4342)

* Updated includes

* Added version files to articles with no header

Co-authored-by: Steve Danielson <steve.danielson@microsoft.com>

Author: steved0x

docs/artifacts/concepts/best-practices.md

@@ -10,6 +10,8 @@ monikerRange: '>= tfs-2017'
 
 # Azure Artifacts: best practices
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 This article contains some general guidance and best practices when it comes to producing and consuming packages in Azure Artifacts.
 
 ## Create and publish packages

docs/artifacts/concepts/upstream-behavior.md

@@ -11,6 +11,8 @@ monikerRange: '>= tfs-2017'
 
 # Configure upstream behavior
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 Upstream sources enables developers to use a single feed to publish and consume packages from Artifact feeds and public registries such as NuGet.org or npmjs.com. To set up upstream sources for your feed, check the box to **include packages from common public sources**. This will allow your feed to use packages from the common public registries.
 
 :::image type="content" source="media/include-upstream-sources.png" alt-text="Include packages from common public sources checkbox":::

docs/artifacts/feeds/project-scoped-feeds.md

@@ -9,6 +9,8 @@ monikerRange: '>= tfs-2017'
 
 # Project-scoped feeds
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 Historically, all feeds used to be scoped to an organization. However, to enable public feeds and to become more consistent with the rest of Azure DevOps, feeds created through the new create feed web UI will now be scoped to a project. 
 
 New organizations will automatically have one feed scoped to the organization and all subsequent feeds created will be scoped to a project. All existing organization-scoped feeds will remain organization-scoped.

docs/artifacts/get-started-npm.md

@@ -12,6 +12,8 @@ monikerRange: '>= tfs-2017'
 
 # Get started with npm packages in Azure Artifacts
 
+[!INCLUDE [version-gt-eq-2017](../includes/version-gt-eq-2017.md)]
+
 With Azure Artifacts, you can publish and download npm packages from feeds and public registries such as npmjs.com. This quickstart will guide you through creating your own feed, setting up your project, and publishing and downloading npm packages to and from your Azure Artifacts feed.
 
 ::: moniker range=">=tfs-2017 <= tfs-2018"

docs/artifacts/how-to/follow-package-notifications.md

@@ -1,4 +1,4 @@
----
+---
 title: Receive package notifications
 description: How to follow a package and get notified every time a new version is published
 ms.technology: devops-artifacts
@@ -9,6 +9,8 @@ monikerRange: '>= tfs-2017'
 
 # Package notification
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 Notifications are a great tool to stay informed about specific changes within your project. In Azure Artifacts, when you follow a package you’ll be notified every time a new version of that package is published. A notification will be sent to your preferred email address with details about the new published version. The preferred email address is usually the email address you signed into Azure DevOps with, but you can change it from your profile page.
 
 ## Follow a package

docs/artifacts/how-to/project-scoped-feeds-pipeline-project-permissions.md

@@ -1,4 +1,4 @@
----
+---
 title: Allow Pipelines to access project-scoped feeds that are scoped to a different project
 description: How to set permissions to access a project-scoped feed in a different project
 ms.technology: devops-artifacts
@@ -9,6 +9,8 @@ monikerRange: '>= tfs-2017'
 
 # How to allow a Pipeline to access a project-scoped feed in a different project
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 When a Pipeline needs to connect to a project-scoped feed in a different project, the pipeline must have access to both the project that the feed is scoped to and the feed itself.
 Your **Project build service** identity will look as follows:
 `[Project name] Build Service ([Organization name])` (e.g. FabrikamFiber Build Service (codesharing-demo))

docs/artifacts/npm/npm-audit.md

@@ -9,6 +9,8 @@ monikerRange: 'azure-devops'
 
 # Use npm audit
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 The *npm audit* command scans your project for security vulnerabilities and provides a detailed report of any identified anomaly. Performing security audits is an essential part in identifying and fixing vulnerabilities in the project's dependencies. Fixing these vulnerabilities could prevent things like data loss, service outages, and unauthorized access to sensitive information.
 
 Azure DevOps does not support *npm audit*, if you try to run the default *npm audit* command from your pipeline, the task will fail with the following message: *Unexpected end of JSON input while parsing...*.

docs/artifacts/nuget/move-from-fileshares.md

@@ -11,6 +11,8 @@ monikerRange: '>= tfs-2017'
 
 # Migrate your packages from file shares
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 Azure Artifacts provides hosted NuGet feeds as a service. If you're using NuGet packages as a part of your continuous delivery workflow, Azure Artifacts can help you manage your dependencies through public and private feeds. Azure Artifacts works with any continuous integration system that supports authenticated NuGet feeds.
 
 ## Key concepts

docs/artifacts/nuget/publish-to-nuget-org.md

@@ -11,6 +11,8 @@ monikerRange: '>= tfs-2017'
 
 # Publish packages to NuGet.org
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 NuGet.org is a package manager that enables developers to share reusable code. A NuGet package is a compressed file with `.nupkg` extension that contains compiled code that can be consumed in other projects. Packages hosted in NuGet.org are available to all developers around the world.
 
 ## Prerequisites

docs/artifacts/quickstarts/github-actions.md

@@ -11,6 +11,8 @@ ms.topic: quickstart
 
 # Quickstart: Use GitHub Actions to push to Azure Artifacts
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 Get started using [GitHub Actions](https://docs.github.com/en/actions) and Azure Artifacts together. GitHub Actions help you automate your software development workflows from within GitHub. You can use GitHub Actions to deploy to an Azure Artifacts feed. 
 ## Prerequisites
 

docs/artifacts/quickstarts/universal-packages.md

@@ -10,6 +10,8 @@ monikerRange: '>= tfs-2017'
 
 # Publish and download universal packages with Azure CLI
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 With universal packages, you can store different types of packages other than the widely used ones such as NuGet, npm, Maven, or Python packages. Using Azure CLI, you can publish and download universal packages from the command line. Uploaded packages can vary in size (up to 4 TB), but should always have a name and a version number. This article will walk you through the steps to publish and download your universal packages to Azure Artifacts feeds.
 
 ## Prerequisites

docs/artifacts/reference/artifactignore.md

@@ -11,6 +11,8 @@ monikerRange: 'azure-devops'
 
 # Use .artifactignore
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 The *.artifactignore* is a text file that controls which files are uploaded when you publish a Universal Package or a Pipeline Artifact.
 
 *.artifactignore* is typically checked into your version control repository and the syntax is similar to that of *.gitignore*.

docs/artifacts/reference/limits.md

@@ -9,6 +9,8 @@ monikerRange: '>= tfs-2017'
 
 # Package sizes and count limits
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 Azure Artifacts is a highly scalable package management solution that enables developers to create, host, and share different types of packages. In this article, we will cover the size and count limits that developers should be aware of when using Azure Artifacts. Some of these limits are imposed by the client tools that Azure Artifacts integrates with (example nuget.exe).
 
 ## Count limits

docs/artifacts/start-using-azure-artifacts.md

@@ -12,6 +12,8 @@ monikerRange: '>= tfs-2017'
 
 # Azure Artifacts overview
 
+[!INCLUDE [version-gt-eq-2017](../includes/version-gt-eq-2017.md)]
+
 Azure Artifacts enables developers to share and consume packages from different feeds and public registries. Packages can be shared within the same team, the same organization, and even publicly. Azure Artifacts supports multiple package types such as NuGet, npm, Python, Maven, and Universal Packages.
 
 Azure Artifacts gets billed on a consumption basis, and is free up until 2 GiB of storage. If your organization needs more storage, you must [set up billing](../organizations/billing/set-up-billing-for-your-organization-vs.md).

docs/artifacts/symbols/debug-with-symbols-windbg.md

@@ -11,6 +11,8 @@ monikerRange: '>= tfs-2017'
 
 # Debug with WinDbg
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
  Azure Artifacts offers a dedicated symbols server to publish your symbols. You can connect a debugger to automatically retrieve the correct symbol files and debug your application. Using WinDbg, you can load an executable or attach the debugger to a running process, consume your symbols, set up breakpoints, and step through and analyze your code.
 
 ## Add the symbol server to WinDbg

docs/artifacts/tutorials/migrate-packages.md

@@ -9,6 +9,8 @@ monikerRange: 'azure-devops'
 
 # Migrate NuGet packages to Azure Artifacts
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 Using the `AzureArtifactsPackageMigration` PowerShell module, you can easily migrate your NuGet packages to Azure Artifacts. This article will walk you through an example of migrating NuGet packages from MyGet to Azure Artifacts.
 
 In this article, you'll learn how to:

docs/artifacts/tutorials/protect-oss-packages-with-upstream-sources.md

@@ -10,6 +10,8 @@ monikerRange: '>= tfs-2017'
 
 # Tutorial: How to use upstream sources
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 Using upstream sources in your feed enables you to manage your application dependencies from a single feed. Using upstream sources makes it easy to consume packages from public registries while having protection against outages or compromised packages. You can also publish your own packages to the same feed and manage all your dependencies in one location.
 
 This tutorial will walk you though how to enable upstream sources on your feed and consume packages from public registries such as NuGet.org or npmjs.com.

docs/artifacts/tutorials/share-packages-publicly.md

@@ -8,6 +8,8 @@ monikerRange: 'azure-devops'
 
 # Share packages publicly
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 Azure Artifacts provides an easy way to share packages to users outside your organization using public feeds. Packages that are stored in public feeds can be restored, installed, or consumed by anyone on the Internet.
 
 ## Prerequisites

docs/pipelines/agents/docker.md

@@ -9,6 +9,8 @@ monikerRange: '>= azure-devops-2019'
 
 # Run a self-hosted agent in Docker
 
+[!INCLUDE [version-gt-eq-2019](../../includes/version-gt-eq-2019.md)]
+
 This article provides instructions for running your Azure Pipelines agent in Docker. You can set up a self-hosted agent in Azure Pipelines to run inside a Windows Server Core (for Windows hosts), or Ubuntu container (for Linux hosts) with Docker. This is useful when you want to run agents with outer orchestration, such as [Azure Container Instances](/azure/container-instances/). In this article, you'll walk through a complete container example, including handling agent self-update.
 
 Both [Windows](#windows) and [Linux](#linux) are supported as container hosts. Windows containers should run on a Windows `vmImage`. 

docs/pipelines/agents/pool-consumption-report.md

@@ -8,6 +8,8 @@ monikerRange: 'azure-devops'
 
 # Historical graph for agent pools (Preview)
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 The pool consumption report enables you to view jobs running in your agent pools graphed with agent pool job concurrency over a span of up to 30 days. You can use this information to help decide whether your jobs aren't running because of concurrency limits. If you have many jobs queued or running jobs at the concurrency or online agents limit, you may wish to [purchase additional parallel jobs](../licensing/concurrent-jobs.md) or provision more self-hosted agents.
 
 ## Prerequisites

docs/pipelines/apps/cd/azure/build-data-pipeline.md

@@ -11,6 +11,8 @@ monikerRange: '=azure-devops'
 
 # Build a data pipeline by using Azure Data Factory, DevOps, and machine learning
 
+[!INCLUDE [version-eq-azure-devops](../../../../includes/version-eq-azure-devops.md)]
+
 Get started building a data pipeline with data ingestion, data transformation, and model training. 
 
 Learn how to grab data from a CSV (comma-separated values) file and save the data to Azure Blob Storage. Transform the data and save it to a staging area. Then train a machine learning model by using the transformed data. Write the model to blob storage as a Python [pickle file](https://docs.python.org/3/library/pickle.html). 

docs/pipelines/apps/cd/azure/cicd-data-overview.md

@@ -11,6 +11,8 @@ monikerRange: '=azure-devops'
 
 # Why data pipelines?
 
+[!INCLUDE [version-eq-azure-devops](../../../../includes/version-eq-azure-devops.md)]
+
 You can use data pipelines to:
 * Ingest data from various data sources
 * Process and transform the data 

docs/pipelines/apps/cd/azure/deploy-arm-template.md

@@ -11,6 +11,8 @@ ms.custom: subject-armqs, contperf-fy21q2
 
 # Quickstart: Use an ARM template to deploy a Linux web app to Azure
 
+[!INCLUDE [version-eq-azure-devops](../../../../includes/version-eq-azure-devops.md)]
+
 Get started with [Azure Resource Manager templates (ARM templates)](/azure/azure-resource-manager/templates/overview) by deploying a Linux web app with MySQL. ARM templates give you a way to save your configuration in code. Using an ARM template is an example of infrastructure as code and a good DevOps practice.
 
 An [ARM template](/azure/azure-resource-manager/templates/overview) is a JavaScript Object Notation (JSON) file that defines the infrastructure and configuration for your project. The template uses declarative syntax. In declarative syntax, you describe your intended deployment without writing the sequence of programming commands to create the deployment.

docs/pipelines/apps/cd/azure/deploy-virtual-scale-set-java.md

@@ -10,6 +10,8 @@ monikerRange: 'azure-devops'
 
 # Tutorial: Deploy a Java app to a virtual machine scale set
 
+[!INCLUDE [version-eq-azure-devops](../../../../includes/version-eq-azure-devops.md)]
+
 A [virtual machine scale set](/azure/virtual-machine-scale-sets/overview) lets you deploy and manage identical, autoscaling virtual machines. 
 
 VMs are created as needed in a scale set. You define rules to control how and when VMs are added or removed from the scale set. These rules can be triggered based on metrics such as CPU load, memory usage, or network traffic.

docs/pipelines/artifacts/artifacts-overview.md

@@ -11,6 +11,8 @@ monikerRange: '>= tfs-2015'
 
 # Artifacts in Azure Pipelines - overview
 
+[!INCLUDE [version-gt-eq-2015](../../includes/version-gt-eq-2015.md)]
+
 Azure Artifacts enable developers to consume and publish different types of packages to Artifacts feeds and public registries such as NuGet.org and npmjs.com. You can use Azure Artifacts in conjunction with Azure Pipelines to deploy packages, publish build artifacts, or integrate files between your pipeline stages to build, test, or deploy your application.
 
 ## Supported artifact types

docs/pipelines/artifacts/build-artifacts.md

@@ -10,6 +10,8 @@ monikerRange: '>= tfs-2015'
 
 # Artifacts in Azure Pipelines
 
+[!INCLUDE [version-gt-eq-2015](../../includes/version-gt-eq-2015.md)]
+
 > [!NOTE]
 > We recommend upgrading from **build artifacts** (`PublishBuildArtifacts@1` and `DownloadBuildArtifacts@0`) to **[pipeline artifacts](pipeline-artifacts.md)** (`PublishPipelineArtifact@1` and `DownloadPipelineArtifact@2`) for faster performance. 
 

docs/pipelines/artifacts/caching-nuget.md

@@ -11,6 +11,8 @@ monikerRange: '>= tfs-2017'
 
 # How to cache NuGet packages to reduce the build time
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 With pipeline caching, you can reduce your build time by caching your dependencies to be used in later runs. In this article, we will walk through the steps to cache and restore NuGet packages.
 
 ## Lock dependencies

docs/pipelines/artifacts/pypi.md

@@ -11,6 +11,8 @@ monikerRange: azure-devops
 
 # Publish Python packages with Azure Pipelines
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 Using Azure Pipelines, you can publish your Python packages to Azure Artifacts feeds, public registries, or as a pipeline artifacts. 
 
 This article will show you how to: 

docs/pipelines/build/options.md

@@ -10,6 +10,8 @@ monikerRange: '>= tfs-2015'
 
 # Build options
 
+[!INCLUDE [version-gt-eq-2015](../../includes/version-gt-eq-2015.md)]
+
 ::: moniker range="<= tfs-2018"
 
 [!INCLUDE [temp](../includes/concept-rename-note.md)]

docs/pipelines/build/run-retention.md

@@ -10,6 +10,8 @@ monikerRange: ">= azure-devops-2020"
 
 # Pipeline Run Retention
 
+[!INCLUDE [version-gt-eq-2020](../../includes/version-gt-eq-2020.md)]
+
 Retaining a pipeline run for longer than the configured [project settings](../policies/retention.md) is handled by the creation of **retention leases**. Temporary retention leases are often created by automatic processes and more permanent leases by manipulating the UI or when Release Management retains artifacts, but they can also be manipulated through the [REST API](/rest/api/azure/devops/build/leases). Here are a some examples of tasks that you can add to your yaml pipeline that will cause a run to retain itself.
 
 ## Prerequisites

docs/pipelines/build/triggers.md

@@ -11,6 +11,8 @@ monikerRange: '>= tfs-2015'
 
 # Specify events that trigger pipelines
 
+[!INCLUDE [version-gt-eq-2015](../../includes/version-gt-eq-2015.md)]
+
 ::: moniker range="<= tfs-2018"
 [!INCLUDE [temp](../includes/concept-rename-note.md)]
 ::: moniker-end

docs/pipelines/ecosystems/ecosystems.md

@@ -16,6 +16,8 @@ monikerRange: '>= tfs-2015'
 
 # Create your Azure Pipelines ecosystem
 
+[!INCLUDE [version-gt-eq-2015](../../includes/version-gt-eq-2015.md)]
+
 You can select from the following languages and platforms to find guidance for building and deploying your app. 
 
 ::: moniker range=">= tfs-2015 <= tfs-2018 || >= azure-devops-2019"

docs/pipelines/library/variable-groups.md

@@ -12,6 +12,8 @@ monikerRange: '>= tfs-2017'
 
 # Add & use variable groups
 
+[!INCLUDE [version-gt-eq-2017](../../includes/version-gt-eq-2017.md)]
+
 Variable groups store values and secrets that you might want to be [passed into a YAML pipeline](variable-groups.md?tabs=yaml&view=azure-devops&preserve-view=true#use-a-variable-group) or make available across multiple pipelines. You can share and use variables groups in multiple pipelines in the same project.
 
 Variables groups are [protected resources](../security/resources.md). You can add approvals and checks to these variables and set pipeline permissions.

docs/pipelines/publish-pipeline-artifact.md

@@ -10,6 +10,8 @@ monikerRange: '>= azure-devops-2020'
 
 # Publish Pipeline Artifacts
 
+[!INCLUDE [version-gt-eq-2020](../includes/version-gt-eq-2020.md)]
+
 Azure Artifacts enable developers to store and manage their packages and control who they want to share it with. Pipeline Artifacts are generally generated after you build your application. The output can then deployed or consumed by another job in your pipeline.
 
 ## Publish Artifacts

docs/pipelines/release/caching.md

@@ -10,6 +10,8 @@ monikerRange: azure-devops
 
 # Pipeline caching
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 Pipeline caching can help reduce build time by allowing the outputs or downloaded dependencies from one run to be reused in later runs, thereby reducing or avoiding the cost to recreate or redownload the same files again. Caching is especially useful in scenarios where the same dependencies are downloaded over and over at the start of each run. This is often a time consuming process involving hundreds or thousands of network calls.
 
 Caching can be effective at improving build time provided the time to restore and save the cache is less than the time to produce the output again from scratch. Because of this, caching may not be effective in all scenarios and may actually have a negative impact on build time.

docs/pipelines/release/visualize-release-test-progress.md

@@ -10,6 +10,8 @@ monikerRange: '>= tfs-2015'
 
 # View release progress and test summary
 
+[!INCLUDE [version-gt-eq-2015](../../includes/version-gt-eq-2015.md)]
+
 Azure Pipelines provides a quick and easy way to check the status of your deployment and test results right from your pipeline definition page. The user interface provides a live update of deployment progress and easy access to logs for more details.
 
 ::: moniker range=">= azure-devops-2019"

docs/pipelines/repos/github-enterprise.md

@@ -8,6 +8,8 @@ monikerRange: 'azure-devops'
 
 # Build GitHub Enterprise Server repositories
 
+[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
+
 You can integrate your on-premises GitHub Enterprise Server with Azure Pipelines. Your on-premises server may be exposed to the Internet or it may not be.
 
 If your GitHub Enterprise Server is reachable from the servers that run Azure Pipelines service, then: