Merge pull request #3802 from atikmapari/Broken-link-alexcnichols

Broken link fixed

Author: PRMerger15

Diff for: release-notes/2017/jul-14-team-services.md

@@ -79,7 +79,7 @@ When preparing a PR or commenting you sometimes have a short list of things that
 
 ![Task list toolbar](media/07_14_13.png)
 
-Once you’ve added a task list, you can simply check the boxes to mark items as completed. These are expressed and stored within the comment as `[ ]` and `[x]` in Markdown. See [Markdown guidance](https://visualstudio.microsoft.com/docs/reference/markdown-guidance#checklist-or-task-list) for more information.
+Once you’ve added a task list, you can simply check the boxes to mark items as completed. These are expressed and stored within the comment as `[ ]` and `[x]` in Markdown. See [Markdown guidance](/azure/devops/project/wiki/markdown-guidance#checklist-or-task-list) for more information.
 
 ![Task list complete](media/07_14_14.png)
 
@@ -90,7 +90,7 @@ Show your support for a PR comment with a single click on the __like__ button. Y
 
 ## Build
 ### Pull request build variables
-You can now get the pull request ID, source branch, and target branch from  [build variables](https://visualstudio.microsoft.com/docs/build/define/variables).
+You can now get the pull request ID, source branch, and target branch from  [build variables](/azure/devops/pipelines/process/variables).
 
 ### Faster publishing of artifacts from Windows agents to file shares
 We’ve added an option to make it faster to publish artifacts from Windows agents to file shares. In the __Publish Build Artifacts__ task arguments, select **Enable Copy Concurrency** to enable multi-threaded mode and copy multiple files at the same time. This is equivalent to `robocopy /mt`. Optionally you can specify the number of threads in the **Copy Concurrency Value** (the default is 8).
@@ -170,7 +170,7 @@ A team admin can configure their team’s default delivery preference via the te
 ### Constraints on SVG images, screenshots and badges
 Due to security concerns, we have added SVG constraints to make extensions safer.
 * The icons and screenshot can no longer be SVG.
-* The badges provided in the manifest can not be SVGs unless they are from [approved badge providers](https://visualstudio.microsoft.com/docs/integrate/extensions/develop/manifest#approvedbadges).
+* The badges provided in the manifest can not be SVGs unless they are from [approved badge providers](/azure/devops/extend/develop/manifest#approvedbadges).
 * Images in README.md and CHANGELOG.md can not be SVGs unless they are from approved badge providers.
 
 ## How to provide feedback

Diff for: release-notes/2017/jun-22-team-services.md

@@ -26,7 +26,7 @@ If you change the description or the picklist values of a shared field, it will
 ## Work item type icons
 We have made a global commitment to make our products fully accessible to our customers. As part of that commitment, we have been working to find and address many accessibility issues—anywhere from keyboard patterns to visual design and layout. 
 
-Work item tracking has relied solely on color in many experiences to convey work item type. However, this is problematic for our color-blind or low-vision users who may not be able to distinguish between items due to similarities in color. To increase the scanability of work item types for all our customers, we have introduced icons to our visual language of work item types. You can [customize your work item types](https://visualstudio.microsoft.com/docs/work/process/customize-process-wit#change-description-icon-or-color-of-a-custom-wit) by choosing from our icon library.
+Work item tracking has relied solely on color in many experiences to convey work item type. However, this is problematic for our color-blind or low-vision users who may not be able to distinguish between items due to similarities in color. To increase the scanability of work item types for all our customers, we have introduced icons to our visual language of work item types. You can [customize your work item types](/azure/devops/work/process/customize-process-wit#change-description-icon-or-color) by choosing from our icon library.
 
 Color bars conveying type on the backlog and queries grids have been replaced with colored icons.
 
@@ -46,7 +46,7 @@ Change the setting through your Visual Studio profile.
 ![profile setting](media/06_22_35.png)
 
 ## Extensions block work item save
-Work item form custom controls, groups, and pages can now [block work item save](https://visualstudio.microsoft.com/docs/integrate/extensions/reference/client/api/tfs/workitemtracking/services/workitemformservice#seterror) to validate data and ensure the user fills out any required information before saving the work item form. 
+Work item form custom controls, groups, and pages can now block work item save to validate data and ensure the user fills out any required information before saving the work item form. 
 
 ## Collapsible pull request comments
 Reviewing code is a critical part of the pull request experience, so we’ve added new features to make it easier for reviewers to focus on the code. Code reviewers can easily hide comments to get them out of the way when reviewing new code for the first time.  
@@ -143,7 +143,7 @@ In this release you’ll see the following changes:
 
 ![default build queue on tasks tab](media/06_22_default-build-queue-on-tasks-tab-required.png)
 
-* The [Visual Studio Build](https://visualstudio.microsoft.com/docs/build/steps/build/visual-studio-build) and [MSBuild](https://visualstudio.microsoft.com/docs/build/steps/build/msbuild) tasks now default to the **Latest** setting for the version argument.
+* The [Visual Studio Build](/azure/devops/pipelines/tasks/build/visual-studio-build) and [MSBuild](/azure/devops/pipelines/tasks/build/msbuild) tasks now default to the **Latest** setting for the version argument.
 
 Coming soon you’ll see more changes. For example, the following hosted pools (and corresponding queues) will be:
 
@@ -162,7 +162,7 @@ Coming soon you’ll see more changes. For example, the following hosted pools (
 
 We recommend that you migrate to our new task-based build system, which includes access to hosted agents to run your builds. See our recently published guide to [migrate from XAML builds to new builds](/azure/devops/pipelines/build/migrate-from-xaml-builds).
 
-However, if you still need to run XAML builds during the migration, then you should set up a private XAML build controller now. To use private XAML controllers and agents, you need to have sufficient private pipelines in your account. For details, see [I’m looking for the hosted XAML build controller. Where did it go?](https://visualstudio.microsoft.com/docs/build/concepts/agents/hosted#im-looking-for-the-hosted-xaml-build-controller-where-did-it-go)
+However, if you still need to run XAML builds during the migration, then you should set up a private XAML build controller now. To use private XAML controllers and agents, you need to have sufficient private pipelines in your account. For details, see [I’m looking for the hosted XAML build controller. Where did it go?](/azure/devops/pipelines/agents/hosted#im-looking-for-the-hosted-xaml-build-controller-where-did-it-go)
 
 ## Build definition menu on build summary page
 
@@ -193,7 +193,7 @@ To enable this feature in the __Variable Groups__ page, use the toggle button __
 
 ![add secrets](media/06_22_29.png)
 
-After you have created a variable group mapped to Azure Key Vault, you can link it to your release definitions, as documented in [Variable groups](https://visualstudio.microsoft.com/docs/build/concepts/library/variable-groups).
+After you have created a variable group mapped to Azure Key Vault, you can link it to your release definitions, as documented in [Variable groups](/cli/azure/pipelines/variable-group).
 
 Note that it’s just the secret names that are mapped to the variable group variables, not the values. The actual values (the latest version) of each secret will be fetched and consumed during the release.  
 
@@ -225,7 +225,7 @@ As part of this work, we’ve also released a new __NuGet Tool Installer__ task
 ![NuGet](media/06_22_07.png)
 
 ### npm build task updates
-Whether you’re building your npm project on Linux, macOS, or Windows, the new __NPM__ build task will accommodate. We have also reorganized the task to make both __npm install__ and __npm publish__ easier. For __install__ and __publish__, we have simplified credential acquisition so that credentials for registries listed in your project’s .npmrc file can be safely stored in a [service endpoint](https://visualstudio.microsoft.com/docs/build/concepts/library/service-endpoints). Alternatively, if you’re using a VSTS feed, we have a picker that will let you select a feed, and then we will generate a .npmrc with requisite credentials that are used by the build agent.
+Whether you’re building your npm project on Linux, macOS, or Windows, the new __NPM__ build task will accommodate. We have also reorganized the task to make both __npm install__ and __npm publish__ easier. For __install__ and __publish__, we have simplified credential acquisition so that credentials for registries listed in your project’s .npmrc file can be safely stored in a [service endpoint](/azure/devops/pipelines/library/service-endpoints). Alternatively, if you’re using a VSTS feed, we have a picker that will let you select a feed, and then we will generate a .npmrc with requisite credentials that are used by the build agent.
 
 ### Working outside your account/collection
 It’s now easier to work with feeds outside your VSTS account, whether they’re __Package Management__ feeds in another VSTS account or TFS server or non-Package Management feeds like NuGet.org/npmjs.com, Artifactory, or MyGet. Dedicated __Service Endpoint__ types for NuGet, npm, and Maven make it easy to enter the correct credentials and enable the build tasks to work seamlessly across package download and package push operations.
@@ -249,7 +249,7 @@ Unlike __NuGet__ and __npm__, the __Maven__ and __dotnet__ build tasks did not p
 Now any Project Collect Administrator, not just the account owner, can make the first Marketplace purchase. This makes it easier for accounts with multiple Project Collection Administrators to pay for VSTS.
 
 ## Deep link to remove your spending limit easily during a Marketplace purchase
-If you want to use the Azure subscription that came with your Visual Studio or MSDN subscription to pay for Marketplace purchases, you need to remove your spending limit and add a credit card. With this release, we’ve added a deep link to make it easy to remove the spending limit for your subscription. We also check to make sure you remove the limit indefinitely, so your Marketplace purchases won’t be interrupted. For more information, see [How to set up billing Q&A](https://visualstudio.microsoft.com/docs/setup-admin/team-services/set-up-billing-for-your-account-vs#q-which-azure-subscriptions-can-i-link-to-my-team-services-account-and-use-for-billing).
+If you want to use the Azure subscription that came with your Visual Studio or MSDN subscription to pay for Marketplace purchases, you need to remove your spending limit and add a credit card. With this release, we’ve added a deep link to make it easy to remove the spending limit for your subscription. We also check to make sure you remove the limit indefinitely, so your Marketplace purchases won’t be interrupted. For more information, see [How to set up billing Q&A](/azure/devops/organizations/billing/set-up-billing-for-your-organization-vs).
 
 ![deep link to remove spending limit](media/06_22_19.png)
 

Diff for: release-notes/2017/nov-28-vsts.md

@@ -124,7 +124,7 @@ To learn more, see the [VSTS CLI docs](/cli/vsts/). To view the source, visit th
 
 ### Query last run by information
 
-As your project’s **Shared Queries** tree grows, it can be difficult to determine that a query is no longer being used and can be deleted. To help you manage your **Shared Queries**, we have added two new pieces of metadata to our [query REST APIs](https://visualstudio.microsoft.com/docs/integrate/api/wit/queries#get-a-query-or-folder), last executed by and last executed date, so that you can write clean-up scripts to delete stale queries.
+As your project’s **Shared Queries** tree grows, it can be difficult to determine that a query is no longer being used and can be deleted. To help you manage your **Shared Queries**, we have added two new pieces of metadata to our query REST APIs, last executed by and last executed date, so that you can write clean-up scripts to delete stale queries.
 
 ### Create work items from the Queries hub
 
@@ -149,7 +149,7 @@ You can now expand or collapse all the items on the sprint **Task board** with j
 
 Often, when migrating work items from another source, organizations want to retain all the original properties of the work item. For example, you may want to create a bug that retains the original created date and created by values from the system where it originated.
 
-The API to [update a work item](https://visualstudio.microsoft.com/docs/integrate/api/wit/work-items#make-an-update-bypassing-rules) has a bypassrule flag to enable that scenario. Previously the identity who made that API request had to be member of the Project Collection Administrators group. With this deployment we have added a permission at the project level to execute the API with the bypassrule flag.
+The API to update a work item has a bypassrule flag to enable that scenario. Previously the identity who made that API request had to be member of the Project Collection Administrators group. With this deployment we have added a permission at the project level to execute the API with the bypassrule flag.
 
 > [!div class="mx-imgBorder"]
 > ![Grant bypassrule](media/126_03.png)

Diff for: release-notes/2018/feb-14-vsts.md

@@ -165,7 +165,7 @@ If you are managing permissions through Azure Active Directory (Azure AD) group
 
 ### Manage users with Graph REST APIs Public Preview
 
-The Graph REST API resources allow developers to write applications that manage users, groups, and group memberships. The set of APIs cover key user management scenarios including adding a Microsoft Account (MSA) or Azure Active Directory (Azure AD) user to VSTS, creating a VSTS group, and adding/removing members from a VSTS group. See the Graph REST API [documentation](https://visualstudio.microsoft.com/docs/integrate/api/graph/overview) and [samples](https://github.com/Microsoft/vsts-dotnet-samples) for more information.
+The Graph REST API resources allow developers to write applications that manage users, groups, and group memberships. The set of APIs cover key user management scenarios including adding a Microsoft Account (MSA) or Azure Active Directory (Azure AD) user to VSTS, creating a VSTS group, and adding/removing members from a VSTS group. See the Graph REST API [documentation](/azure/devops/integrate/) and [samples](https://github.com/Microsoft/vsts-dotnet-samples) for more information.
 
 ### Leave account
 

Diff for: release-notes/2018/jun-19-vsts.md

@@ -186,7 +186,7 @@ In order to enhance end-to-end traceability, you can see all the commits that we
 
 ### Use upstream sources in legacy feeds
 
-Until now, [legacy feeds](/azure/devops/artifacts/reference/feed-upgrade-learn-more?view=azure-devops&preserve-view=true) could not use the nuget.org upstream source or take advantage of improvements made to the npmjs.com upstream source. With this update, you can upgrade a legacy feed and use those features. Look for the banner above your feed’s packages for more information, including behavior changes you should be aware of before upgrading.
+Until now, legacy feeds could not use the nuget.org upstream source or take advantage of improvements made to the npmjs.com upstream source. With this update, you can upgrade a legacy feed and use those features. Look for the banner above your feed’s packages for more information, including behavior changes you should be aware of before upgrading.
 
 ### Use arbitrary public npm feeds as upstream sources
 

Diff for: release-notes/2018/mar-05-vsts.md

@@ -89,7 +89,7 @@ Previously, as part of a deployment phase, you could choose to either download a
 
 ### Improve code quality with the latest extensions from SonarSource
 
-SonarSource recently released an updated [SonarQube extension](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarqube) and a new [SonarCloud extension](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarcloud), which enable static code analysis for numerous languages. The VSTS Gradle and Maven tasks take advantage of these extensions for Java builds in particular. Just enable **Run SonarQube or SonarCloud Analysis** on version 2.* of the Gradle or Maven task, then add the **Prepare** and **Publish** SonarQube/SonarCloud tasks as shown below. See the [Analyzing with SonarQube](https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Extension+for+VSTS-TFS) documentation for more information.
+SonarSource recently released an updated [SonarQube extension](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarqube) and a new [SonarCloud extension](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarcloud), which enable static code analysis for numerous languages. The VSTS Gradle and Maven tasks take advantage of these extensions for Java builds in particular. Just enable **Run SonarQube or SonarCloud Analysis** on version 2.* of the Gradle or Maven task, then add the **Prepare** and **Publish** SonarQube/SonarCloud tasks as shown below.
 
 > [!div class="mx-imgBorder"]
 > ![Tasks for Gradle and Maven](media/131_03.png)