removed archived content (MicrosoftDocs#4528)

* removed archived content

* remove archived content from project folder

* updates to test folder and includes folder

* build warning fixes

* some moniker replacements in artifacts folder

* build warning fixes

Author: KathrynEE

docs/artifacts/feeds/feed-permissions.md

@@ -63,7 +63,7 @@ By default, users in an Azure DevOps organization can create new feeds in that o
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 2. Select **Permissions**.
 

docs/artifacts/get-started-npm.md

@@ -16,7 +16,7 @@ monikerRange: '<= azure-devops'
 
 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"
+::: moniker range=" tfs-2018"
 
 ## License the Azure Artifacts extension
 
@@ -133,7 +133,7 @@ If you're developing on Windows, we recommend using `vsts-npm-auth` to authentic
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 <= tfs-2018"
+::: moniker range=" tfs-2018"
 
 1. Select **Packages**, and then select **Connect to feed**.
 

docs/artifacts/get-started-nuget.md

@@ -21,13 +21,13 @@ Developers can use Azure Artifacts to publish and consume NuGet packages both to
 - [Install NuGet client tools](/nuget/install-nuget-client-tools)
 - [Feed permissions](feeds/feed-permissions.md).
 
-::: moniker range=">=tfs-2017 <= tfs-2018"
+::: moniker range=" tfs-2018"
 
 This quickstart assumes you've already set up Azure Artifacts. You can check out how to license the extension in the [License Azure Artifacts guide](start-using-azure-artifacts.md).
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops"
+::: moniker range="< azure-devops"
 
 > [!NOTE]
 > Azure Artifacts is an extension that comes pre-installed on TFS 2017 or newer, if it was removed from your organization, you can install it from the [Azure Artifacts Marketplace](https://marketplace.visualstudio.com/items?itemName=ms.feed).

docs/artifacts/how-to/delete-and-recover-packages.md

@@ -38,7 +38,7 @@ In this article, you'll learn how to:
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build and Release**, and then select **Packages**.
 
@@ -74,7 +74,7 @@ In Azure Artifacts, packages are immutable. When you publish a package to your f
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build and Release**.
 
@@ -127,7 +127,7 @@ In Azure Artifacts, packages are immutable. When you publish a package to your f
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build and Release**.
 
@@ -149,7 +149,7 @@ In Azure Artifacts, packages are immutable. When you publish a package to your f
 
    ::: moniker-end
 
-   ::: moniker range=">=tfs-2017 < azure-devops-2019"
+   ::: moniker range="< azure-devops-2019"
 
     :::image type="content" source="../media/connect-to-feed.png" alt-text="Screenshot that shows the button for connecting to a feed in Team Foundation Server.":::
 
@@ -225,7 +225,7 @@ To configure retention policies:
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build and Release**.
 
@@ -277,7 +277,7 @@ Deleted packages will remain in the Recycle Bin for 30 days. After that, they'll
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build and Release**, and then select **Packages**. 
 

docs/artifacts/includes/create-feed.md

@@ -28,7 +28,7 @@ ms.date: 02/14/2022
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 <= tfs-2018"
+::: moniker range="tfs-2018"
 
 Azure Artifacts is installed by default for TFS 2017 customers. You must upgrade to TFS 2017 in order to use Azure Artifacts. If this is the first time using your feed, you might be asked to [assign a license](../start-using-azure-artifacts.md?preserve-view=true&view=tfs-2018#assign-licenses-in-tfs)
 

docs/artifacts/includes/edit-feed.md

@@ -15,7 +15,7 @@ ms.date: 02/16/2022
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 <= tfs-2018"
+::: moniker range=" tfs-2018"
 
 1. Select the gear icon to navigate to your feed's settings.
 

docs/artifacts/includes/npm/npmrc.md

@@ -85,7 +85,7 @@ ms.date: 02/15/2022
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 <= tfs-2018"
+::: moniker range=" tfs-2018"
 
 1. From **Packages**, select **Connect to feed**.
 

docs/artifacts/includes/nuget/nuget-consume-endpoint.md

@@ -22,7 +22,7 @@ ms.date: 09/07/2021
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build and Release**, and then select **Packages**.
 

docs/artifacts/includes/nuget/nuget-publish-endpoint.md

@@ -29,7 +29,7 @@ ms.date: 02/18/2022
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build and Release** > **Packages**.
 

docs/artifacts/maven/publish-package-gradle.md

@@ -51,7 +51,7 @@ gradle -v
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 <= tfs-2018"
+::: moniker range="tfs-2018"
 
 1. Select your profile icon, and then select **Security**.
 

docs/artifacts/npm/npmrc.md

@@ -28,7 +28,7 @@ We recommend using two **.npmrc_** files, the first one we'll use to authenticat
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Packages**, and then select **Connect to feed**.
 
@@ -56,7 +56,7 @@ We recommend using two **.npmrc_** files, the first one we'll use to authenticat
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 4. Follow the instructions to set up your project.
 
@@ -180,7 +180,7 @@ Azure Artifacts recommend using the `npmAuthenticate` task to set up authenticat
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build and Release**, and then select **Builds**.
 

docs/artifacts/npm/upstream-sources.md

@@ -54,7 +54,7 @@ You can view the packages you saved from upstreams by selecting your **Source**
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 
 :::image type="content" source="media/view-cached-packages.png" alt-text="Screenshot of the filtered npm packages in TFS":::

docs/artifacts/nuget/nuget-exe.md

@@ -34,7 +34,7 @@ monikerRange: '>= tfs-2018'
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 <= tfs-2018"
+::: moniker range="tfs-2018"
 
 2. Select **Connect to feed**.
 
@@ -86,7 +86,7 @@ nuget setapikey <Personal_Access_Token> -source <Feed_URL>
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 <= tfs-2018"
+::: moniker range="tfs-2018"
 
 ## Project setup (NuGet 2)
 

docs/artifacts/nuget/upstream-sources.md

@@ -59,7 +59,7 @@ You can view the packages you saved from upstreams by selecting your **Source**
 
 ::: moniker-end
 
-::: moniker range=">= tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 :::image type="content" source="media/view-cached-packages.png" alt-text="A screenshot showing how to filter packages by source in TFS":::
 

docs/artifacts/package-badges.md

@@ -34,7 +34,7 @@ To start sharing your Artifacts packages using package badges, you'll first have
 
    ::: moniker-end
 
-   ::: moniker range="<= tfs-2018"
+   ::: moniker range="tfs-2018"
 
    :::image type="content" source="media/edit-feed-full.png" alt-text="A screenshot showing how to navigate to the feed settings in TFS":::
 
@@ -52,7 +52,7 @@ To start sharing your Artifacts packages using package badges, you'll first have
 
     ::: moniker-end
 
-    ::: moniker range="<= tfs-2018"
+    ::: moniker range="tfs-2018"
 
     This will enable the **Create badge** button for every package in that feed.
 

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

@@ -28,7 +28,7 @@ Azure Artifacts comes pre-installed in Azure DevOps Services, Azure DevOps Serve
 > [!NOTE]
 > Azure Artifacts license is included with every basic license for TFS 2017, 2018, and Azure DevOps Server 2019 and 2020.
 
-::: moniker range=">= tfs-2017 <= tfs-2018"
+::: moniker range="tfs-2018"
 
 ## Install Azure Artifacts in TFS
 

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

@@ -34,7 +34,7 @@ In this tutorial, you will:
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build & Release**, and then select **Packages**.
 
@@ -50,7 +50,7 @@ In this tutorial, you will:
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 2. Select **New Feed** to create a new feed.
 
@@ -66,7 +66,7 @@ In this tutorial, you will:
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 3. Provide a name for your feed, and then select its visibility. Make sure your check the **Include packages from common public sources** checkbox to enable upstream sources. Select **Create** when you are done
 
@@ -97,7 +97,7 @@ Now that we created our feed, we need to update the config file to point to our
 
 ::: moniker-end
 
-::: moniker range=">=tfs-2017 < azure-devops-2019"
+::: moniker range="< azure-devops-2019"
 
 1. Select **Build & Release** > **Packages**, and then select **Connect to Feed**.
 

docs/includes/features-not-available-stakeholder.md

@@ -3,7 +3,7 @@ ms.technology: devops-agile
 ms.author: kaelli
 author: KathrynEE
 ms.topic: include
-ms.date: 04/09/2021
+ms.date: 04/04/2022
 ---
 
 ### Features not available to users with Stakeholder access 
@@ -75,29 +75,5 @@ If a Stakeholder needs access to one or more of the following features—whi
 - Access the full set of features under **Code**, **Build and Release**, or **Test**.  
 ::: moniker-end
 
-::: moniker range="tfs-2017"
-
-- Change the priority of an item within a backlog
-- Delete work items 
-- Add work items, drag-and-drop work items, or change fields on cards on a Kanban board
-- Add new work item tags 
-- Create shared queries, view charts, and modify dashboards  
-- View Delivery Plans (a Marketplace extension)
-- Access the full set of features under **Code**, **Build and Release**, or **Test** 
-- Participate in team rooms, which capture interactive, detailed conversations about the project.  
-
-::: moniker-end
-
-::: moniker range="<= tfs-2015"
-
-- Change the priority of an item within a backlog
-- Delete work items 
-- Add work items, drag-and-drop work items, or change fields on cards on a Kanban board
-- Add new work item tags 
-- Create shared queries, view charts, and modify the home page  
-- Access the full set of features under **Code**, **Build and Release**, or **Test**  
-- Participate in team rooms, which capture interactive, detailed conversations about the project.  
-
-::: moniker-end
 
 

docs/includes/get-started/customize-work-tracking.md

@@ -3,7 +3,7 @@ ms.technology: devops-security
 ms.author: kaelli
 author: KathrynEE
 ms.topic: include
-ms.date: 02/28/2022
+ms.date: 04/04/2022
 ---
 
 
@@ -26,7 +26,7 @@ To learn more, see these articles:
 
 ::: moniker-end
 
-::: moniker range="<= tfs-2018"
+::: moniker range="tfs-2018"
 
 - [On-premises XML process customization](../../reference/on-premises-xml-process-model.md)  
 - [Add or modify a field to track work](../../reference/add-modify-field.md)  

docs/includes/get-started/share-project-vision.md

@@ -3,34 +3,23 @@ ms.technology: devops-new-user
 ms.author: kaelli
 author: KathrynEE
 ms.topic: include
-ms.date: 02/28/2022
+ms.date: 04/04/2022
 ---
- 
 
 <a id="share-vision" />
 
 
-::: moniker range=">= tfs-2018"
-
 ## Share your project vision, set up a project wiki 
 
-::: moniker-end
 
 ::: moniker range="azure-devops"  
 
 Each project has a summary page that's useful for sharing information through **README** files. Or, redirect users to a project Wiki. For users who are new to your project, we recommend that you [set up your project summary page](../../organizations/projects/project-vision-status.md). Or, you can [provision a Wiki](../../project/wiki/wiki-create-repo.md). Use these features to share established processes and procedures for your project. 
 
 ::: moniker-end  
 
-::: moniker range=">= tfs-2018 < azure-devops"  
+::: moniker range="< azure-devops"  
 Each project has a summary page that's useful for sharing information through **README files**. For users who are new to your project, we recommend that you [set up your project summary page](../../organizations/projects/project-vision-status.md). Or, you can [provision a Wiki](../../project/wiki/wiki-create-repo.md). Use these features to share established processes and procedures for your project. 
 
 ::: moniker-end
 
-::: moniker range="< tfs-2018" 
-
-## Share your project vision 
-
-Each project has a summary page that's useful for sharing information through **README files**. You can use this page to share information relevant to your project. To learn more, see [set up your project summary page](../../organizations/projects/project-vision-status.md). 
-
-::: moniker-end