Merge pull request #79322 from v-thepet/links6-11

PRMerger17 · web-flow · commit 1ec630a775a2 · 2019-06-12T05:43:54.000+08:00
AzureLinkBugs: Fix external links 6/10
diff --git a/articles/azure-monitor/app/status-monitor-v2-detailed-instructions.md b/articles/azure-monitor/app/status-monitor-v2-detailed-instructions.md
@@ -198,7 +198,7 @@ For more information, see [Installing a PowerShell Module](https://docs.microsof
 
 ### Option 2: Unzip and import nupkg manually
 Install the manually downloaded PowerShell module into a PowerShell directory so it will be discoverable by PowerShell sessions.
-For more information, see [Installing a PowerShell Module](https://docs.mircrosoft.com/powershell/developer/module/installing-a-powershell-module).
+For more information, see [Installing a PowerShell Module](https://docs.microsoft.com/powershell/developer/module/installing-a-powershell-module).
 
 If you're installing the module into any other directory, manually import the module by using [Import-Module](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/import-module?view=powershell-6).
 
diff --git a/articles/expressroute/expressroute-locations.md b/articles/expressroute/expressroute-locations.md
@@ -83,7 +83,7 @@ The following table shows locations by service provider. If you want to view ava
 | **[CenturyLink Cloud Connect](https://www.centurylink.com/cloudconnect)** |Supported |Supported |Las Vegas, New York, San Antonio, Silicon Valley, Tokyo, Toronto |
 | **Chief Telecom** |Supported |Supported |Hong Kong, Taipei |
 | **China Telecom Global** |Supported |Not Supported |Hong Kong SAR |
-| **[Cologix](https://www.cologix.com/solutions/cloud-connect/public-clouds/microsoft-cloud/)** |Supported |Supported |Chicago, Dallas, Montreal, Toronto, Washington DC |
+| **[Cologix](https://www.cologix.com/hyperscale/microsoft-azure/)** |Supported |Supported |Chicago, Dallas, Montreal, Toronto, Washington DC |
 | **[Colt](https://www.colt.net/uk/en/news/colt-announces-dedicated-cloud-access-for-microsoft-azure-services-en.htm)** |Supported |Supported |Amsterdam, Dublin, London, Newport, Paris, Singapore2, Tokyo |
 | **[Comcast](https://business.comcast.com/landingpage/microsoft-azure)** |Supported |Supported |Chicago, Silicon Valley, Washington DC |
 | **[CoreSite](https://www.coresite.com/solutions/cloud-services/public-cloud-providers/microsoft-azure-expressroute)** |Supported |Supported |Chicago, Denver, Los Angeles, New York, Silicon Valley, Silicon Valley2, Washington DC, Washington DC2 |
diff --git a/articles/hdinsight/storm/apache-storm-develop-java-topology.md b/articles/hdinsight/storm/apache-storm-develop-java-topology.md
@@ -14,7 +14,7 @@ ms.custom: H1Hack27Feb2017,hdinsightactive,hdiseo17may2017
 
 # Create an Apache Storm topology in Java
 
-Learn how to create a Java-based topology for [Apache Storm](https://storm.apache.org/). Here, you create a Storm topology that implements a word-count application. You use [Apache Maven](https://maven.apache.org/) to build and package the project. Then, you learn how to define the topology using the [Apache Storm Flux](https://storm.apache.org/releases/2.0.0-SNAPSHOT/flux.html) framework.
+Learn how to create a Java-based topology for [Apache Storm](https://storm.apache.org/). Here, you create a Storm topology that implements a word-count application. You use [Apache Maven](https://maven.apache.org/) to build and package the project. Then, you learn how to define the topology using the [Apache Storm Flux](https://storm.apache.org/releases/2.0.0/flux.html) framework.
 
 After completing the steps in this document, you can deploy the topology to Apache Storm on HDInsight.
 
@@ -617,7 +617,7 @@ There is a 5-second interval between emission of words and counts. The **WordCou
 
 ## Convert the topology to Flux
 
-[Flux](https://storm.apache.org/releases/2.0.0-SNAPSHOT/flux.html) is a new framework available with Storm 0.10.0 and higher, which allows you to separate configuration from implementation. Your components are still defined in Java, but the topology is defined using a YAML file. You can package a default topology definition with your project, or use a standalone file when submitting the topology. When submitting the topology to Storm, you can use environment variables or configuration files to populate values in the YAML topology definition.
+[Flux](https://storm.apache.org/releases/2.0.0/flux.html) is a new framework available with Storm 0.10.0 and higher, which allows you to separate configuration from implementation. Your components are still defined in Java, but the topology is defined using a YAML file. You can package a default topology definition with your project, or use a standalone file when submitting the topology. When submitting the topology to Storm, you can use environment variables or configuration files to populate values in the YAML topology definition.
 
 The YAML file defines the components to use for the topology and the data flow between them. You can include a YAML file as part of the jar file or you can use an external YAML file.
 
diff --git a/articles/iot-edge/how-to-install-iot-edge-windows-server-vm.md b/articles/iot-edge/how-to-install-iot-edge-windows-server-vm.md
@@ -16,13 +16,13 @@ The Azure IoT Edge runtime is what turns a device into an IoT Edge device. The r
 
 To learn more about how the IoT Edge runtime works and what components are included, see [Understand the Azure IoT Edge runtime and its architecture](iot-edge-runtime.md).
 
-This article lists the steps to run the Azure IoT Edge runtime on a Windows Server 2019 virtual machine using the [Windows Server](https://azuremarketplace.microsoft.com/marketplace/apps/Microsoft.WindowsServer?tab=Overview) Azure Marketplace offer. Follow the instructions at [Install the Azure IoT Edge runtime](how-to-install-iot-edge-windows.md) on Windows for use with other versions.
+This article lists the steps to run the Azure IoT Edge runtime on a Windows Server 2019 virtual machine using the [Windows Server](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftwindowsserver.windowsserver?tab=Overview) Azure Marketplace offer. Follow the instructions at [Install the Azure IoT Edge runtime](how-to-install-iot-edge-windows.md) on Windows for use with other versions.
 
 > [!NOTE]
 > The IoT Edge runtime on Windows Server is in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 ## Deploy from the Azure Marketplace
-1.	Navigate to the [Windows Server](https://azuremarketplace.microsoft.com/marketplace/apps/Microsoft.WindowsServer?tab=Overview) Azure Marketplace offer or by searching “Windows Server” on [Azure Marketplace](https://azuremarketplace.microsoft.com/)
+1.	Navigate to the [Windows Server](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftwindowsserver.windowsserver?tab=Overview) Azure Marketplace offer or by searching “Windows Server” on [Azure Marketplace](https://azuremarketplace.microsoft.com/)
 2.	Select **GET IT NOW** 
 3.  In **Software plan**, find "Windows Server 2019 Datacenter Server Core with Containers" and then select **Continue** on the next dialog.
     * You can also use these instructions for other versions of Windows Server with Containers
diff --git a/articles/marketplace/cloud-partner-portal/virtual-machine/cpp-create-vhd.md b/articles/marketplace/cloud-partner-portal/virtual-machine/cpp-create-vhd.md
@@ -22,7 +22,7 @@ This article details the steps required to create a virtual hard disk (VHD) for
 The operating system VHD for your VM image must be based on an Azure-approved base image that contains Windows Server or SQL Server.
 To begin, create a VM from one of the following images, located at the Microsoft Azure portal:
 
--	Windows Server ([2016](https://www.microsoft.com/evalcenter/evaluate-windows-server-2016), [2012 R2 Datacenter](https://azure.microsoft.com/marketplace/partners/microsoft/windowsserver2012r2datacenter/), [2012 Datacenter](https://azure.microsoft.com/marketplace/partners/microsoft/windowsserver2012datacenter/), [2008 R2 SP1](https://azure.microsoft.com/marketplace/partners/microsoft/windowsserver2008r2sp1/))
+-	Windows Server ([2016](https://www.microsoft.com/evalcenter/evaluate-windows-server-2016), [2012 R2 Datacenter](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftwindowsserver.windowsserver?tab=Overview), [2012 Datacenter](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftwindowsserver.windowsserver?tab=Overview), [2008 R2 SP1](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftwindowsserver.windowsserver?tab=Overview))
 -	[SQL Server 2014](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-server-pricing-guidance) (Enterprise, Standard, Web)
 -	[SQL Server 2012 SP2](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-server-pricing-guidance) (Enterprise, Standard, Web)
 
diff --git a/articles/notification-hubs/notification-hubs-android-push-notification-google-gcm-get-started.md b/articles/notification-hubs/notification-hubs-android-push-notification-google-gcm-get-started.md
@@ -106,7 +106,7 @@ Your notification hub is now configured to work with GCM, and you have the conne
 
 ### Updating the project's AndroidManifest.xml
 
-1. To support GCM, implement an Instance ID listener service in the code that is used to [obtain registration tokens](https://developers.google.com/cloud-messaging/android/client#sample-register) using [Google's Instance ID API](https://developers.google.com/instance-id/). In this tutorial, the name of the class is `MyInstanceIDService`.
+1. To support GCM, implement an Instance ID listener service in the code that is used to [obtain registration tokens](https://developers.google.com/cloud-messaging/) using [Google's Instance ID API](https://developers.google.com/instance-id/). In this tutorial, the name of the class is `MyInstanceIDService`.
 
     Add the following service definition to the AndroidManifest.xml file, inside the `<application>` tag. Replace the `<your package>` placeholder with your actual package name shown at the top of the `AndroidManifest.xml` file.
   
@@ -140,7 +140,7 @@ Your notification hub is now configured to work with GCM, and you have the conne
     ```
 4. Add the following necessary GCM permissions below the  `</application>` tag. Replace `<your package>` with the package name shown at the top of the `AndroidManifest.xml` file.
 
-    For more information on these permissions, see [Setup a GCM Client app for Android](https://developers.google.com/cloud-messaging/android/client#manifest).
+    For more information on these permissions, see [Setup a GCM Client app for Android](https://developers.google.com/cloud-messaging/).
 
     ```xml
     <uses-permission android:name="android.permission.INTERNET"/>
diff --git a/articles/notification-hubs/notification-hubs-nodejs-push-notification-tutorial.md b/articles/notification-hubs/notification-hubs-nodejs-push-notification-tutorial.md
@@ -103,7 +103,7 @@ The `GcmService` object provides a `send` method that can be used to send push n
 - **Payload** - the message's JSON or raw string payload.
 - **Callback** - the callback function.
 
-For more information on the payload format, see the **Payload** section of the [Implementing GCM Server](https://developer.android.com/google/gcm/server.html#payload) document.
+For more information on the payload format, see the **Payload** section of the [Implementing GCM Server](https://developers.google.com/cloud-messaging/) document.
 
 The following code uses the `GcmService` instance exposed by the `NotificationHubService` to send a push notification to all registered clients.
 
diff --git a/articles/spatial-anchors/concepts/authentication.md b/articles/spatial-anchors/concepts/authentication.md
@@ -51,7 +51,7 @@ Once that is done, the SDK will handle the exchange of the account key for an ac
 
 ## Azure AD user authentication
 
-For applications targeting Azure Active Directory users, the recommended approach is to use an Azure AD token for the user, which you can obtain using the ADAL library as described in the following documentation: https://docs.microsoft.com/azure/active-directory/develop/v1-overview; you should follow the steps listed under “Quick starts”, which include:
+For applications targeting Azure Active Directory users, the recommended approach is to use an Azure AD token for the user, which you can obtain using the ADAL library as described in the following documentation: [https://docs.microsoft.com/azure/active-directory/develop/v1-overview](../../active-directory/develop/v1-overview.md); you should follow the steps listed under “Quick starts”, which include:
 
 1. Configuration in Azure portal
     1.	Register your application in Azure AD as **Native application**. As part of registering, you will need to determine whether your application should be multi-tenant or not, and provide the redirect URLs allowed for your application.  
@@ -84,7 +84,7 @@ The recommended option to deploy apps leveraging Azure Spatial Anchors to produc
 
 Here, it is assumed that your app uses its own mechanism (for example: Microsoft account, PlayFab, Facebook, Google ID, custom username/password, etc.) to authenticate to its backend service. Once your users are authenticated to your backend service, that service can retrieve an Azure AD token, exchange it for an access token for Azure Spatial Anchors, and return it back to your client application.
 
-The Azure AD access token is retrieved using the ADAL library as described in the following documentation: https://docs.microsoft.com/azure/active-directory/develop/v1-overview; you should follow the steps listed under “Quick starts”, which include:
+The Azure AD access token is retrieved using the ADAL library as described in the following documentation: [https://docs.microsoft.com/azure/active-directory/develop/v1-overview](../../active-directory/develop/v1-overview.md); you should follow the steps listed under “Quick starts”, which include:
 
 1.	Configuration in Azure portal:
     1.	Register your application in Azure AD:
diff --git a/articles/virtual-machines/linux/sizes-hpc.md b/articles/virtual-machines/linux/sizes-hpc.md
@@ -69,7 +69,7 @@ The Azure Marketplace has many Linux distributions that support RDMA connectivit
 
   [!INCLUDE [virtual-machines-common-ubuntu-rdma](../../../includes/virtual-machines-common-ubuntu-rdma.md)]  
 
-  For more details on enabling InfiniBand, setting up MPI, see [Enable InfiniBand](https://docs.microsoft.com/azure/virtual-machines/workloads/hpc/enable-infiniband-with-sriov).
+  For more details on enabling InfiniBand, setting up MPI, see [Enable InfiniBand](../workloads/hpc/enable-infiniband.md).
 
 
 ### Cluster configuration options
@@ -104,5 +104,5 @@ Azure provides several options to create clusters of Linux HPC VMs that can comm
 
 ## Next steps
 
-- Learn more about how to setup, optimize and scale [HPC workloads](https://docs.microsoft.com/azure/virtual-machines/workloads/hpc) on Azure.
+- Learn more about how to setup, optimize and scale [HPC workloads](../workloads/hpc/configure.md) on Azure.
 - Learn more about how [Azure compute units (ACU)](acu.md) can help you compare compute performance across Azure SKUs.
diff --git a/articles/virtual-machines/windows/storage-performance.md b/articles/virtual-machines/windows/storage-performance.md
@@ -20,7 +20,7 @@ Lsv2-series virtual machines support a variety of workloads that need high I/O a
 
 The design of the Lsv2-series Virtual Machines (VMs) maximizes the AMD EPYC™ 7551 processor to provide the best performance between the processor, memory, NVMe devices, and the VMs. In addition to maximizing the hardware performance, Lsv2-series VMs are designed to work with the needs of Windows and Linux operating systems for better performance with the hardware and the software.
 
-Tuning the software and hardware resulted in the optimized version of [Windows Server 2019 Datacenter](https://azuremarketplace.microsoft.com/marketplace/apps/Microsoft.WindowsServer?tab=Overview), released in early December 2018 to the Azure Marketplace, which supports maximum performance on the NVMe devices in Lsv2-series VMs.
+Tuning the software and hardware resulted in the optimized version of [Windows Server 2019 Datacenter](https://azuremarketplace.microsoft.com/marketplace/apps/microsoftwindowsserver.windowsserver?tab=Overview), released in early December 2018 to the Azure Marketplace, which supports maximum performance on the NVMe devices in Lsv2-series VMs.
 
 This article provides tips and suggestions to ensure your workloads and applications achieve the maximum performance designed into the VMs. The information on this page will be continuously updated as more Lsv2 optimized images are added to the Azure Marketplace.
 
