Merge pull request #105882 from john-par/1668809-clean-up-broken-azure-docs-pr-links-02-27

megvanhuygen · web-flow · commit ada664e850bd · 2020-02-27T14:29:03.000-08:00
1668809, clean up broken azure docs pr links 02-27
diff --git a/articles/backup/sap-hana-db-about.md b/articles/backup/sap-hana-db-about.md
@@ -9,7 +9,7 @@ ms.date: 12/11/2019
 
 SAP HANA databases are mission critical workloads that require a low recovery point objective (RPO) and a fast recovery time objective (RTO). You can now [back up SAP HANA databases running on Azure VMs](https://docs.microsoft.com/azure/backup/tutorial-backup-sap-hana-db) using [Azure Backup](https://docs.microsoft.com/azure/backup/backup-overview).
 
-Azure Backup is [Backint certified](https://www.sap.com/dmc/exp/2013_09_adpd/enEN/#/d/solutions?id=8f3fd455-a2d7-4086-aa28-51d8870acaa5) by SAP, to provide native backup support by leveraging SAP HANA’s native APIs. This offering from Azure Backup aligns with Azure Backup’s mantra of **zero-infrastructure** backups, eliminating the need to deploy and manage backup infrastructure. You can now seamlessly back up and restore SAP HANA databases running on Azure VMs ([M series VMs](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-memory) also supported now!) and leverage enterprise management capabilities that Azure Backup provides.
+Azure Backup is [Backint certified](https://www.sap.com/dmc/exp/2013_09_adpd/enEN/#/d/solutions?id=8f3fd455-a2d7-4086-aa28-51d8870acaa5) by SAP, to provide native backup support by leveraging SAP HANA’s native APIs. This offering from Azure Backup aligns with Azure Backup’s mantra of **zero-infrastructure** backups, eliminating the need to deploy and manage backup infrastructure. You can now seamlessly back up and restore SAP HANA databases running on Azure VMs ([M series VMs](../virtual-machines/m-series.md) also supported now!) and leverage enterprise management capabilities that Azure Backup provides.
 
 ## Added value
 
diff --git a/articles/cognitive-services/LUIS/luis-language-support.md b/articles/cognitive-services/LUIS/luis-language-support.md
@@ -56,7 +56,7 @@ Language support varies for [prebuilt entities](luis-reference-prebuilt-entities
 [!INCLUDE [Text Analytics support notes](includes/text-analytics-support-notes.md)]
 
 ### Speech API supported languages
-See Speech [Supported languages](https://docs.microsoft.com/azure/cognitive-services/Speech/api-reference-rest/supportedlanguages##interactive-and-dictation-mode) for Speech dictation mode languages.
+See Speech [Supported languages](../speech-service/speech-to-text.md) for Speech dictation mode languages.
 
 ### Bing Spell Check supported languages
 See Bing Spell Check [Supported languages](https://docs.microsoft.com/azure/cognitive-services/bing-spell-check/bing-spell-check-supported-languages) for a list of supported languages and status.
diff --git a/articles/data-explorer/ingest-data-streaming.md b/articles/data-explorer/ingest-data-streaming.md
@@ -75,7 +75,7 @@ There are two supported streaming ingestion types:
 
 Streaming ingestion doesn't support the following features:
 * [Database cursors](/azure/kusto/management/databasecursor).
-* [Data mapping](/azure/kusto/management/mappings). Only [pre-created](/azure/kusto/management/tables#create-ingestion-mapping) data mapping is supported. 
+* [Data mapping](/azure/kusto/management/mappings). Only [pre-created](/azure/kusto/management/create-ingestion-mapping-command) data mapping is supported. 
 
 ## Next steps
 
diff --git a/articles/migrate/common-questions-discovery-assessment.md b/articles/migrate/common-questions-discovery-assessment.md
@@ -96,7 +96,7 @@ No, the dependency visualization can't be exported. However, Azure Migrate uses
 
 ## Can I automate  MMA/Dependency agent installation?
 
-Use this [script to install the Dependency agent](../azure-monitor/insights/vminsights-enable-hybrid-cloud.md#installation-script-examples). Follow these [instructions to install MMA](https://docs.microsoft.com/azure/azure-monitor/platform/log-analytics-agent#install-and-configure-agent) by using the command line or automation. For
+Use this [script to install the Dependency agent](../azure-monitor/insights/vminsights-enable-hybrid-cloud.md#installation-script-examples). Follow these [instructions to install MMA](../azure-monitor/platform/log-analytics-agent.md#installation-and-configuration) by using the command line or automation. For
 MMA, use [this script](https://gallery.technet.microsoft.com/scriptcenter/Install-OMS-Agent-with-2c9c99ab).
 
 In addition to scripts, you can also use deployment tools like Microsoft Endpoint Configuration Manager and [Intigua](https://www.intigua.com/getting-started-intigua-for-azure-migration) to deploy the agents.
diff --git a/articles/migrate/how-to-create-group-machine-dependencies.md b/articles/migrate/how-to-create-group-machine-dependencies.md
@@ -71,7 +71,7 @@ To install the agent on a Windows machine:
 5. Click **Add** to add a new Log Analytics workspace. Paste in the workspace ID and key that you copied from the portal. Click **Next**.
 
 You can install the agent from the command line or using an automated method such as Configuration Manager or [Intigua](https://go.microsoft.com/fwlink/?linkid=2104196).
-- [Learn more](https://docs.microsoft.com/azure/azure-monitor/platform/log-analytics-agent#install-and-configure-agent) about using these methods to install the MMA agent.
+- [Learn more](../azure-monitor/platform/log-analytics-agent.md#installation-and-configuration) about using these methods to install the MMA agent.
 - The MMA agent can also be installed using this [script](https://go.microsoft.com/fwlink/?linkid=2104394).
 - [Learn more](https://docs.microsoft.com/azure/azure-monitor/platform/log-analytics-agent#supported-windows-operating-systems) about the Windows operating systems supported by MMA.
 
diff --git a/articles/migrate/migrate-v1.md b/articles/migrate/migrate-v1.md
@@ -225,7 +225,7 @@ To install the agent on a Windows machine:
 4. In **Agent Setup Options**, select **Azure Log Analytics** > **Next**.
 5. Click **Add** to add a new Log Analytics workspace. Paste in the workspace ID and key that you copied from the portal. Click **Next**.
 
-You can install the agent from the command line or using an automated method such as Configuration Manager. [Learn more](https://docs.microsoft.com/azure/azure-monitor/platform/log-analytics-agent#install-and-configure-agent) about using these methods to install the MMA agent.
+You can install the agent from the command line or using an automated method such as Configuration Manager. [Learn more](../azure-monitor/platform/log-analytics-agent.md#installation-and-configuration) about using these methods to install the MMA agent.
 
 #### Install the MMA agent on a Linux machine
 
diff --git a/articles/service-fabric/service-fabric-tutorial-scale-cluster.md b/articles/service-fabric/service-fabric-tutorial-scale-cluster.md
@@ -842,7 +842,7 @@ After creating a Service Fabric cluster, you can scale a cluster node type verti
 
 [Export a template and parameters file](#export-the-template-for-the-resource-group) from the resource group for the most recent deployment.  Open the *parameters.json* file.  If you deployed the cluster using the [sample template][template] in this tutorial, there are three node types in the cluster.  
 
-The size of the VMs in the second node type is set in the *vmNodeType1Size* parameter.  Change the *vmNodeType1Size* parameter value from Standard_D2_V2 to [Standard_D3_V2](/azure/virtual-machines/windows/sizes-general#dv2-series), which doubles the resources of each VM instance.
+The size of the VMs in the second node type is set in the *vmNodeType1Size* parameter.  Change the *vmNodeType1Size* parameter value from Standard_D2_V2 to [Standard_D3_V2](../virtual-machines/dv2-dsv2-series.md), which doubles the resources of each VM instance.
 
 The VM SKU for all three node types is set in the *vmImageSku* parameter.  Again, changing the VM SKU of a node type should be approached with caution and is not recommended for the primary node type.
 
diff --git a/articles/spring-cloud/diagnostic-services.md b/articles/spring-cloud/diagnostic-services.md
@@ -27,7 +27,7 @@ Choose the log category and metric category you want to monitor.
 
 ## Metrics
 
-For a complete list of metrics, see [Spring Cloud Metrics](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-concept-metrics#user-portal-metrics-options)
+For a complete list of metrics, see [Spring Cloud Metrics](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-concept-metrics#user-metrics-options).
 
 To get started, enable one of these services to receive the data. To learn about configuring Log Analytics, see [Get started with Log Analytics in Azure Monitor](../azure-monitor/log-query/get-started-portal.md). 
 
diff --git a/articles/spring-cloud/spring-cloud-tutorial-alerts-action-groups.md b/articles/spring-cloud/spring-cloud-tutorial-alerts-action-groups.md
@@ -81,7 +81,7 @@ To configure an **Alert**, navigate back to the **Alerts** page, and click **Man
 
 1. Click **Done**.
 
-For details of the conditions available to monitor, see [User portal metrics options](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-concept-metrics#user-portal-metrics-options).
+For details of the conditions available to monitor, see [User portal metrics options](spring-cloud-concept-metrics.md#user-metrics-options).
 
  Under **ACTIONS**, click **Select action group**. From **ACTIONS** pane select the previously defined **Action Group**.
 
@@ -104,7 +104,7 @@ A rule can also be created using the **Metrics** page:
    ![Screenshot Portal new alert rule](media/alerts-action-groups/alerts-5.png)
 
 ## Next steps
-* [User portal metrics options](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-concept-metrics#user-portal-metrics-options)
+* [User portal metrics options](spring-cloud-concept-metrics.md#user-metrics-options)
 * [Create and manage action groups in the Azure portal](https://docs.microsoft.com/azure/azure-monitor/platform/action-groups)
 * [SMS Alert Behavior in Action Groups](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-sms-behavior)
 * [Tutorial: Using Distributed Tracing with Azure Spring Cloud](https://docs.microsoft.com/azure/spring-cloud/spring-cloud-tutorial-distributed-tracing)
diff --git a/articles/virtual-machines/linux/generation-2.md b/articles/virtual-machines/linux/generation-2.md
@@ -30,18 +30,18 @@ Generation 2 VMs use the new UEFI-based boot architecture rather than the BIOS-b
 Generation 1 VMs are supported by all VM sizes in Azure (except for Mv2-series VMs). Azure now offers generation 2 support for the following selected VM series:
 
 * [B-series](https://docs.microsoft.com/azure/virtual-machines/linux/b-series-burstable)
-* [DC-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-general#dc-series)
-* [Dsv2-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-general#dsv2-series) and [Dsv3-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-general#dsv3-series-1)
-* [Esv3-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-memory#esv3-series)
-* [Fsv2-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-compute#fsv2-series-1)
+* [DC-series](../dcv2-series.md)
+* [DSv2-series](../dv2-dsv2-series.md) and [Dsv3-series](../dv3-dsv3-series.md)
+* [Esv3-series](../ev3-esv3-series.md)
+* [Fsv2-series](../fsv2-series.md)
 * [GS-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-previous-gen#gs-series)
-* [HB-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-hpc#hb-series)
-* [HC-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-hpc#hc-series)
-* [Ls-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-previous-gen#ls-series) and [Lsv2-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-storage#lsv2-series)
-* [Mv2-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-memory#mv2-series)
-* [NCv2-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-gpu#ncv2-series) and [NCv3-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-gpu#ncv3-series)
-* [ND-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-gpu#nd-series)
-* [NVv3-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-gpu#nvv3-series--1)
+* [HB-series](../hb-series.md)
+* [HC-series](../hc-series.md)
+* [Ls-series](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-previous-gen#ls-series) and [Lsv2-series](../lsv2-series.md)
+* [Mv2-series](../mv2-series.md)
+* [NCv2-series](../ncv2-series.md) and [NCv3-series](../ncv3-series.md)
+* [ND-series](../nd-series.md)
+* [NVv3-series](../nvv3-series.md)
 
 > [!NOTE]
 > The usage of generation 2 VM images for Mv2-series VMs is generally available since the Mv2-series works with generation 2 VM images exclusively. Generation 1 VM images are not supported on Mv2-series VMs. 
diff --git a/articles/virtual-machines/troubleshooting/linux-index.yml b/articles/virtual-machines/troubleshooting/linux-index.yml
@@ -158,6 +158,6 @@ landingContent:
           - text:  Troubleshoot Azure Backup Server
             url: https://docs.microsoft.com/azure/backup/backup-azure-mabs-troubleshoot
           - text:  Review the features of Azure Backup
-            url: https://docs.microsoft.com/azure/backup/backup-introduction-to-azure-backup#using-premium-storage-vms-with-azure-backup
+            url: https://docs.microsoft.com/azure/backup/backup-introduction-to-azure-backup
           - text:  Understand how to backup Azure virtual machines to Recovery Services vaults
             url: https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm
diff --git a/articles/virtual-machines/windows/generation-2.md b/articles/virtual-machines/windows/generation-2.md
@@ -30,18 +30,18 @@ Generation 2 VMs use the new UEFI-based boot architecture rather than the BIOS-b
 Generation 1 VMs are supported by all VM sizes in Azure (except for Mv2-series VMs). Azure now offers generation 2 support for the following selected VM series:
 
 * [B-series](https://docs.microsoft.com/azure/virtual-machines/windows/b-series-burstable)
-* [DC-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-general#dc-series)
-* [Dsv2-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-general#dsv2-series) and [Dsv3-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-general#dsv3-series-1)
-* [Esv3-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-memory#esv3-series)
-* [Fsv2-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-compute#fsv2-series-1)
+* [DC-series](../dcv2-series.md)
+* [DSv2-series](../dv2-dsv2-series.md) and [Dsv3-series](../dv3-dsv3-series.md)
+* [Esv3-series](../ev3-esv3-series.md)
+* [Fsv2-series](../fsv2-series.md)
 * [GS-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-previous-gen#gs-series)
-* [HB-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-hpc#hb-series)
-* [HC-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-hpc#hc-series)
-* [Ls-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-previous-gen#ls-series) and [Lsv2-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-storage#lsv2-series)
-* [Mv2-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-memory#mv2-series)
-* [NCv2-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-gpu#ncv2-series) and [NCv3-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-gpu#ncv3-series)
-* [ND-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-gpu#nd-series)
-* [NVv3-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-gpu#nvv3-series--1)
+* [HB-series](../hb-series.md)
+* [HC-series](../hc-series.md)
+* [Ls-series](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-previous-gen#ls-series) and [Lsv2-series](../lsv2-series.md)
+* [Mv2-series](../mv2-series.md)
+* [NCv2-series](../ncv2-series.md) and [NCv3-series](../ncv3-series.md)
+* [ND-series](../nd-series.md)
+* [NVv3-series](../nvv3-series.md)
 
 > [!NOTE]
 > The usage of generation 2 VM images for Mv2-series VMs is generally available since the Mv2-series works with generation 2 VM images exclusively. Generation 1 VM images are not supported on Mv2-series VMs. 
diff --git a/articles/virtual-machines/windows/sql/virtual-machines-windows-sql-connect.md b/articles/virtual-machines/windows/sql/virtual-machines-windows-sql-connect.md
@@ -133,7 +133,7 @@ The following table lists the requirements to connect to SQL Server running in a
 
 | Requirement | Description |
 |---|---|
-| [Enable SQL Server Authentication mode](https://docs.microsoft.com/sql/database-engine/configure-windows/change-server-authentication-mode#SSMSProcedure) | SQL Server Authentication is needed to connect to the VM remotely unless you have configured Active Directory on a Virtual Network. |
+| [Enable SQL Server Authentication mode](/sql/database-engine/configure-windows/change-server-authentication-mode#use-ssms) | SQL Server Authentication is needed to connect to the VM remotely unless you have configured Active Directory on a Virtual Network. |
 | [Create a SQL login](https://docs.microsoft.com/sql/relational-databases/security/authentication-access/create-a-login) | If you are using SQL Authentication, you need a SQL Login with a user name and password that also has permissions to your target database. |
 | [Enable TCP/IP protocol](#manualtcp) | SQL Server must allow connections over TCP. |
 | [Enable firewall rule for the SQL Server port](https://docs.microsoft.com/sql/database-engine/configure-windows/configure-a-windows-firewall-for-database-engine-access) | The firewall on the VM must allow inbound traffic on the SQL Server port (default 1433). |
diff --git a/articles/virtual-machines/workloads/redhat/overview.md b/articles/virtual-machines/workloads/redhat/overview.md
@@ -35,7 +35,7 @@ Azure also offers Red Hat Gold Images. These images may be useful to customers w
 > Note on double billing: Double billing is incurred when a user pays twice for RHEL subscriptions. This usually happens when a customer uses subscription-manager to attach an entitlement on a RHEL PAYG VM. For example, a customer that uses subscription-manager to attach an entitlement for SAP packages on a RHEL PAYG image will indirectly be double-billed because they will pay twice for RHEL - once through the PAYG premium fee and once through their SAP subscription. This will not happen to BYOS image users.
 
 ### Generation 2 images
-Generation 2 VMs provide some newer features compared to Generation 1 VMs. Details are laid out in the [Generation 2 documentation](https://docs.microsoft.com/azure/virtual-machines/linux/generation-2). The key difference from a RHEL image perspective is that Generation 2 VMs use a UEFI instead of BIOS firmware interface, and use a GUID Partition Table (GPT) instead of a master boot record (MBR) on boot time. This allows for, among other things, OS disk sizes larger than 2TB. In addition, the [Mv2 series VMs](https://docs.microsoft.com/azure/virtual-machines/linux/sizes-memory#mv2-series) run only on Generation 2 images.
+Generation 2 VMs provide some newer features compared to Generation 1 VMs. Details are laid out in the [Generation 2 documentation](https://docs.microsoft.com/azure/virtual-machines/linux/generation-2). The key difference from a RHEL image perspective is that Generation 2 VMs use a UEFI instead of BIOS firmware interface, and use a GUID Partition Table (GPT) instead of a master boot record (MBR) on boot time. This allows for, among other things, OS disk sizes larger than 2TB. In addition, the [Mv2 series VMs](../../mv2-series.md) run only on Generation 2 images.
 
 RHEL Generation 2 images are available in the marketplace. Look for "gen2" in the image SKU when listing all images using the Azure CLI, and go to the "Advanced" tab in the VM deploy process to deploy a Generation 2 VM.
 
diff --git a/articles/virtual-machines/workloads/sap/hana-vm-operations.md b/articles/virtual-machines/workloads/sap/hana-vm-operations.md
@@ -66,7 +66,7 @@ You also can deploy a complete installed SAP HANA platform on the Azure VM servi
 
 >[!IMPORTANT]
 > In order to use M208xx_v2 VMs, you need to be careful selecting your 
->  Linux image from the Azure VM image gallery. In order to read the details, read the article [Memory optimized virtual machine sizes](https://docs.microsoft.com/azure/virtual-machines/windows/sizes-memory#mv2-series). 
+>  Linux image from the Azure VM image gallery. In order to read the details, read the article [Memory optimized virtual machine sizes](../../mv2-series.md).
 > 
 
 
diff --git a/articles/virtual-machines/workloads/sap/sap-high-availability-guide-wsfc-file-share.md b/articles/virtual-machines/workloads/sap/sap-high-availability-guide-wsfc-file-share.md
@@ -30,7 +30,7 @@ ms.custom: H1Hack27Feb2017
 
 [kb4025334]:https://support.microsoft.com/help/4025334/windows-10-update-kb4025334
 
-[dv2-series]:https://docs.microsoft.com/azure/virtual-machines/windows/sizes-general#dv2-series
+[dv2-series]:../../dv2-dsv2-series.md
 [ds-series]:https://docs.microsoft.com/azure/virtual-machines/windows/sizes-general
 
 [sap-installation-guides]:http://service.sap.com/instguides
diff --git a/includes/virtual-machines-common-ephemeral.md b/includes/virtual-machines-common-ephemeral.md
