Merge pull request #278618 from v-savila/0618-Validation

Bulk update: Global effort to fix validation errors

Author: prmerger-automator[bot]

articles/app-service/deploy-container-azure-pipelines.md

@@ -20,10 +20,10 @@ In this article, we use Azure Pipelines to deploy a Windows container applicatio
 - A working Windows app with Dockerfile hosted on [Azure Repos](https://docs.github.com/get-started/quickstart/create-a-repo). 
 
 ## Add a Service Connection
-Before you create your pipeline, you should first create your Service Connection since you'll be asked to choose and verify your connection when creating your template. A Service Connection allows you to connect to your registry of choice (ACR or Docker Hub) when using the task templates. When adding a new service connection, choose the Docker Registry option. The following form asks you to choose Docker Hub or Azure Container Registry along with pertaining information. To follow along with this tutorial, use Azure Container Registry. You can create a new Service Connection following the directions [here](https://learn.microsoft.com/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml#create-new).
+Before you create your pipeline, you should first create your Service Connection since you'll be asked to choose and verify your connection when creating your template. A Service Connection allows you to connect to your registry of choice (ACR or Docker Hub) when using the task templates. When adding a new service connection, choose the Docker Registry option. The following form asks you to choose Docker Hub or Azure Container Registry along with pertaining information. To follow along with this tutorial, use Azure Container Registry. You can create a new Service Connection following the directions [here](/azure/devops/pipelines/library/service-endpoints).
 
 ## Secure your secrets
-Since we're using sensitive information that you don't want others to access, we use variables to protect our information. Create a variable by following the directions [here](https://learn.microsoft.com/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#secret-variables).
+Since we're using sensitive information that you don't want others to access, we use variables to protect our information. Create a variable by following the directions [here](/azure/devops/pipelines/process/variables).
 
 To add a Variable, you click the **Variables** button next to the Save button in the top-right of the editing view for your pipeline. Select the **New Variable** button and enter your information. Add the variables below with your own secrets appropriate from each resource.
 

articles/azure-monitor/alerts/action-groups.md

@@ -561,7 +561,7 @@ If you use the webhook action, your target webhook endpoint must be able to proc
 
 > [!NOTE]
 >
->Pre-requisites: https://learn.microsoft.com/powershell/microsoftgraph/installation?view=graph-powershell-1.0
+>Pre-requisites: [Install the Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/installation?view=graph-powershell-1.0&preserve-view=true)
 
 #### How to run?
 

articles/virtual-machines/move-virtual-machines-regional-zonal-powershell.md

@@ -545,7 +545,7 @@ To address the situations where the VM SKU is not found or there is a capacity i
 
 Selected virtual machine can't be moved to availability zone due to insufficient quota.
 
-**Recommended Action:** In-sufficient quota found. Refer to link and contact [support](https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits).
+**Recommended Action:** In-sufficient quota found. Refer to link and contact [support](../azure-resource-manager/management/azure-subscription-service-limits.md).
 
 
 

articles/virtual-machines/windows/prepare-for-upload-vhd-image.md

@@ -17,7 +17,7 @@ ms.custom: engagement-fy23
 
 Before you upload a Windows virtual machine (VM) from on-premises to Azure, you must prepare the
 virtual hard disk (VHD or VHDX). Azure supports both generation 1 and generation 2 VMs that are in
-VHD file format and that have a fixed-size disk. The maximum size allowed for the OS VHD on a generation 1 VM is 2 TB. You can validate your VHD or VHDX file by refering to [this documentation](https://learn.microsoft.com/powershell/module/hyper-v/test-vhd?view=windowsserver2022-ps).
+VHD file format and that have a fixed-size disk. The maximum size allowed for the OS VHD on a generation 1 VM is 2 TB. You can validate your VHD or VHDX file by refering to [this documentation](/powershell/module/hyper-v/test-vhd?view=windowsserver2022-ps&preserve-view=true).
 
 You can convert a VHDX file to VHD, convert a dynamically
 expanding disk to a fixed-size disk, but you can't change a VM's generation. For more information,