Merge pull request #188403 from cmcclister/cm-linkfix-20220211-2

LinkFix: azure-docs-pr (2022-02) - 2

Author: v-shils

articles/iot-edge/how-to-update-iot-edge.md

@@ -122,7 +122,7 @@ If you want to update to the most recent version of IoT Edge, use the following
 :::moniker range=">=iotedge-2020-11"
 
 >[!IMPORTANT]
->This is a Public Preview version of [Azure IoT Edge for Linux on Windows continuous release (EFLOW CR)](https://aka.ms/AzEFLOW-Versions), not intended for production use. A clean install may be required for production use once the final General Availability (GA) release is available.
+>This is a Public Preview version of [Azure IoT Edge for Linux on Windows continuous release (EFLOW CR)](./version-history.md), not intended for production use. A clean install may be required for production use once the final General Availability (GA) release is available.
 >
 >To find out if you're currently using the continuous release version, navigate to **Settings** > **Apps** on your Windows device. Find **Azure IoT Edge** in the list of apps and features. If your listed version is 1.2.x.y, you are running the continuous release version.
 <!-- end 1.2 -->
@@ -319,4 +319,4 @@ If you're installing IoT Edge, rather than upgrading an existing installation, u
 
 View the latest [Azure IoT Edge releases](https://github.com/Azure/azure-iotedge/releases).
 
-Stay up-to-date with recent updates and announcements in the [Internet of Things blog](https://azure.microsoft.com/blog/topics/internet-of-things/)
+Stay up-to-date with recent updates and announcements in the [Internet of Things blog](https://azure.microsoft.com/blog/topics/internet-of-things/)

articles/iot-edge/iot-edge-for-linux-on-windows.md

@@ -21,7 +21,7 @@ Azure IoT Edge for Linux on Windows (EFLOW) allows you to run containerized Linu
 <!-- 1.2 -->
 :::moniker range=">=iotedge-2020-11"
 >[!NOTE]
->The latest version of [Azure IoT Edge for Linux on Windows continuous release (EFLOW CR)](https://aka.ms/AzEFLOW-Versions), based on IoT Edge version 1.2, is in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). A clean installation may be required for devices going into production use once the general availability (GA) release is available. For more information, see [EFLOW continuous release](https://github.com/Azure/iotedge-eflow/wiki/EFLOW-Continuous-Release).
+>The latest version of [Azure IoT Edge for Linux on Windows continuous release (EFLOW CR)](./version-history.md), based on IoT Edge version 1.2, is in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). A clean installation may be required for devices going into production use once the general availability (GA) release is available. For more information, see [EFLOW continuous release](https://github.com/Azure/iotedge-eflow/wiki/EFLOW-Continuous-Release).
 :::moniker-end
 <!-- end 1.2 -->
 
@@ -107,4 +107,4 @@ Use the Azure IoT Edge support and feedback channels to get assistance with Azur
 
 Watch [Azure IoT Edge for Linux on Windows 10 IoT Enterprise](https://aka.ms/azeflow-show) for more information and a sample in action.
 
-Follow the steps in [Manually provision a single Azure IoT Edge for Linux on a Windows device](how-to-provision-single-device-linux-on-windows-symmetric.md) to set up a device with Azure IoT Edge for Linux on Windows.
+Follow the steps in [Manually provision a single Azure IoT Edge for Linux on a Windows device](how-to-provision-single-device-linux-on-windows-symmetric.md) to set up a device with Azure IoT Edge for Linux on Windows.

articles/iot-hub-device-update/import-update.md

@@ -79,8 +79,8 @@ Learn how to obtain a new update and import it into Device Update for IoT Hub. I
 ## If you're importing via APIs instead
 
 In addition to importing via the Azure portal, you can also import an update programmatically by:
-* Using `Azure SDK` for [.NET](https://docs.microsoft.com/dotnet/api/azure.iot.deviceupdate), [Java](https://docs.microsoft.com/java/api/com.azure.iot.deviceupdate), [JavaScript](https://docs.microsoft.com/javascript/api/@azure/iot-device-update) or [Python](https://docs.microsoft.com/python/api/azure-mgmt-deviceupdate/azure.mgmt.deviceupdate)
-* Using [Import Update REST API](https://docs.microsoft.com/rest/api/deviceupdate/2020-09-01/updates)
+* Using `Azure SDK` for [.NET](/dotnet/api/azure.iot.deviceupdate), [Java](/java/api/com.azure.iot.deviceupdate), [JavaScript](/javascript/api/@azure/iot-device-update) or [Python](/python/api/azure-mgmt-deviceupdate/azure.mgmt.deviceupdate)
+* Using [Import Update REST API](/rest/api/deviceupdate/2020-09-01/updates)
 * Using [sample PowerShell modules](https://github.com/Azure/iot-hub-device-update/tree/main/tools/AduCmdlets)
 
 > [!NOTE]
@@ -90,10 +90,10 @@ Update files and import manifest must be uploaded to an Azure Storage Blob conta
 
 > [!TIP]
 > To upload large update files to Azure Storage Blob container, you may use one of the following for better performance:
-> - [AzCopy](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-v10)
+> - [AzCopy](../storage/common/storage-use-azcopy-v10.md)
 > - [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer)
 
 ## Next Steps
 
 * [Create Groups](create-update-group.md)
-* [Learn about import concepts](import-concepts.md)
+* [Learn about import concepts](import-concepts.md)

articles/iot-hub/iot-hub-ha-dr.md

@@ -131,7 +131,7 @@ Time to recover = RTO [10 min - 2 hours for manual failover | 2 - 26 hours for M
 
 ## Disable disaster recovery
 
-IoT Hub provides Microsoft-Initiated Failover and Manual Failover by replicating data to the [paired region](/azure/availability-zones/cross-region-replication-azure) for each IoT hub. For some regions, you can avoid data replication outside of the region by disabling disaster recovery when creating an IoT hub. The following regions support this feature:
+IoT Hub provides Microsoft-Initiated Failover and Manual Failover by replicating data to the [paired region](../availability-zones/cross-region-replication-azure.md) for each IoT hub. For some regions, you can avoid data replication outside of the region by disabling disaster recovery when creating an IoT hub. The following regions support this feature:
 
 - **Brazil South**; paired region, South Central US.
 - **Southeast Asia (Singapore)**; paired region, East Asia (Hong Kong).
@@ -182,4 +182,4 @@ Here's a summary of the HA/DR options presented in this article that can be used
 
 * [What is Azure IoT Hub?](about-iot-hub.md)
 * [Get started with IoT Hubs (Quickstart)](../iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-csharp)
-* [Tutorial: Perform manual failover for an IoT hub](tutorial-manual-failover.md)
+* [Tutorial: Perform manual failover for an IoT hub](tutorial-manual-failover.md)

articles/key-vault/general/whats-new.md

@@ -21,7 +21,7 @@ Here's what's new with Azure Key Vault. New features and improvements are also a
 
 ## January 2022
 
-Azure Key Vault service throughput limits have been increased to serve double its previous quota for each vault to help ensure high performance for applications. That is, for secret GET and RSA 2,048-bit software keys, you'll receive 4,000 GET transactions per 10 seconds vs 2,000 per 10 seconds previously. The service quotas are specific to operation type and the entire list can be accessed in [Azure Key Vault Service Limits](https://docs.microsoft.com/azure/key-vault/general/service-limits). 
+Azure Key Vault service throughput limits have been increased to serve double its previous quota for each vault to help ensure high performance for applications. That is, for secret GET and RSA 2,048-bit software keys, you'll receive 4,000 GET transactions per 10 seconds vs 2,000 per 10 seconds previously. The service quotas are specific to operation type and the entire list can be accessed in [Azure Key Vault Service Limits](./service-limits.md). 
 
 For Azure update announcement, see [General availability: Azure Key Vault increased service limits for all its customers] (https://azure.microsoft.com/updates/azurekeyvaultincreasedservicelimits/)
 
@@ -139,4 +139,4 @@ First preview version (version 2014-12-08-preview) was announced on January 8, 2
 
 ## Next steps
 
-If you have additional questions, please contact us through [support](https://azure.microsoft.com/support/options/).
+If you have additional questions, please contact us through [support](https://azure.microsoft.com/support/options/).

articles/key-vault/secrets/quick-create-go.md

@@ -14,7 +14,7 @@ ms.devlang: golang
 
 In this quickstart, you'll learn to use the Azure SDK for Go to create, retrieve, list, and delete secrets from Azure Key Vault.
 
- Azure Key Vault can store [several objects types](/azure/key-vault/general/about-keys-secrets-certificates#object-types). But, this quickstart focuses on secrets. By using Azure Key Vault to store secrets, you avoid storing secrets in your code, which increases the security of your applications. 
+ Azure Key Vault can store [several objects types](../general/about-keys-secrets-certificates.md#object-types). But, this quickstart focuses on secrets. By using Azure Key Vault to store secrets, you avoid storing secrets in your code, which increases the security of your applications. 
 
 Get started with the [azsecrets](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/keyvault/azsecrets) package and learn how to manage Azure Key Vault secrets using Go.
 
@@ -237,4 +237,4 @@ az group delete --resource-group quickstart-rg
 - [Overview of Azure Key Vault](../general/overview.md)
 - [Azure Key Vault developer's guide](../general/developers-guide.md)
 - [Key Vault security overview](../general/security-features.md)
-- [Authenticate with Key Vault](../general/authentication.md)
+- [Authenticate with Key Vault](../general/authentication.md)

articles/load-balancer/load-balancer-common-deployment-errors.md

@@ -33,7 +33,7 @@ This article describes some common Azure Load Balancer deployment errors and pro
 |MarketplacePurchaseEligibilityFailed | Switch to the correct Administrative account to enable purchases due to subscription being an EA Subscription. You can read more [here](../marketplace/marketplace-faq-publisher-guide.yml#what-could-block-a-customer-from-completing-a-purchase-). |
 |ResourceDeploymentFailure| If your load balancer is in a failed state, follow these steps to bring it back from the failed state:<ol><li>Go to https://resources.azure.com, and sign in with your Azure portal credentials.</li><li>Select **Read/Write**.</li><li>On the left, expand **Subscriptions**, and then expand the Subscription with the Load Balancer to update.</li><li>Expand **ResourceGroups**, and then expand the resource group with the Load Balancer to update.</li><li>Select **Microsoft.Network** > **LoadBalancers**, and then select the Load Balancer to update, **LoadBalancer_1**.</li><li>On the display page for **LoadBalancer_1**, select **GET** > **Edit**.</li><li>Update the **ProvisioningState** value from **Failed** to **Succeeded**.</li><li>Select **PUT**.</li></ol>|
 |LoadBalancerWithoutFrontendIPCantHaveChildResources | A Load Balancer resource that has no frontend IP configurations, cannot have associated child resources or components associated to it. In order to mitigate this error, add a frontend IP configuration and then add the resources you are trying to add. |
-| LoadBalancerRuleCountLimitReachedForNic | A backend pool member's network interface (virtual machine, virtual machine scale set) cannot be associated to more than 300 rules. Reduce the number of rules or leverage another Load Balancer. This limit is documented on the [Load Balancer limits page](/azure/azure-resource-manager/management/azure-subscription-service-limits#load-balancer).
+| LoadBalancerRuleCountLimitReachedForNic | A backend pool member's network interface (virtual machine, virtual machine scale set) cannot be associated to more than 300 rules. Reduce the number of rules or leverage another Load Balancer. This limit is documented on the [Load Balancer limits page](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer).
 | LoadBalancerInUseByVirtualMachineScaleSet | The Load Balancer resource is in use by a virtual machine scale set and cannot be deleted. Use the ARM ID provided in the error message to search for the virtual machine scale set in order to delete it. | 
 
 

articles/load-testing/tutorial-cicd-azure-pipelines.md

@@ -153,7 +153,7 @@ First, you'll install the Azure Load Testing extension from the Azure DevOps Mar
 For every update to the main branch, the Azure pipeline executes the following steps:
 
 - Deploy the sample Node.js application to an Azure App Service web app. The name of the web app is configured in the pipeline definition.
-- Create an Azure Load Testing resource using the Azure Resource Manager (ARM) template present in the GitHub repository. Learn more about ARM templates [here](/azure/azure-resource-manager/templates/overview).
+- Create an Azure Load Testing resource using the Azure Resource Manager (ARM) template present in the GitHub repository. Learn more about ARM templates [here](../azure-resource-manager/templates/overview.md).
 - Trigger Azure Load Testing to create and run the load test, based on the Apache JMeter script and the test configuration YAML file in the repository.
 
 To view the results of the load test in the pipeline log:
@@ -342,4 +342,4 @@ The following YAML code snippet describes how to use the task in an Azure Pipeli
 You've now created an Azure Pipelines CI/CD workflow that uses Azure Load Testing for automatically running load tests. By using pass/fail criteria, you can set the status of the CI/CD workflow. With parameters, you can make the running of load tests configurable.
 
 * For more information about parameterizing load tests, see [Parameterize a load test](./how-to-parameterize-load-tests.md).
-* For more information about defining test pass/fail criteria, see [Define test criteria](./how-to-define-test-criteria.md).
+* For more information about defining test pass/fail criteria, see [Define test criteria](./how-to-define-test-criteria.md).

articles/load-testing/tutorial-cicd-github-actions.md

@@ -63,7 +63,7 @@ To grant GitHub Actions access to your Azure Load Testing resource, perform the
 
 ### Create a service principal
 
-First, you'll create an Azure Active Directory [service principal](/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object) and grant it the permissions to access your Azure Load Testing resource.
+First, you'll create an Azure Active Directory [service principal](../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) and grant it the permissions to access your Azure Load Testing resource.
 
 1. Run the following Azure CLI command to create a service principal and assign the *Contributor* role:
 
@@ -181,7 +181,7 @@ Update the *SampleApp.yaml* GitHub Actions workflow file to configure the parame
 The GitHub Actions workflow executes the following steps for every update to the main branch:
 
 - Deploy the sample Node.js application to an Azure App Service web app. The name of the web app is configured in the workflow file.
-- Create an Azure Load Testing resource using the Azure Resource Manager (ARM) template present in the GitHub repository. Learn more about ARM templates [here](/azure/azure-resource-manager/templates/overview).
+- Create an Azure Load Testing resource using the Azure Resource Manager (ARM) template present in the GitHub repository. Learn more about ARM templates [here](../azure-resource-manager/templates/overview.md).
 - Trigger Azure Load Testing to create and run the load test based on the Apache JMeter script and the test configuration YAML file in the repository.
 
 To view the results of the load test in the GitHub Actions workflow log:
@@ -315,4 +315,4 @@ You've now created a GitHub Actions workflow that uses Azure Load Testing for au
 
 * Learn more about the [Azure Load Testing Action](https://github.com/marketplace/actions/azure-load-testing).
 * Learn how to [parameterize a load test](./how-to-parameterize-load-tests.md).
-* Learn how to [define test pass/fail criteria](./how-to-define-test-criteria.md).
+* Learn how to [define test pass/fail criteria](./how-to-define-test-criteria.md).

articles/machine-learning/concept-network-data-access.md

@@ -120,7 +120,7 @@ To secure communication between Azure Machine Learning and Azure SQL Database, t
 
 * __Allow Azure services and resources to access the Azure SQL Database server__. Enabling this setting _allows all connections from Azure_, including __connections from the subscriptions of other customers__, to your database server.
 
-    For information on enabling this setting, see [IP firewall rules - Azure SQL Database and Synapse Analytics](/azure/azure-sql/database/firewall-configure).
+    For information on enabling this setting, see [IP firewall rules - Azure SQL Database and Synapse Analytics](../azure-sql/database/firewall-configure.md).
 
 * __Allow the IP address range of the Azure Machine Learning service in Firewalls and virtual networks__ for the Azure SQL Database. Allowing the IP addresses through the firewall limits __connections to the Azure Machine Learning service for a region__.
 
@@ -129,7 +129,7 @@ To secure communication between Azure Machine Learning and Azure SQL Database, t
 
     To get a list of the IP addresses for Azure Machine Learning, download the [Azure IP Ranges and Service Tags](https://www.microsoft.com/download/details.aspx?id=56519) and search the file for `AzureMachineLearning.<region>`, where `<region>` is the Azure region that contains your Azure Machine Learning workspace.
 
-    To add the IP addresses to your Azure SQL Database, see [IP firewall rules - Azure SQL Database and Synapse Analytics](/azure/azure-sql/database/firewall-configure).
+    To add the IP addresses to your Azure SQL Database, see [IP firewall rules - Azure SQL Database and Synapse Analytics](../azure-sql/database/firewall-configure.md).
 
 ## Next steps