Merge pull request #285310 from rmca14/fixwarns8-22

Fix warnings migration

Author: prmerger-automator[bot]

articles/governance/policy/how-to/migrate-from-automanage-best-practices.md

@@ -234,12 +234,10 @@ next steps:
 <!-- Reference link definitions -->
 [01]: ../overview.md
 [02]: ../../../backup/backup-azure-arm-userestapi-createorupdatepolicy.md
-[03]: ../../../virtual-machines/extensions/iaas-antimalware-windows.md
+[03]: /azure/virtual-machines/extensions/iaas-antimalware-windows
 [04]: https://learn.microsoft.com/windows-server/manage/windows-admin-center/azure/manage-vm
 [05]: ../../../update-manager/migration-overview.md
 [06]: https://ms.portal.azure.com/
 [07]: ../concepts/definition-structure-basics.md
 [08]: ../assign-policy-portal.md
 [09]: https://azure.microsoft.com/pricing/details/azure-automanage/
-
-

articles/virtual-desktop/add-session-hosts-host-pool.md

@@ -53,7 +53,7 @@ For a general idea of what's required, such as supported operating systems, virt
 
   - At least one Windows OS image available on the cluster. For more information, see how to [create VM images by using Azure Marketplace images](/azure-stack/hci/manage/virtual-machine-image-azure-marketplace), [use images in an Azure Storage account](/azure-stack/hci/manage/virtual-machine-image-storage-account), and [use images in a local share](/azure-stack/hci/manage/virtual-machine-image-local-share).
 
-  - The [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview) on Azure Stack HCI VMs created outside the Azure Virtual Desktop service, such as with an automated pipeline. The virtual machines use the agent to communicate with [Azure Instance Metadata Service](../virtual-machines/instance-metadata-service.md), which is a [required endpoint for Azure Virtual Desktop](../virtual-desktop/required-fqdn-endpoint.md).
+  - The [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview) on Azure Stack HCI VMs created outside the Azure Virtual Desktop service, such as with an automated pipeline. The virtual machines use the agent to communicate with [Azure Instance Metadata Service](/azure/virtual-machines/instance-metadata-service), which is a [required endpoint for Azure Virtual Desktop](../virtual-desktop/required-fqdn-endpoint.md).
 
   - A logical network that you created on your Azure Stack HCI cluster. DHCP logical networks or static logical networks with automatic IP allocation are supported. For more information, see [Create logical networks for Azure Stack HCI](/azure-stack/hci/manage/create-logical-networks).
 

articles/vpn-gateway/vpn-gateway-classic-resource-manager-migration.md

@@ -17,7 +17,7 @@ VPN gateways can now be migrated from the classic deployment model to [Resource
 > [!IMPORTANT]
 > [!INCLUDE [classic gateway restrictions](../../includes/vpn-gateway-classic-gateway-restrict-create.md)]
 
-VPN gateways are migrated as part of VNet migration from classic to Resource Manager. This migration is done one VNet at a time. There aren't additional requirements in terms of tools or prerequisites to migrate. Migration steps are identical to the existing VNet migration and are documented at [IaaS resources migration page](../virtual-machines/migration-classic-resource-manager-ps.md). 
+VPN gateways are migrated as part of VNet migration from classic to Resource Manager. This migration is done one VNet at a time. There aren't additional requirements in terms of tools or prerequisites to migrate. Migration steps are identical to the existing VNet migration and are documented at [IaaS resources migration page](/azure/virtual-machines/migration-classic-resource-manager-ps).
 
 There isn't a data path downtime during migration and thus existing workloads continue to function without the loss of on-premises connectivity during migration. The public IP address associated with the VPN gateway doesn't change during the migration process. This implies that you won't need to reconfigure your on-premises router once the migration is completed.  
 
@@ -64,4 +64,4 @@ Since we transform VNet-to-VNet connectivity without requiring local sites, the
 
 ## Next steps
 
-After learning about VPN gateway migration support, go to [platform-supported migration of IaaS resources from classic to Resource Manager](../virtual-machines/migration-classic-resource-manager-ps.md) to get started.
+After learning about VPN gateway migration support, go to [platform-supported migration of IaaS resources from classic to Resource Manager](/azure/virtual-machines/migration-classic-resource-manager-ps) to get started.