Merge pull request #92894 from craigcaseyMSFT/vcraic1022b

garycentric · web-flow · commit 30c8e667ef4e · 2019-10-22T20:34:08.000-07:00
fix broken links from CATS report
diff --git a/articles/active-directory/saas-apps/google-apps-provisioning-tutorial.md b/articles/active-directory/saas-apps/google-apps-provisioning-tutorial.md
@@ -28,7 +28,7 @@ The objective of this tutorial is to demonstrate the steps to be performed in G
 > [!NOTE]
 > The G Suite connector was recently updated on October 2019. Changes made to the G Suite connector include:
 - Added support for additional G Suite user and group attributes. 
-- Updated G Suite target attribute names to match what is defined [here]().
+- Updated G Suite target attribute names to match what is defined [here](/azure/active-directory/manage-apps/customize-application-attributes).
 - Updated default attribute mappings.
 
 ## Prerequisites
diff --git a/articles/azure-functions/durable/durable-functions-dotnet-entities.md b/articles/azure-functions/durable/durable-functions-dotnet-entities.md
@@ -116,7 +116,7 @@ For example, we can modify the counter entity so it starts an orchestration when
 Class-based entities can be accessed directly, using explicit string names for the entity and its operations. We provide some examples below; for a deeper explanation of the underlying concepts (such as signals vs. calls) see the discussion in [Accessing entities](durable-functions-entities.md#accessing-entities). 
 
 > [!NOTE]
-> Where possible, we recommend [Accessing entities through interfaces](), because it provides more type checking.
+> Where possible, we recommend [Accessing entities through interfaces](#accessing-entities-through-interfaces), because it provides more type checking.
 
 ### Example: client signals entity
 
diff --git a/articles/azure-monitor/platform/alerts-overview.md b/articles/azure-monitor/platform/alerts-overview.md
@@ -180,9 +180,9 @@ The consumption and management of alert instances requires the user to have the
 
 You might want to query programmatically for alerts generated against your subscription. This might be to create custom views outside of the Azure portal, or to analyze your alerts to identify patterns and trends.
 
-You can query for alerts generated against your subscriptions either by using the [Alert Management REST API](https://aka.ms/alert-management-api) or by using the [Azure Resource Graph REST API for Alerts](https://docs.microsoft.com/rest/api/azureresourcegraph/resources/resources).
+You can query for alerts generated against your subscriptions either by using the [Alert Management REST API](https://aka.ms/alert-management-api) or by using the [Azure Resource Graph REST API for Alerts](https://docs.microsoft.com/rest/api/azureresourcegraph/resourcegraph(2018-09-01-preview)/resources/resources)).
 
-The [Azure Resource Graph REST API for Alerts](https://docs.microsoft.com/rest/api/azureresourcegraph/resources/resources) allows you to query for alert instances at scale. This is recommended when you have to manage alerts generated across many subscriptions. 
+The [Azure Resource Graph REST API for Alerts](https://docs.microsoft.com/rest/api/azureresourcegraph/resourcegraph(2018-09-01-preview)/resources/resources)) allows you to query for alert instances at scale. This is recommended when you have to manage alerts generated across many subscriptions. 
 
 The following sample request to the API returns the count of alerts within one subscription:
 
diff --git a/articles/data-catalog/data-catalog-adopting-data-catalog.md b/articles/data-catalog/data-catalog-adopting-data-catalog.md
@@ -120,7 +120,7 @@ To learn more about the data source registration tool, see [Get started with Azu
 As part of the pilot project, Nancy's team also uses data sources that are described in an Excel workbook that David and is colleagues maintain. Since other teams in the enterprise also use Excel workbooks to describe data sources, the IT team decides to create a tool to migrate the Excel workbook to Data Catalog. By using the Data Catalog REST API to import existing annotations, the pilot project team can have a complete data catalog consisting of metadata extracted from the data sources using the data source registration tool, complete with information previously documented by data producers and consumers, without the need for manual re-entry. As the enterprise data catalog grows, the organization can use the data source registration tool for common data sources, and the Data Catalog API for custom sources and uncommon scenarios.
 
 > [!NOTE]
-> We wrote a sample tool that uses the **Azure Data Catalog** API to migrate an Excel workbook to Data Catalog. To learn about the Data Catalog API and the sample tool, [download the Ad Hoc workbook code sample](https://azure.microsoft.com/documentation/samples/data-catalog-dotnet-excel-register-data-assets/), and check out the [Azure Data Catalog REST API](/rest/api/datacatalog/) documentation.
+> We wrote a sample tool that uses the **Azure Data Catalog** API to migrate an Excel workbook to Data Catalog. To learn about the Data Catalog API and the sample tool, [download the Ad Hoc workbook code sample](https://github.com/Azure-Samples/data-catalog-dotnet-excel-register-data-assets), and check out the [Azure Data Catalog REST API](/rest/api/datacatalog/) documentation.
 
 After the pilot project is in place, it's time to execute your Data Catalog adoption plan.
 
diff --git a/articles/digital-twins/security-authenticating-apis.md b/articles/digital-twins/security-authenticating-apis.md
@@ -44,7 +44,7 @@ When developers architect Digital Twins solutions, they typically create a middl
 
 1. The acquired token is then used to authenticate with or call APIs that are further downstream using the On-Behalf-Of flow
 
-For instructions about how to orchestrate the on-behalf-of flow, see [OAuth 2.0 On-Behalf-Of flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow). You also can view code samples in [Calling a downstream web API](https://azure.microsoft.com/resources/samples/active-directory-dotnet-webapi-onbehalfof/).
+For instructions about how to orchestrate the on-behalf-of flow, see [OAuth 2.0 On-Behalf-Of flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow). You also can view code samples in [Calling a downstream web API](https://github.com/Azure-Samples/active-directory-dotnet-webapi-onbehalfof).
 
 ## Next steps
 
diff --git a/articles/governance/resource-graph/concepts/work-with-data.md b/articles/governance/resource-graph/concepts/work-with-data.md
@@ -39,7 +39,7 @@ az graph query -q "Resources | project name | order by name asc" --first 200 --o
 Search-AzGraph -Query "Resources | project name | order by name asc" -First 200
 ```
 
-In the [REST API](/rest/api/azureresourcegraph/resources/resources), the control is **$top** and is
+In the [REST API](/rest/api/azureresourcegraph/resourcegraph(2018-09-01-preview)/resources/resources), the control is **$top** and is
 part of **QueryRequestOptions**.
 
 The control that is _most restrictive_ will win. For example, if your query uses the **top** or
@@ -73,14 +73,13 @@ az graph query -q "Resources | project name | order by name asc" --skip 10 --out
 Search-AzGraph -Query "Resources | project name | order by name asc" -Skip 10
 ```
 
-In the [REST API](/rest/api/azureresourcegraph/resources/resources), the control is **$skip** and is
+In the [REST API](/rest/api/azureresourcegraph/resourcegraph(2018-09-01-preview)/resources/resources), the control is **$skip** and is
 part of **QueryRequestOptions**.
 
 ## Paging results
 
 When it's necessary to break a result set into smaller sets of records for processing or because a
-result set would exceed the maximum allowed value of _1000_ returned records, use paging. The [REST
-API](/rest/api/azureresourcegraph/resources/resources) **QueryResponse** provides values to
+result set would exceed the maximum allowed value of _1000_ returned records, use paging. The [REST API](/rest/api/azureresourcegraph/resourcegraph(2018-09-01-preview)/resources/resources) **QueryResponse** provides values to
 indicate of a results set has been broken up: **resultTruncated** and **$skipToken**.
 **resultTruncated** is a boolean value that informs the consumer if there are additional records
 not returned in the response. This condition can also be identified when the **count** property is
diff --git a/articles/hdinsight/storm/apache-troubleshoot-storm.md b/articles/hdinsight/storm/apache-troubleshoot-storm.md
@@ -133,7 +133,7 @@ For more information about using Storm event hub spout .jar files with your topo
 
 ### Java-based topology
 
-[Process events from Azure Event Hubs with Apache Storm on HDInsight (Java)](https://docs.microsoft.com/azure/hdinsight/hdinsight-storm-develop-java-event-hub-topology)
+[Process events from Azure Event Hubs with Apache Storm on HDInsight (Java)](https://github.com/Azure-Samples/hdinsight-java-storm-eventhub)
 
 ### C#-based topology (Mono on HDInsight 3.4+ Linux Storm clusters)
 
diff --git a/articles/kinect-dk/about-azure-kinect-dk.md b/articles/kinect-dk/about-azure-kinect-dk.md
@@ -11,7 +11,7 @@ keywords: azure, kinect, overview, dev kit, DK, device, depth, body tracking, sp
 
 # About Azure Kinect DK
 
-Azure Kinect DK is a developer kit with advanced AI sensors that provide sophisticated computer vision and speech models.  Kinect contains a depth sensor, spatial microphone array with a video camera, and orientation sensor as an all in-one small device with multiple modes, options, and software development kits (SDKs). It is available for purchase in [Microsoft online store](https://www.microsoft.com/p/azure-kinect-dk/8pp5vxmd9nhq?activetab=pivot:overviewtab).
+Azure Kinect DK is a developer kit with advanced AI sensors that provide sophisticated computer vision and speech models.  Kinect contains a depth sensor, spatial microphone array with a video camera, and orientation sensor as an all in-one small device with multiple modes, options, and software development kits (SDKs). It is available for purchase in [Microsoft online store](https://www.microsoft.com/p/azure-kinect-dk/8pp5vxmd9nhq).
 
 The Azure Kinect DK development environment consists of the following multiple SDKs:
 
diff --git a/articles/networking/networking-partners-msp.md b/articles/networking/networking-partners-msp.md
@@ -34,7 +34,7 @@ Use the links in this section for more information about managed cloud networkin
 
 [Equinix](https://www.equinix.com/)
 
-[InterCloud](https://www.intercloud.com/partners/cloud-service-providers/get-azure-expressroute)
+[InterCloud](https://intercloud.com/partners/get-to-azure-via-expressroute/)
 
 [IIJ](https://www.iij.ad.jp/biz/cloudex/)
 
diff --git a/articles/security/fundamentals/encryption-overview.md b/articles/security/fundamentals/encryption-overview.md
@@ -54,7 +54,7 @@ The three server-side encryption models offer different key management character
 
 ### Azure disk encryption
 
-You can protect Windows and Linux virtual machines by using [Azure disk encryption](/azure/security/azure-security-disk-encryption), which uses [Windows BitLocker](https://technet.microsoft.com/library/cc766295(v=ws.10).aspx) technology and Linux [DM-Crypt](https://en.wikipedia.org/wiki/Dm-crypt) to protect both operating system disks and data disks with full volume encryption.
+You can protect Windows and Linux virtual machines by using [Azure disk encryption](/azure/security/fundamentals/azure-disk-encryption-vms-vmss), which uses [Windows BitLocker](https://technet.microsoft.com/library/cc766295(v=ws.10).aspx) technology and Linux [DM-Crypt](https://en.wikipedia.org/wiki/Dm-crypt) to protect both operating system disks and data disks with full volume encryption.
 
 Encryption keys and secrets are safeguarded in your [Azure Key Vault subscription](../../key-vault/key-vault-overview.md). By using the Azure Backup service, you can back up and restore encrypted virtual machines (VMs) that use Key Encryption Key (KEK) configuration.
 
