Merge pull request #90270 from john-par/1414791-clean-up-broken-azure-docs-pr-links-9-30

ktoliver · web-flow · commit eb7021990689 · 2019-10-02T10:58:59.000-07:00
[WIP] 1414791 clean up broken azure docs pr links 9 30
diff --git a/articles/aks/istio-install.md b/articles/aks/istio-install.md
@@ -19,7 +19,7 @@ This article shows you how to install Istio. The Istio `istioctl` client binary
 > [!NOTE]
 > These instructions reference Istio version `1.1.3`.
 >
-> The Istio `1.1.x` releases have been tested by the Istio team against Kubernetes versions `1.11`, `1.12`, `1.13`. You can find additional Istio versions at [GitHub - Istio Releases][istio-github-releases] and information about each of the releases at [Istio - Release Notes][istio-release-notes].
+> The Istio `1.1.x` releases have been tested by the Istio team against Kubernetes versions `1.11`, `1.12`, `1.13`. You can find additional Istio versions at [GitHub - Istio Releases][istio-github-releases] and information about each of the releases at [Istio News][istio-release-notes].
 
 In this article, you learn how to:
 
@@ -551,7 +551,7 @@ To learn how to monitor your AKS application using Application Insights and Isti
 [istio-docs-concepts]: https://istio.io/docs/concepts/what-is-istio/
 [istio-github]: https://github.com/istio/istio
 [istio-github-releases]: https://github.com/istio/istio/releases
-[istio-release-notes]: https://istio.io/about/notes/
+[istio-release-notes]: https://istio.io/news/
 [istio-install-download]: https://istio.io/docs/setup/kubernetes/download-release/
 [istio-install-helm]: https://istio.io/docs/setup/kubernetes/install/helm/
 [istio-install-helm-options]: https://istio.io/docs/reference/config/installation-options/
diff --git a/articles/app-service/web-sites-integrate-with-vnet.md b/articles/app-service/web-sites-integrate-with-vnet.md
@@ -274,13 +274,13 @@ If those items don't answer your problems, look first for things like:
 **regional VNet Integration**
 * is your destination an RFC 1918 address
 * is there an NSG blocking egress from your integration subnet
-* if going across ExpressRoute or a VPN, is your on-premise gateway configured to route traffic back up to Azure? If you can reach endpoints in your VNet but not on-premises, this is good to check.
+* if going across ExpressRoute or a VPN, is your on-premises gateway configured to route traffic back up to Azure? If you can reach endpoints in your VNet but not on-premises, this is good to check.
 
 **gateway required VNet Integration**
 * is the point-to-site address range in the RFC 1918 ranges (10.0.0.0-10.255.255.255 / 172.16.0.0-172.31.255.255 / 192.168.0.0-192.168.255.255)?
 * Does the Gateway show as being up in the portal? If your gateway is down, then bring it back up.
 * Do certificates show as being in sync or do you suspect that the network configuration was changed?  If your certificates are out of sync or you suspect that there has been a change made to your VNet configuration that wasn't synced with your ASPs, then hit "Sync Network".
-* if going across ExpressRoute or a VPN, is your on-premise gateway configured to route traffic back up to Azure? If you can reach endpoints in your VNet but not on-premises, this is good to check.
+* if going across ExpressRoute or a VPN, is your on-premises gateway configured to route traffic back up to Azure? If you can reach endpoints in your VNet but not on-premises, this is good to check.
 
 Debugging networking issues is a challenge because there you cannot see what is blocking access to a specific host:port combination. Some of the causes include:
 
@@ -340,6 +340,6 @@ You can integrate App Service with an Azure Virtual Network using PowerShell. Fo
 [V2VNETPortal]: ../vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal.md
 [VPNERCoex]: ../expressroute/expressroute-howto-coexist-resource-manager.md
 [ASE]: environment/intro.md
