Merge pull request #214927 from cmcclister/cm-linkfix-20221018-4

LinkFix: azure-docs-pr (2022-10) - 4

Author: Court72

articles/frontdoor/front-door-faq.yml

@@ -262,13 +262,12 @@ sections:
       - question: |
           Can I set alerts with Azure Front Door?
         answer:  |
-          Yes, Azure Front Door does support alerts. Alerts are configured on metrics. For reference to create alerts, please check [Configure alerts](/azure/frontdoor/standard-premium/how-to-monitor-metrics#configure-alerts-in-azure-portal).
-          And for more information about metrics available on Front Door diagnostic monitoring refer to [Front Door metrics](/azure/frontdoor/front-door-diagnostics#metrics).
+          Yes, Azure Front Door does support alerts. Alerts are configured on metrics. For reference to create alerts, please check [Configure alerts](./standard-premium/how-to-monitor-metrics.md#configure-alerts-in-azure-portal).
+          And for more information about metrics available on Front Door diagnostic monitoring refer to [Front Door metrics](./front-door-diagnostics.md#metrics).
       
 additionalContent: |
 
   ## Next steps
   
   - Learn how to [create a Front Door](quickstart-create-front-door.md).
   - Learn [how Front Door works](front-door-routing-architecture.md).
-          

articles/governance/machine-configuration/agent-notes.md

@@ -19,7 +19,7 @@ The guest configuration agent receives improvements on an ongoing basis. To stay
 - Known issues
 - Bug fixes
 
-For information on release notes for the connected machine agent, please see [What's new with the connected machine agent](/azure/azure-arc/servers/agent-release-notes).
+For information on release notes for the connected machine agent, please see [What's new with the connected machine agent](../../azure-arc/servers/agent-release-notes.md).
 
 ## Release notes
 
@@ -55,4 +55,4 @@ az vm extension set  --publisher Microsoft.GuestConfiguration --name Configurati
 - [Assign your custom policy definition](../policy/assign-policy-portal.md) using
   Azure portal.
 - Learn how to view
-  [compliance details for machine configuration](../policy/how-to/determine-non-compliance.md) policy assignments.
+  [compliance details for machine configuration](../policy/how-to/determine-non-compliance.md) policy assignments.

articles/hdinsight/benefits-of-migrating-to-hdinsight-40.md

@@ -237,7 +237,7 @@ Hive metastore operation takes much time and thus slow down Hive compilation. In
 
 ## Troubleshooting guide
 
-[HDInsight 3.6 to 4.0 troubleshooting guide for Hive workloads](/azure/hdinsight/interactive-query/interactive-query-troubleshoot-migrate-36-to-40.md) provides answers to common issues faced when migrating Hive workloads from HDInsight 3.6 to HDInsight 4.0.
+[HDInsight 3.6 to 4.0 troubleshooting guide for Hive workloads](./interactive-query/interactive-query-troubleshoot-migrate-36-to-40.md) provides answers to common issues faced when migrating Hive workloads from HDInsight 3.6 to HDInsight 4.0.
 
 ## References
 
@@ -255,5 +255,5 @@ https://hadoop.apache.org/docs/r3.1.1/hadoop-project-dist/hadoop-common/release/
 
 ## Further reading
 
-* [HDInsight 4.0 Announcement](/azure/hdinsight/hdinsight-version-release.md)
-* [HDInsight 4.0 deep dive](https://azure.microsoft.com/blog/deep-dive-into-azure-hdinsight-4-0.md)
+* [HDInsight 4.0 Announcement](./hdinsight-version-release.md)
+* [HDInsight 4.0 deep dive](https://azure.microsoft.com/blog/deep-dive-into-azure-hdinsight-4-0.md)

articles/hdinsight/hdinsight-overview-before-you-start.md

@@ -19,7 +19,7 @@ HDInsight have two options to configure the databases in the clusters.
 
 During cluster creation, default configuration will use internal database. Once the cluster is created, customer can’t change the database type.  Hence, it's recommended to create and use the external database. You can create custom databases for Ambari, Hive, and Ranger.
 
-For more information, see how to [Set up HDInsight clusters with a custom Ambari DB](/azure/hdinsight/hdinsight-custom-ambari-db.md)
+For more information, see how to [Set up HDInsight clusters with a custom Ambari DB](./hdinsight-custom-ambari-db.md)
 
 ## Keep your clusters up to date
 
@@ -29,10 +29,10 @@ As part of the best practices, we recommend you keep your clusters updated on re
 
 HDInsight release happens every 30 to 60 days. It's always good to move to the latest release as early possible. The recommended maximum duration for cluster upgrades is less than six months.
 
-For more information, see how to [Migrate HDInsight cluster to a newer version](/azure/hdinsight/hdinsight-upgrade-cluster.md)
+For more information, see how to [Migrate HDInsight cluster to a newer version](./hdinsight-upgrade-cluster.md)
 
 ## Next steps
 
 * [Create Apache Hadoop cluster in HDInsight](./hadoop/apache-hadoop-linux-create-cluster-get-started-portal.md)
 * [Create Apache Spark cluster - Portal](./spark/apache-spark-jupyter-spark-sql-use-portal.md)
-* [Enterprise security in Azure HDInsight](./domain-joined/hdinsight-security-overview.md)
+* [Enterprise security in Azure HDInsight](./domain-joined/hdinsight-security-overview.md)

articles/hdinsight/hdinsight-release-notes.md

@@ -36,7 +36,7 @@ This new feature allows you to add more disks in cluster, which will be used as
 > The added disks are only configured for node manager local directories.
 > 
 
-For more information, [see here](/azure/hdinsight/hdinsight-hadoop-provision-linux-clusters#configuration--pricing)
+For more information, [see here](./hdinsight-hadoop-provision-linux-clusters.md#configuration--pricing)
 
 **2. Selective logging analysis**
 
@@ -46,7 +46,7 @@ Selective logging analysis is now available on all regions for public preview. Y
 1. Selective Logging uses script action to disable/enable tables and their log types. Since it doesn't open any new ports or change any existing security setting hence, there are no security changes.
 1. Script Action runs in parallel on all specified nodes and changes the configuration files for disabling/enabling tables and their log types.
 
-For more information, [see here](/azure/hdinsight/selective-logging-analysis)
+For more information, [see here](./selective-logging-analysis.md)
 
 
 ![Icon_showing_bug_fixes](media/hdinsight-release-notes/icon-for-bugfix.png) 
@@ -118,4 +118,4 @@ https://hdiconfigactions.blob.core.windows.net/log-analytics-patch/OMSUPGRADE14.
 
 ### Known issues
 
-HDInsight is compatible with Apache HIVE 3.1.2. Due to a bug in this release, the Hive version is shown as 3.1.0 in hive interfaces. However, there's no impact on the functionality.
+HDInsight is compatible with Apache HIVE 3.1.2. Due to a bug in this release, the Hive version is shown as 3.1.0 in hive interfaces. However, there's no impact on the functionality.

articles/hdinsight/manage-clusters-runbooks.md

@@ -22,7 +22,7 @@ If you don’t have an Azure subscription, create a [free account](https://azure
 
 ## Prerequisites
 
-* An existing [Azure Automation account](/azure/automation/quickstarts/create-azure-automation-account-portal).
+* An existing [Azure Automation account](../automation/quickstarts/create-azure-automation-account-portal.md).
 * An existing [Azure Storage account](../storage/common/storage-account-create.md), which will be used as cluster storage.
 
 ## Install HDInsight modules
@@ -162,4 +162,4 @@ When no longer needed, delete the Azure Automation Account that was created to a
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Manage Apache Hadoop clusters in HDInsight by using Azure PowerShell](hdinsight-administer-use-powershell.md)
+> [Manage Apache Hadoop clusters in HDInsight by using Azure PowerShell](hdinsight-administer-use-powershell.md)

articles/healthcare-apis/iot/device-data-through-iot-hub.md

@@ -50,7 +50,7 @@ Use your device (real or simulated) to send the sample heart rate message shown
 This message will get routed to MedTech service, where the message will be transformed into a FHIR Observation resource and stored into FHIR service.
 
 > [!IMPORTANT]
-> To avoid device spoofing in device-to-cloud messages, Azure IoT Hub enriches all messages with additional properties. To learn more about these properties, see [Anti-spoofing properties](/azure/iot-hub/iot-hub-devguide-messages-construct#anti-spoofing-properties).
+> To avoid device spoofing in device-to-cloud messages, Azure IoT Hub enriches all messages with additional properties. To learn more about these properties, see [Anti-spoofing properties](../../iot-hub/iot-hub-devguide-messages-construct.md#anti-spoofing-properties).
 >
 > To learn about IoT Hub device message enrichment and IotJsonPathContentTemplate mappings usage with the MedTech service device mapping, see [How to use IotJsonPathContentTemplate mappings](how-to-use-iot-jsonpath-content-mappings.md).
 
@@ -91,4 +91,4 @@ To learn about the different stages of data flow within MedTech service, see
 >[!div class="nextstepaction"]
 >[MedTech service data flow](iot-data-flow.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/how-to-display-metrics.md

@@ -71,7 +71,7 @@ Metric category|Metric name|Metric description|
 
    > [!TIP]
    >
-   > To learn more about advanced metrics display and sharing options, see [Getting started with Azure Metrics Explorer](/azure/azure-monitor/essentials/metrics-getting-started)
+   > To learn more about advanced metrics display and sharing options, see [Getting started with Azure Metrics Explorer](../../azure-monitor/essentials/metrics-getting-started.md)
 
    > [!IMPORTANT]
    >
@@ -115,4 +115,4 @@ To learn about the MedTech service frequently asked questions (FAQs), see
 > [!div class="nextstepaction"]
 > [Frequently asked questions about the MedTech service](iot-connector-faqs.md)
 
-(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+(FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/how-to-use-iot-jsonpath-content-mappings.md

@@ -38,7 +38,7 @@ With each of these examples, you're provided with:
  * An example of what the MedTech service device message will look like after normalization.
 
 > [!IMPORTANT]
-> To avoid device spoofing in device-to-cloud messages, Azure IoT Hub enriches all messages with additional properties. To learn more about these properties, see [Anti-spoofing properties](/azure/iot-hub/iot-hub-devguide-messages-construct#anti-spoofing-properties).
+> To avoid device spoofing in device-to-cloud messages, Azure IoT Hub enriches all messages with additional properties. To learn more about these properties, see [Anti-spoofing properties](../../iot-hub/iot-hub-devguide-messages-construct.md#anti-spoofing-properties).
 
 > [!TIP]
 > [Visual Studio Code with the Azure IoT Hub extension](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) is a recommended method for sending IoT device messages to your IoT Hub for testing and troubleshooting.
@@ -274,4 +274,4 @@ In this article, you learned how to use IotJsonPathContentTemplate mappings with
 >[!div class="nextstepaction"]
 >[How to use the FHIR destination mapping](how-to-use-fhir-mappings.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/iot-metrics-diagnostics-export.md

@@ -12,7 +12,7 @@ ms.author: jasteppe
 
 # How to configure diagnostic settings for exporting the MedTech service metrics 
 
-In this article, you'll learn how to configure diagnostic settings for the MedTech service to export metrics to different destinations (for example: to [Azure storage](/azure/storage/) or an [Azure event hub](/azure/event-hubs/)) for audit, analysis, or backup.
+In this article, you'll learn how to configure diagnostic settings for the MedTech service to export metrics to different destinations (for example: to [Azure storage](../../storage/index.yml) or an [Azure event hub](../../event-hubs/index.yml)) for audit, analysis, or backup.
 
 ## Create a diagnostic setting for the MedTech service
 1. To enable metrics export for your MedTech service, select **MedTech service** in your workspace under **Services**.
@@ -90,4 +90,4 @@ In this article, you'll learn how to configure diagnostic settings for the MedTe
 To view the frequently asked questions (FAQs) about the MedTech service, see
 
 >[!div class="nextstepaction"]
->[MedTech service FAQs](iot-connector-faqs.md)
+>[MedTech service FAQs](iot-connector-faqs.md)