Migrate several blog links to new devblogs.microsoft.com

blogs/2017/10/24/theicon.md

@@ -32,7 +32,7 @@ For complete transparency, we want to share some history as we think it helps to
 
 ## Welcome to the family
 
-Back in [March](https://blogs.msdn.microsoft.com/visualstudio/2017/03/08/iterations-on-infinity/), we (the broader Visual Studio team) set out to create a "family" feel across all of the developer tools we produce. If you read that blog post again, you can see that we had to work within a set of "challenging" corporate branding guidelines (for example, a single color).
+Back in [March](https://devblogs.microsoft.com/visualstudio/iterations-on-infinity), we (the broader Visual Studio team) set out to create a "family" feel across all of the developer tools we produce. If you read that blog post again, you can see that we had to work within a set of "challenging" corporate branding guidelines (for example, a single color).
 
 It is easy to blame the guidelines, but at the same time, having a set of products that are easily and broadly recognizable is a valuable asset. Instead, we took on the challenge of working within the constraints while also working across the company to evolve the guidelines and address the problems we faced.
 

blogs/2018/07/12/introducing-logpoints-and-auto-attach.md

@@ -112,7 +112,7 @@ A Logpoint is a breakpoint variant that does not "break" into the debugger but i
 
 ![Logpoints](logpoints.gif)
 
-The concept for Logpoints isn't new, and over the past few years, we have seen different flavors of this concept in tools like [Visual Studio](https://codewala.net/2018/01/25/tracepoint-an-awsome-feature-of-visual-studio/), [Edge DevTools](https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide/debugger) and [GDB](https://sourceware.org/gdb/onlinedocs/gdb/Tracepoints.html) under several names such as [Tracepoints](https://blogs.msdn.microsoft.com/devops/2013/10/10/tracepoints/) and [Logpoints](https://blogs.msdn.microsoft.com/visualstudio/2017/09/13/debug-live-apps-in-azure-with-the-snappoints-and-logpoints-preview/).
+The concept for Logpoints isn't new, and over the past few years, we have seen different flavors of this concept in tools like [Visual Studio](https://codewala.net/2018/01/25/tracepoint-an-awsome-feature-of-visual-studio/), [Edge DevTools](https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide/debugger) and [GDB](https://sourceware.org/gdb/onlinedocs/gdb/Tracepoints.html) under several names such as Tracepoints and [Logpoints](https://devblogs.microsoft.com/visualstudio/debug-live-apps-in-azure-with-the-snappoints-and-logpoints-preview).
 
 ### Why and when to use Logpoints?
 

blogs/2018/08/07/debug-adapter-protocol-website.md

@@ -92,7 +92,7 @@ These characteristics are similar to those of the Language Server Protocol publi
 
 Now we have followed suit for the Debug Adapter Protocol by moving the DAP specification from its [old location](https://github.com/Microsoft/vscode-debugadapter-node) to a new website [https://microsoft.github.io/debug-adapter-protocol](https://microsoft.github.io/debug-adapter-protocol/) and a corresponding repository [https://github.com/Microsoft/debug-adapter-protocol](https://github.com/Microsoft/debug-adapter-protocol).
 
-This move should emphasize that the Debug Adapter Protocol in not specific to Visual Studio Code. For example, Visual Studio is now also [supporting this protocol](https://blogs.msdn.microsoft.com/visualstudio/2018/03/26/adding-support-for-debug-adapters-to-visual-studio-ide/).
+This move should emphasize that the Debug Adapter Protocol in not specific to Visual Studio Code. For example, Visual Studio is now also [supporting this protocol](https://devblogs.microsoft.com/visualstudio/adding-support-for-debug-adapters-to-visual-studio-ide).
 
 In the new location we provide:
 

docs/editor/versioncontrol.md

@@ -224,7 +224,7 @@ You can always set up a [credential helper](https://help.github.com/articles/cac
 
 ### How can I sign into Git with my Azure DevOps organization which requires multi-factor authentication?
 
-There are now [Git credential helpers](https://blogs.msdn.com/b/visualstudioalm/archive/2015/11/18/visual-studio-team-services-git-credential-manager-for-mac-and-linux.aspx) that assist with multi-factor authentication. You can download these from [Git Credential Manager for Mac and Linux](https://github.com/Microsoft/Git-Credential-Manager-for-Mac-and-Linux) and [Git Credential Manager for Windows](https://github.com/Microsoft/Git-Credential-Manager-for-Windows).
+There are now [Git credential helpers](https://devblogs.microsoft.com/devops/git-credential-manager-for-mac-and-linux) that assist with multi-factor authentication. You can download these from [Git Credential Manager for Mac and Linux](https://github.com/Microsoft/Git-Credential-Manager-for-Mac-and-Linux) and [Git Credential Manager for Windows](https://github.com/Microsoft/Git-Credential-Manager-for-Windows).
 
 ### I have GitHub Desktop installed on my computer but VS Code ignores it
 

docs/java/java-faq.md

@@ -29,7 +29,7 @@ Sure. [Keymap extensions](/docs/getstarted/keybindings.md#keymap-extensions) in
 
 ## Where can I find the latest progress of Java support on Visual Studio Code?
 
-We're currently publishing our updates at [The Visual Studio Blog](https://blogs.msdn.microsoft.com/visualstudio/tag/java/), which will report all our major features and improvements.
+We're currently publishing our updates at [The Visual Studio Blog](https://devblogs.microsoft.com/visualstudio/tag/java/), which will report all our major features and improvements.
 
 While you're using Java within VS Code, you might also see a *Release Notes* once you update the [Java Extension Pack](https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack). That will give you an overview on the notable updates included in the extensions.
 

release-notes/v1_24.md

@@ -488,7 +488,7 @@ Meanwhile, Vetur now has End-To-End test coverage and centralized file system ac
 
 ## Engineering
 
-We moved our [continuous integration builds](https://aka.ms/vscode-builds) over to our friends at [Azure DevOps](https://azure.microsoft.com/services/devops/) (👋 shout out to [@chrisrpatterson](https://github.com/chrisrpatterson) & [@lszomoru](https://github.com/lszomoru) for their ongoing support). This was only possible given the DevOps team's work on [public projects](https://blogs.msdn.microsoft.com/devops/2018/04/27/vsts-public-projects-limited-preview/), as well as several other features. Azure DevOps allows us to have a [single YAML based build definition](https://github.com/Microsoft/vscode/blob/master/build/tfs/continuous-build.yml) which targets all our three major platforms: Windows, macOS and Linux.
+We moved our [continuous integration builds](https://aka.ms/vscode-builds) over to our friends at [Azure DevOps](https://azure.microsoft.com/services/devops/) (👋 shout out to [@chrisrpatterson](https://github.com/chrisrpatterson) & [@lszomoru](https://github.com/lszomoru) for their ongoing support). This was only possible given the DevOps team's work on [public projects](https://devblogs.microsoft.com/devops/vsts-public-projects-limited-preview), as well as several other features. Azure DevOps allows us to have a [single YAML based build definition](https://github.com/Microsoft/vscode/blob/master/build/tfs/continuous-build.yml) which targets all our three major platforms: Windows, macOS and Linux.
 
 [![Azure DevOps Builds](images/1_24/vsts.png)](https://aka.ms/vscode-builds)