-[creategatewaysubnet]: https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal#gatewaysubnet
+[creategatewaysubnet]: ../vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal.md#creategw
 [creategateway]: https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal#creategw
 [setp2saddresses]: https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal#addresspool
diff --git a/articles/azure-resource-manager/index.yml b/articles/azure-resource-manager/index.yml
@@ -82,7 +82,7 @@ landingContent:
       - linkListType: reference
         links:
           - text: Azure Quickstart templates
-            url: /resources/templates/
+            url: template-deployment-overview.md
   # Card
   - title: Deploy templates
     linkLists:
diff --git a/articles/backup/backup-mabs-release-notes-v3.md b/articles/backup/backup-mabs-release-notes-v3.md
@@ -57,7 +57,7 @@ This article provides the known issues and workarounds for Microsoft Azure Backu
 1.  [Backup](https://docs.microsoft.com/sql/relational-databases/backup-restore/create-a-full-database-backup-sql-server?view=sql-server-2017#SSMSProcedure) your SQL database and uninstall MABS V2 (choose to retain the protected data during uninstall).
 2.  Upgrade to SQL 2017 (Enterprise) and uninstall reporting as part of upgrade.
 3. [Install](https://docs.microsoft.com/sql/reporting-services/install-windows/install-reporting-services?view=sql-server-2017#install-your-report-server) SQL Server Reporting Services (SSRS).
-4.  [Install](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms#download-ssms-182) SQL Server Management Studio (SSMS).
+4.  [Install](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms) SQL Server Management Studio (SSMS).
 5.  Configure Reporting using the parameters as documented in [SSRS configuration with SQL 2017](https://docs.microsoft.com/azure/backup/backup-azure-microsoft-azure-backup#upgrade-mabs).
 6.  [Install](backup-azure-microsoft-azure-backup.md) MABS V3.
 7. [Restore](https://docs.microsoft.com/sql/relational-databases/backup-restore/restore-a-database-backup-using-ssms?view=sql-server-2017) SQL using SSMS and run DPM-Sync tool as described [here](https://docs.microsoft.com/previous-versions/system-center/data-protection-manager-2010/ff634215(v=technet.10)).
diff --git a/articles/batch/batch-custom-images.md b/articles/batch/batch-custom-images.md
@@ -39,7 +39,7 @@ To scale Batch pools reliably with a custom image, we recommend creating a manag
 
 ### Prepare a VM
 
-If you are creating a new VM for the image, use a first party Azure Marketplace image supported by Batch as the base image for your managed image. Only first party images can be used as a base image. To get a full list of Azure Marketplace image references supported by Azure Batch, see the [List node agent SKUs](/rest/api/batchservice/account/listnodeagentskus) operation.
+If you are creating a new VM for the image, use a first party Azure Marketplace image supported by Batch as the base image for your managed image. Only first party images can be used as a base image. To get a full list of Azure Marketplace image references supported by Azure Batch, see the [List node agent SKUs](/java/api/com.microsoft.azure.batch.protocol.accounts.listnodeagentskus) operation.
 
 > [!NOTE]
 > You can't use a third-party image that has additional license and purchase terms as your base image. For information about these Marketplace images, see the guidance for [Linux](../virtual-machines/linux/cli-ps-findimage.md#deploy-an-image-with-marketplace-terms
diff --git a/articles/batch/batch-sig-images.md b/articles/batch/batch-sig-images.md
@@ -54,7 +54,7 @@ To scale Batch pools reliably with a custom image, we recommend creating a manag
 
 ### Prepare a VM
 
-If you are creating a new VM for the image, use a first party Azure Marketplace image supported by Batch as the base image for your managed image. Only first party images can be used as a base image. To get a full list of Azure Marketplace image references supported by Azure Batch, see the [List node agent SKUs](/rest/api/batchservice/account/listnodeagentskus) operation.
+If you are creating a new VM for the image, use a first party Azure Marketplace image supported by Batch as the base image for your managed image. Only first party images can be used as a base image. To get a full list of Azure Marketplace image references supported by Azure Batch, see the [List node agent SKUs](/java/api/com.microsoft.azure.batch.protocol.accounts.listnodeagentskus) operation.
 
 > [!NOTE]
 > You can't use a third-party image that has additional license and purchase terms as your base image. For information about these Marketplace images, see the guidance for [Linux](../virtual-machines/linux/cli-ps-findimage.md#deploy-an-image-with-marketplace-terms
diff --git a/articles/cognitive-services/Ink-Recognizer/index.yml b/articles/cognitive-services/Ink-Recognizer/index.yml
@@ -49,7 +49,7 @@ landingContent:
         - text: Azure PowerShell
           url: https://docs.microsoft.com/powershell/module/az.cognitiveservices/#cognitive_services
         - text: Azure CLI
-          url: https://docs.microsoft.com/cli/azure/cognitiveservices?view=azure-cli-latest#az_cognitiveservices_list
+          url: https://docs.microsoft.com/cli/azure/cognitiveservices?view=azure-cli-latest#az-cognitiveservices-list
 
 - title: Samples
   linkLists:
diff --git a/articles/cognitive-services/diagnostic-logging.md b/articles/cognitive-services/diagnostic-logging.md
@@ -30,7 +30,7 @@ To enable diagnostic logging, you'll need somewhere to store your log data. This
 Let's start by enabling diagnostic logging using the Azure portal.
 
 > [!NOTE]
-> To enable this feature using PowerShell or the Azure CLI, use the instructions provided in [Collect and consume log data from your Azure resources](https://docs.microsoft.com/azure/azure-monitor/platform/diagnostic-logs-overview#diagnostic-settings).
+> To enable this feature using PowerShell or the Azure CLI, use the instructions provided in [Collect and consume log data from your Azure resources](https://docs.microsoft.com/azure/azure-monitor/platform/diagnostic-logs-overview).
 
 1. Navigate to the Azure portal. Then locate and select a Cognitive Services resource. For example, your subscription to Bing Web Search.   
 2. Next, from the left-hand navigation menu, locate **Monitoring** and select **Diagnostic settings**. This screen contains all previously created diagnostic settings for this resource.
diff --git a/articles/cognitive-services/text-analytics/index.yml b/articles/cognitive-services/text-analytics/index.yml
@@ -135,7 +135,7 @@ landingContent:
         - text: Go client library
           url: https://godoc.org/github.com/Azure/azure-sdk-for-go/services/cognitiveservices/v2.1/textanalytics
         - text: Azure PowerShell 
-          url: https://docs.microsoft.com/powershell/module/az.cognitiveservices/#cognitive_services"
+          url: https://docs.microsoft.com/powershell/module/az.cognitiveservices
         - text: Azure CLI 
           url: https://docs.microsoft.com/cli/azure/cognitiveservices?view=azure-cli-latest
 
diff --git a/articles/cosmos-db/bulk-executor-graph-dotnet.md b/articles/cosmos-db/bulk-executor-graph-dotnet.md
@@ -68,7 +68,7 @@ catch (Exception e)
 }
 ```
 
-For more information on the parameters of the bulk executor library, refer to the [BulkImportData to Azure Cosmos DB topic](https://docs.microsoft.com/azure/cosmos-db/bulk-executor-dot-net#bulk-import-data-to-azure-cosmos-db).
+For more information on the parameters of the bulk executor library, refer to the [BulkImportData to Azure Cosmos DB topic](bulk-executor-dot-net.md#bulk-import-data-to-an-azure-cosmos-account).
 
 The payload needs to be instantiated into `GremlinVertex` and `GremlinEdge` objects. Here is how these objects can be created:
 
diff --git a/articles/cosmos-db/scripts/cli/cassandra/throughput.md b/articles/cosmos-db/scripts/cli/cassandra/throughput.md
@@ -39,7 +39,7 @@ This script uses the following commands. Each command in the table links to comm
 | [az cosmosdb create](/cli/azure/cosmosdb#az-cosmosdb-create) | Creates an Azure Cosmos DB account. |
 | [az cosmosdb cassandra keyspace create](/cli/azure/cosmosdb/cassandra/keyspace#az-cosmosdb-cassandra-keyspace-create) | Creates an Azure Cosmos Cassandra keyspace. |
 | [az cosmosdb cassandra table create](/cli/azure/cosmosdb/cassandra/table#az-cosmosdb-cassandra-table-create) | Creates an Azure Cosmos Cassandra table. |
-| [az cosmosdb cassandra keyspace throughput update](/cli/azure/cosmosdb/cassandra/keyspace/throughputaz-cosmosdb-cassandra-keyspace-throughput-update) | Update RU/s for an Azure Cosmos Cassandra keyspace. |
+| [az cosmosdb cassandra keyspace throughput update](/cli/azure/cosmosdb/cassandra/keyspace/throughput?view=azure-cli-latest#az-cosmosdb-cassandra-keyspace-throughput-update) | Update RU/s for an Azure Cosmos Cassandra keyspace. |
 | [az cosmosdb cassandra table throughput update](/cli/azure/cosmosdb/cassandra/table/throughput#az-cosmosdb-cassandra-table-throughput-update) | Update RU/s for an Azure Cosmos Cassandra table. |
 | [az group delete](/cli/azure/resource#az-resource-delete) | Deletes a resource group including all nested resources. |
 
diff --git a/articles/data-factory/monitor-using-azure-monitor.md b/articles/data-factory/monitor-using-azure-monitor.md
@@ -466,7 +466,7 @@ After a few moments, the new setting appears in your list of settings for this d
 * In _Azure-Diagnostics_ mode, diagnostic logs flow into _AzureDiagnostics_ table
 
 > [!NOTE]
-> Because an Azure log table can't have more than 500 columns, we highly recommended you select Resource-Specific mode. For more information, see [Log Analytics Known Limitations](https://docs.microsoft.com/azure/azure-monitor/platform/diagnostic-logs-stream-log-store#known-limitation-column-limit-in-azurediagnostics).
+> Because an Azure log table can't have more than 500 columns, we highly recommended you select Resource-Specific mode. For more information, see [Log Analytics Known Limitations](../azure-monitor/platform/resource-logs-collect-workspace.md#column-limit-in-azurediagnostics).
 
 ### Install Azure Data Factory Analytics from Azure Marketplace
 
diff --git a/articles/germany/germany-migration-compute.md b/articles/germany/germany-migration-compute.md
@@ -173,7 +173,7 @@ Migrating Azure Functions resources from Azure Germany to global Azure isn't sup
 
 For more information:
 
-- Refresh your knowledge by completing the [Functions tutorials](https://docs.microsoft.com/azure/azure-functions/#step-by-step-tutorials).
+- Refresh your knowledge by completing the [Functions tutorials](https://docs.microsoft.com/azure/azure-functions).
 - Learn how to [export Resource Manager templates](../azure-resource-manager/manage-resource-groups-portal.md#export-resource-groups-to-templates) or read an overview of [Azure Resource Manager](../azure-resource-manager/resource-group-overview.md).
 - Review the [Azure Functions overview](../azure-functions/functions-overview.md).
 - Get an [overview of Azure locations](https://azure.microsoft.com/global-infrastructure/locations/).
diff --git a/articles/germany/germany-migration-iot.md b/articles/germany/germany-migration-iot.md
@@ -49,7 +49,7 @@ Migrating Azure Functions resources from Azure Germany to global Azure isn't sup
 
 For more information:
 
-- Refresh your knowledge by completing the [Functions tutorials](https://docs.microsoft.com/azure/azure-functions/#step-by-step-tutorials).
+- Refresh your knowledge by completing the [Functions tutorials](https://docs.microsoft.com/azure/azure-functions).
 - Learn how to [export Resource Manager templates](../azure-resource-manager/manage-resource-groups-portal.md#export-resource-groups-to-templates) or read the overview of [Azure Resource Manager](../azure-resource-manager/resource-group-overview.md).
 - Review the [Azure Functions overview](../azure-functions/functions-overview.md).
 - Read an [overview of Azure locations](https://azure.microsoft.com/global-infrastructure/locations/).
diff --git a/articles/germany/germany-migration-security.md b/articles/germany/germany-migration-security.md
@@ -42,7 +42,7 @@ Get-AzKeyVaultSecret -vaultname mysecrets -name Deploydefaultpw
 
 For more information:
 
-- Refresh your knowledge by completing the [Key Vault tutorials](https://docs.microsoft.com/azure/key-vault/#step-by-step-tutorials).
+- Refresh your knowledge by completing the [Key Vault tutorials](https://docs.microsoft.com/azure/key-vault/).
 - Review the [Key Vault overview](../key-vault/key-vault-overview.md).
 - Review the [Key Vault PowerShell cmdlets](/powershell/module/az.keyvault/).
 
diff --git a/articles/kinect-dk/access-data-body-frame.md b/articles/kinect-dk/access-data-body-frame.md
@@ -21,7 +21,7 @@ The following functions are covered:
 - [k4abt_frame_get_body_skeleton()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga7ef3f65827c9d21dac0caef572cc6c23.html#ga7ef3f65827c9d21dac0caef572cc6c23)
 - [k4abt_frame_get_capture()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_gad9eef11f6496bbfe997536c374217d9a.html#gad9eef11f6496bbfe997536c374217d9a)
 - [k4abt_frame_get_num_bodies()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga485b3a0f29e61c75f2e3d8b78b345ea9.html#ga485b3a0f29e61c75f2e3d8b78b345ea9)
-- [k4abt_frame_get_timestamp_usec()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga4c7d92c9f1b4e4a4b928736fb315f918.html#ga4c7d92c9f1b4e4a4b928736fb315f918)
+- [k4abt_frame_get_device_timestamp_usec()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga04be7b814b40296cd6b97044ed7283e4.html#ga04be7b814b40296cd6b97044ed7283e4)
 
 ## Key components of a body frame
 
diff --git a/articles/kinect-dk/build-first-body-app.md b/articles/kinect-dk/build-first-body-app.md
@@ -28,7 +28,7 @@ Getting started with the Body Tracking SDK? This quickstart will get you up and
   - [k4a_device_stop_cameras()](https://microsoft.github.io/Azure-Kinect-Sensor-SDK/master/group___functions_ga4fa0e0a011a7105309ad97f081a5d6b8.html#ga4fa0e0a011a7105309ad97f081a5d6b8)
   - [k4a_device_close()](https://microsoft.github.io/Azure-Kinect-Sensor-SDK/master/group___functions_ga7a3931d9a690b3971caaac83b43f9423.html#ga7a3931d9a690b3971caaac83b43f9423)
 - Review the documentation on the following Body Tracking SDK functions:
-  - [k4abt_tracker_create()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_gae395d73880395ffc6ffbdd5132aa9181.html#gae395d73880395ffc6ffbdd5132aa9181)
+  - [k4abt_tracker_create()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga1aa71481b8441def94de11b29e0e3cbc.html#ga1aa71481b8441def94de11b29e0e3cbc)
   - [k4abt_tracker_enqueue_capture()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga093becd9bb4a63f5f4d56f58097a7b1e.html#ga093becd9bb4a63f5f4d56f58097a7b1e)
   - [k4abt_tracker_pop_result()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_gaaf446fb1579cbbe0b6af824ee0a7458b.html#gaaf446fb1579cbbe0b6af824ee0a7458b)
   - [k4abt_tracker_shutdown()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga94036969ef94cbc414c78b3f6d04bfa5.html#ga94036969ef94cbc414c78b3f6d04bfa5)
diff --git a/articles/machine-learning/service/how-to-train-ml-models.md b/articles/machine-learning/service/how-to-train-ml-models.md
@@ -111,7 +111,7 @@ Parameter | Description | Default
 `custom_docker_image`| Name of the image you want to use. Only provide images available in public docker repositories (in this case Docker Hub). To use an image from a private docker repository, use the constructor's `environment_definition` parameter instead. [See example](https://github.com/Azure/MachineLearningNotebooks/blob/master/how-to-use-azureml/training-with-deep-learning/how-to-use-estimator/how-to-use-estimator.ipynb). | `None`
 `node_count`| Number of nodes to use for your training job. | `1`
 `process_count_per_node`| Number of processes (or "workers") to run on each node. In this case, you use the `2` GPUs available on each node.| `1`
-`distributed_training`| [MPIConfiguration ]('https://docs.microsoft.com/python/api/azureml-core/azureml.core.runconfig.mpiconfiguration?view=azure-ml-py') object for launching distributed training using MPI backend.  | `None`
+`distributed_training`| [MPIConfiguration ](https://docs.microsoft.com/python/api/azureml-core/azureml.core.runconfig.mpiconfiguration?view=azure-ml-py) object for launching distributed training using MPI backend.  | `None`
 
 
 Finally, submit the training job:
diff --git a/articles/managed-applications/microsoft-common-fileupload.md b/articles/managed-applications/microsoft-common-fileupload.md
@@ -44,7 +44,7 @@ A control that allows a user to specify one or more files to upload.
 ```
 
 ## Remarks
-- `constraints.accept` specifies the types of files that are shown in the browser's file dialog. See the [HTML5 specification](https://www.w3.org/TR/html5/forms.html#attr-input-accept) for allowed values. The default value is **null**.
+- `constraints.accept` specifies the types of files that are shown in the browser's file dialog. See the [HTML5 specification](https://html.spec.whatwg.org/multipage/input.html#attr-input-accept) for allowed values. The default value is **null**.
 - If `options.multiple` is set to **true**, the user is allowed to select more than one file in the browser's file dialog. The default value is **false**.
 - This element supports uploading files in two modes based on the value of `options.uploadMode`. If **file** is specified, the output has the contents of the file as a blob. If **url** is specified, then the file is uploaded to a temporary location, and the output has the URL of the blob. Temporary blobs will be purged after 24 hours. The default value is **file**.
 - An uploaded file is protected. The output URL includes a [SAS token](../storage/common/storage-dotnet-shared-access-signature-part-1.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) for accessing the file during deployment.
diff --git a/articles/security/develop/threat-modeling-tool-communication-security.md b/articles/security/develop/threat-modeling-tool-communication-security.md
diff --git a/articles/sql-database/sql-database-in-memory-sample.md b/articles/sql-database/sql-database-in-memory-sample.md
diff --git a/articles/storsimple/storsimple-partner-csp-faq.md b/articles/storsimple/storsimple-partner-csp-faq.md
diff --git a/articles/time-series-insights/time-series-insights-authentication-and-authorization.md b/articles/time-series-insights/time-series-insights-authentication-and-authorization.md

Original file line number	Diff line number	Diff line change
`@@ -68,7 +68,7 @@ catch (Exception e)`
`68`	`68`	`}`
`69`	`69`	```
`70`	`70`
`71`		`-For more information on the parameters of the bulk executor library, refer to the [BulkImportData to Azure Cosmos DB topic](https://docs.microsoft.com/azure/cosmos-db/bulk-executor-dot-net#bulk-import-data-to-azure-cosmos-db).`
	`71`	`+For more information on the parameters of the bulk executor library, refer to the [BulkImportData to Azure Cosmos DB topic](bulk-executor-dot-net.md#bulk-import-data-to-an-azure-cosmos-account).`
`72`	`72`
`73`	`73`	The payload needs to be instantiated into `GremlinVertex` and `GremlinEdge` objects. Here is how these objects can be created:
`74`	`74`