Merge pull request #292047 from v-sreedevank/17Dec-Context

Update links to Migrate ToC

Author: prmerger-automator[bot]

articles/migrate/migrate-servers-to-azure-using-private-link.md

@@ -90,7 +90,7 @@ Enable replication as follows:
     - Select **No** if you don't want to apply Azure Hybrid Benefit and select **Next**. 
 
     - Select **Yes** if you have Windows Server machines that are covered with active Software Assurance or Windows Server subscriptions, and you want to apply the benefit to the machines you're migrating and select **Next**. 
-1. In **Compute**, review the VM name, size, OS disk type, and availability configuration (if selected in the previous step). VMs must conform with [Azure requirements](migrate-support-matrix-vmware-migration.md#azure-vm-requirements). 
+1. In **Compute**, review the VM name, size, OS disk type, and availability configuration (if selected in the previous step). VMs must conform with [Azure requirements](migrate-support-matrix-vmware-migration.md#azure-vm-requirements?context=/azure/migrate/context/migrate-context). 
 
     - **VM size**: If you're using assessment recommendations, the VM size dropdown shows the recommended size. Otherwise, Azure Migrate picks a size based on the closest match in the Azure subscription. Alternatively, pick a manual size in **Azure VM size**. 
 
@@ -106,7 +106,7 @@ Enable replication as follows:
 1. In **Tags**, add tags to your migrated virtual machines, disks, and NICs.
 
 1. In **Review and start replication**, review the settings, and select **Replicate** to start the initial replication for the servers. 
-    Next, follow the instructions to [perform migrations](tutorial-migrate-vmware.md#run-a-test-migration). 
+    Next, follow the instructions to [perform migrations](tutorial-migrate-vmware.md#run-a-test-migration?context=/azure/migrate/context/migrate-context). 
 
 #### Provisioning for the first time  
 
@@ -131,9 +131,9 @@ Ensure that the on-premises appliance has network connectivity to the storage ac
 
 ## Next steps 
 
- - [Migrate VMs](tutorial-migrate-vmware.md#migrate-vms)
- - Complete the [migration process](tutorial-migrate-vmware.md#complete-the-migration).
- - Review the [post-migration best practices](tutorial-migrate-vmware.md#post-migration-best-practices). 
+ - [Migrate VMs](tutorial-migrate-vmware.md#migrate-vms?context=/azure/migrate/context/migrate-context)
+ - Complete the [migration process](tutorial-migrate-vmware.md#complete-the-migration?context=/azure/migrate/context/migrate-context).
+ - Review the [post-migration best practices](tutorial-migrate-vmware.md#post-migration-best-practices?context=/azure/migrate/context/migrate-context). 
 
 ::: zone-end
 

articles/migrate/vmware/migrate-support-matrix-vmware.md

@@ -16,7 +16,7 @@ This article summarizes prerequisites and support requirements for using the [Az
 
 To assess servers, first, create an Azure Migrate project. The Azure Migrate: Discovery and assessment tool is automatically added to the project. Then, deploy the Azure Migrate appliance. The appliance continuously discovers on-premises servers and sends configuration and performance metadata to Azure. When discovery is finished, gather the discovered servers into groups and run assessments per group.
 
-As you plan your migration of VMware servers to Azure, see the [migration support matrix](migrate-support-matrix-vmware-migration.md).
+As you plan your migration of VMware servers to Azure, see the [migration support matrix](../migrate-support-matrix-vmware-migration.md).
 
 
 ## VMware requirements
@@ -320,7 +320,7 @@ Discovery method |  Dependency information between servers is gathered by using
 
 Requirement | Details
 --- | ---
-Before deployment | You should have a project in place with the Azure Migrate: Discovery and assessment tool added to the project.<br /><br />You deploy dependency visualization after setting up an Azure Migrate appliance to discover your on-premises servers.<br /><br />Learn how to [create a project for the first time](../create-manage-projects.md).<br /> Learn how to [add a discovery and assessment tool to an existing project](../how-to-assess.md).<br /> Learn how to set up the Azure Migrate appliance for assessment of [Hyper-V](../how-to-set-up-appliance-hyper-v.md), [VMware](how-to-set-up-appliance-vmware.md), or physical servers.
+Before deployment | You should have a project in place with the Azure Migrate: Discovery and assessment tool added to the project.<br /><br />You deploy dependency visualization after setting up an Azure Migrate appliance to discover your on-premises servers.<br /><br />Learn how to [create a project for the first time](../create-manage-projects.md).<br /> Learn how to [add a discovery and assessment tool to an existing project](../how-to-assess.md).<br /> Learn how to set up the Azure Migrate appliance for assessment of [Hyper-V](../how-to-set-up-appliance-hyper-v.md), [VMware](../how-to-set-up-appliance-vmware.md), or physical servers.
 Supported servers | Supported for all servers in your on-premises environment.
 Log Analytics | Azure Migrate and Modernize uses the [Service Map](/previous-versions/azure/azure-monitor/vm/service-map) solution in [Azure Monitor logs](/azure/azure-monitor/logs/log-query-overview) for dependency visualization.<br /><br /> You associate a new or existing Log Analytics workspace with a project. You can't modify the workspace for a project after you add the workspace. <br /><br /> The workspace must be in the same subscription as the project.<br /><br /> The workspace must be located in the East US, Southeast Asia, or West Europe regions. Workspaces in other regions can't be associated with a project.<br /><br /> The workspace must be in a [region in which Service Map is supported](https://azure.microsoft.com/global-infrastructure/services/?products=monitor&regions=all). You can monitor Azure VMs in any region. The VMs themselves aren't limited to the regions supported by the Log Analytics workspace.<br /><br /> In Log Analytics, the workspace associated with Azure Migrate is tagged with the project key and project name.
 Required agents | On each server that you want to analyze, install the following agents:<br />- Azure Monitor agent (AMA)<br />- [Dependency agent](/azure/azure-monitor/vm/vminsights-dependency-agent-maintenance)<br /><br /> If on-premises servers aren't connected to the internet, download and install the Log Analytics gateway on them.<br /><br /> Learn more about installing the [Dependency agent](../how-to-create-group-machine-dependencies.md#install-the-dependency-agent) and the Azure Monitor agent.
@@ -342,9 +342,9 @@ Assessment | You can add up to 35,000 servers in a single group.<br /><br /> You
 Learn more about [assessments](../concepts-assessment-calculation.md).
 
 
-## Import servers by using RVTools XLSX (preview)
+## Import servers using RVTools XLSX (preview)
 
-As part of your migration journey to Azure by using the Azure Migrate appliance, you first discover servers, inventory, and workloads. However, for a quick assessment before you deploy the appliance, you can [import the servers by using the RVTools XLSX file (preview)](tutorial-import-vmware-using-rvtools-xlsx.md).
+As part of your migration journey to Azure by using the Azure Migrate appliance, you first discover servers, inventory, and workloads. However, for a quick assessment before you deploy the appliance, you can [import the servers by using the RVTools XLSX file (preview)](../tutorial-import-vmware-using-rvtools-xlsx.md).
 
 ### Key benefits
 
@@ -382,4 +382,4 @@ To get an accurate operating system suitability/readiness in Azure VM and Azure
 ## Next steps
 
 * Review [assessment best practices](../best-practices-assessment.md).
-* Learn how to [prepare for a VMware assessment](tutorial-discover-vmware.md).
+* Learn how to [prepare for a VMware assessment](../tutorial-discover-vmware.md).

articles/migrate/vmware/tutorial-import-vmware-using-rvtools-xlsx.md

@@ -50,7 +50,7 @@ Before you begin this tutorial, ensure that you have the following prerequisites
 
 To create a project and register the Azure Migrate appliance, you must have an Azure user account that has the following permissions:
 
-- Contributor or Owner permissions in Azure subscription. Complete the procedure to [set Contributor or Owner permissions in the Azure subscription](tutorial-discover-vmware.md#prepare-an-azure-user-account)
+- Contributor or Owner permissions in Azure subscription. Complete the procedure to [set Contributor or Owner permissions in the Azure subscription](../tutorial-discover-vmware.md#prepare-an-azure-user-account)
 - Permissions to register Microsoft Entra apps.
 - Owner or Contributor and User Access Administrator permission at subscription level to create an instance of Azure Key Vault, which is used during the agentless server migration.
 

articles/migrate/vmware/tutorial-migrate-vmware.md

@@ -115,7 +115,7 @@ Enable replication as follows:
 
     :::image type="content" source="../media/tutorial-migrate-vmware/target-settings.png" alt-text="Screenshot on target settings.":::
 
-11. In **Compute**, review the VM name, size, OS disk type, and availability configuration (if selected in the previous step). VMs must conform with [Azure requirements](./migrate-support-matrix-vmware-migration.md#azure-vm-requirements).
+11. In **Compute**, review the VM name, size, OS disk type, and availability configuration (if selected in the previous step). VMs must conform with [Azure requirements](../migrate-support-matrix-vmware-migration.md#azure-vm-requirements).
 
     - **VM size**: If you're using assessment recommendations, the VM size dropdown shows the recommended size. Otherwise, Azure Migrate picks a size based on the closest match in the Azure subscription. Alternatively, pick a manual size in **Azure VM size**.
     - **OS Type**: Select the type of OS used (Windows or Linux).