Merge pull request #291994 from v-sreedevank/16Dec-VMwareContext

VMware migrate context

Author: v-dirichards

articles/migrate/.openpublishing.redirection.migrate.json

@@ -22,8 +22,8 @@
         },
         {
             "source_path_from_root": "/articles/migrate/migrate-support-matrix-vmware-migration.md",
-            "redirect_url": "/azure/migrate/vmware/migrate-support-matrix-vmware-migration?context=/azure/migrate/context/migrate-context",
-            "redirect_document_id": true
+            "redirect_url": "/azure/migrate/vmware/migrate-support-matrix-vmware-migration",
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/migrate/migrate-support-matrix-vmware.md",
@@ -77,7 +77,12 @@
         },
         {
             "source_path_from_root": "/articles/migrate/tutorial-migrate-vmware.md",
-            "redirect_url": "/azure/migrate/vmware/tutorial-migrate-vmware?context=/azure/migrate/context/migrate-context",
+            "redirect_url": "/azure/migrate/vmware/tutorial-migrate-vmware",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/azure/migrate/vmware/tutorial-migrate-vmware.md",
+            "redirect_url": "tutorial-migrate-vmware?context=/azure/migrate/context/migrate-context",
             "redirect_document_id": true
         },
         {

articles/migrate/add-server-credentials.md

@@ -66,6 +66,6 @@ Feature | Windows credentials | Linux credentials
 
 ## Next steps
 
-- [Steps to add credentials in VMware appliance](./tutorial-discover-vmware.md#provide-server-credentials).
+- [Steps to add credentials in VMware appliance](./tutorial-discover-vmware.md?context=/azure/migrate/context/migrate-context#provide-server-credentials).
 - [Steps to add credentials in Hyper-V appliance](tutorial-discover-hyper-v.md#provide-server-credentials).
 - [Steps to add credentials in physical appliance](tutorial-discover-physical.md#start-continuous-discovery). 

articles/migrate/common-questions-discovery-assessment.md

@@ -34,11 +34,11 @@ Regardless of the migration option chosen, the first step to migrate a server us
 Here are some considerations to keep in mind while deciding on the migration option.
 
 **Agentless migrations** don't require any software (agents) to be deployed on the source VMs/servers being migrated. The agentless option orchestrates replication by integrating with the functionality provided by the virtualization provider.
-The Agentless replication options are available for [VMware VMs](./tutorial-migrate-vmware.md) and [Hyper-V VMs](./tutorial-migrate-hyper-v.md).
+The Agentless replication options are available for [VMware VMs](tutorial-migrate-vmware.md) and [Hyper-V VMs](./tutorial-migrate-hyper-v.md).
 
 **Agent-based migrations** require Azure Migrate software (agents) to be installed on the source VMs/machines to be migrated. The agent-based option doesn’t rely on the virtualization platform for the replication functionality. Therefore, it can be used with any server running an x86/x64 architecture and a version of an operating system supported by the agent-based replication method.
 
-Agent-based migration option can be used for [VMware VMs](./tutorial-migrate-vmware-agent.md), [Hyper-V VMs](./tutorial-migrate-physical-virtual-machines.md), [physical servers](./tutorial-migrate-physical-virtual-machines.md), [VMs running on AWS](./tutorial-migrate-aws-virtual-machines.md), VMs running on GCP, or VMs running on a different virtualization provider. The agent-based migration treats your machines as physical servers for migration.
+Agent-based migration option can be used for [VMware VMs](tutorial-migrate-vmware-agent.md), [Hyper-V VMs](./tutorial-migrate-physical-virtual-machines.md), [physical servers](./tutorial-migrate-physical-virtual-machines.md), [VMs running on AWS](./tutorial-migrate-aws-virtual-machines.md), VMs running on GCP, or VMs running on a different virtualization provider. The agent-based migration treats your machines as physical servers for migration.
 
 While the agentless migration offers another convenience and simplicity over the agent-based replication options for the supported scenarios (VMware and Hyper-V), you may want to consider using the agent-based scenario for the following use cases:
 
@@ -178,7 +178,7 @@ When replication is configured for a virtual machine, it first goes through an i
 
 When you perform the migrate operation on a replicating virtual machine, you've the option to shut down the on-premises virtual machine, and perform one final incremental replication to ensure zero data loss. On performing the migration, the replica managed disks corresponding to the virtual machine are used to create the virtual machine in Azure.
 
-To get started, refer the [VMware agentless migration](./tutorial-migrate-vmware.md) and [Hyper-V agentless migration](./tutorial-migrate-hyper-v.md) tutorials.
+To get started, refer the [VMware agentless migration](tutorial-migrate-vmware.md) and [Hyper-V agentless migration](./tutorial-migrate-hyper-v.md) tutorials.
 
 ### How do I gauge the bandwidth requirement for my migrations?
 
@@ -323,4 +323,4 @@ When replication starts for a VM, an initial replication cycle occurs in which f
 You can work out the bandwidth requirement based on the volume of data needed to be moved in the wave and time within which you would like initial replication to complete (ideally you’d want initial replication to have completed at least 3-4 days prior to the actual migration window to give you sufficient time to perform a test migration prior to the actual window and to keep downtime to a minimum during the window).
 
 ## Next steps
-Learn more about migrating [VMware VMs](./vmware/tutorial-migrate-vmware.md), [Hyper-V VMs](tutorial-migrate-hyper-v.md), and [Physical servers](tutorial-migrate-physical-virtual-machines.md).
+Learn more about migrating [VMware VMs](tutorial-migrate-vmware.md), [Hyper-V VMs](tutorial-migrate-hyper-v.md), and [Physical servers](tutorial-migrate-physical-virtual-machines.md).

articles/migrate/common-questions-server-migration.md

@@ -200,7 +200,7 @@ After the effective utilization value is determined, the storage, network, and c
 
 If you use *as on-premises sizing*, Azure VMware Solution assessment doesn't consider the performance history of the VMs and disks. Instead, it allocates Azure VMware Solution nodes based on the size allocated on-premises. vSAN is part of all AVS SKUs' storage. Azure NetApp Files (Standard, Premium, and Ultra tiers) is used by default in the assessment if external storage can optimize the number of AVS nodes required.
 
-[Learn more](./tutorial-assess-vmware-azure-vmware-solution.md#review-an-assessment) about how to review an Azure VMware Solution assessment.
+[Learn more](tutorial-assess-vmware-azure-vmware-solution.md#review-an-assessment) about how to review an Azure VMware Solution assessment.
 
 ### CPU utilization on Azure VMware Solution nodes
 

articles/migrate/concepts-azure-vmware-solution-assessment-calculation.md

@@ -12,15 +12,15 @@ ms.date: 10/14/2024
 # Enable Arc on Migrate inventory 
 
 
-This article describes how to view the Arc status of your Migrate discovered inventory and Arc enable your on-premises servers discovered in your datacenter with Azure Migrate: Discovery and assessment tool’s [appliance-based discovery](./vmware/how-to-set-up-appliance-vmware.md).  
+This article describes how to view the Arc status of your Migrate discovered inventory and Arc enable your on-premises servers discovered in your datacenter with Azure Migrate: Discovery and assessment tool’s [appliance-based discovery](how-to-set-up-appliance-vmware.md).  
 
 The [Azure Migrate appliance](migrate-appliance.md) is a lightweight appliance that the Azure Migrate: Discovery and assessment tool uses to discover servers running in vCenter Server and to send server configuration and performance metadata to Azure. 
 
 ## Prerequisites 
 
 - Make sure you've [created](create-manage-projects.md) an Azure Migrate project. You can also reuse an existing project to use this capability. 
 - Once you've created a project, the Azure Migrate: Discovery and assessment tool is automatically [added](how-to-create-assessment.md) to the project. 
-- Discover your IT estate using Azure Migrate appliance. Follow our tutorials for [VMware](./vmware/tutorial-discover-vmware.md) or [Hyper-V](tutorial-discover-hyper-v.md) or [Physical/Bare-metal](tutorial-discover-physical.md) or other clouds to try out these steps. 
+- Discover your IT estate using Azure Migrate appliance. Follow our tutorials for [VMware](./tutorial-discover-vmware.md) or [Hyper-V](tutorial-discover-hyper-v.md) or [Physical/Bare-metal](tutorial-discover-physical.md) or other clouds to try out these steps. 
 
 ## Overview 
 

articles/migrate/how-to-arc-enable-inventory.md

@@ -22,7 +22,7 @@ This article describes how to create an Azure VMware Solution assessment for on-
 - [Create](./create-manage-projects.md) an Azure Migrate project.
 - [Add](how-to-assess.md) the Azure Migrate: Discovery and assessment tool if you've already created a project.
 - Set up an Azure Migrate appliance for [VMware vSphere](how-to-set-up-appliance-vmware.md), which discovers the on-premises servers, and sends metadata and performance data to Azure Migrate: Discovery and assessment. [Learn more](migrate-appliance.md).
-- [Import](./tutorial-discover-import.md) the server metadata in comma-separated values (CSV) format or [import your RVTools XLSX file](./tutorial-import-vmware-using-rvtools-xlsx.md).
+- [Import](./tutorial-discover-import.md) the server metadata in comma-separated values (CSV) format or [import your RVTools XLSX file](tutorial-import-vmware-using-rvtools-xlsx.md).
 
 
 ## Azure VMware Solution (AVS) Assessment overview

articles/migrate/how-to-create-azure-vmware-solution-assessment.md

@@ -54,7 +54,7 @@ This discovery process is agentless that is, nothing is installed on the target
 
     - In the manage credentials and discovery sources panel of the Appliance configuration manager, add Domain or SQL Server Authentication credentials that have Sysadmin access on the SQL Server instance and databases to be discovered or have [these permissions](migrate-support-matrix-vmware.md#configure-the-custom-login-for-sql-server-discovery) for each SQL Server instance.
     - Web apps discovery works with both domain and non-domain Windows OS credentials as long as the account used has local admin privileges on servers.
-    You can leverage the automatic credential-mapping feature of the appliance, as highlighted [here](./tutorial-discover-vmware.md#start-continuous-discovery).    
+    You can leverage the automatic credential-mapping feature of the appliance, as highlighted [here](./tutorial-discover-vmware.md#start-continuous-discovery).
 
 > [!Note]
 > For WebApp discovery, you might need to add credentials in DLL format (`netbiosdomain\user`) so that the discovery can complete successfully.

articles/migrate/how-to-discover-sql-existing-project.md

@@ -39,7 +39,7 @@ Before you get started, you need to perform the following steps:
 > [!IMPORTANT]
 > You'll need to have at least one replicating virtual machine in the project before you can add a scale-out appliance for migration.
 
-To learn how to perform the above, review the tutorial on [migrating VMware virtual machines to Azure with the agentless migration method](./tutorial-migrate-vmware.md).
+To learn how to perform the above, review the tutorial on [migrating VMware virtual machines to Azure with the agentless migration method](tutorial-migrate-vmware.md).
 
 ## Deploy a scale-out appliance
 
@@ -202,4 +202,4 @@ In this article, you learned:
 - How to replicate VMs using a scale-out appliance
 
 
-[Learn more](./tutorial-migrate-vmware.md) about migrating servers to Azure using the Migration and modernization tool.
+[Learn more](tutorial-migrate-vmware.md) about migrating servers to Azure using the Migration and modernization tool.

articles/migrate/how-to-scale-out-for-migration.md

@@ -33,10 +33,10 @@ You must have Contributor + User Access Administrator or Owner permissions on th
 
 **Deployment** | **Details** | **Tools**
 --- | --- | ---
-**Discovery and assessment** | Perform an agentless, at-scale discovery and assessment of your servers running on any platform. Examples include hypervisor platforms such as [VMware vSphere](./tutorial-discover-vmware.md) or [Microsoft Hyper-V](./tutorial-discover-hyper-v.md), public clouds such as [AWS](./tutorial-discover-aws.md) or [GCP](./tutorial-discover-gcp.md), or even [bare metal servers](./tutorial-discover-physical.md). | Azure Migrate: Discovery and assessment <br/>
+**Discovery and assessment** | Perform an agentless, at-scale discovery and assessment of your servers running on any platform. Examples include hypervisor platforms such as [VMware vSphere](tutorial-discover-vmware.md) or [Microsoft Hyper-V](./tutorial-discover-hyper-v.md), public clouds such as [AWS](./tutorial-discover-aws.md) or [GCP](./tutorial-discover-gcp.md), or even [bare metal servers](./tutorial-discover-physical.md). | Azure Migrate: Discovery and assessment <br/>
 **Software inventory** | Discover apps, roles, and features running on VMware VMs. | Azure Migrate: Discovery and assessment
 **Dependency visualization** | Use the dependency analysis capability to identify and understand dependencies across servers. <br/> [Agentless dependency visualization](./how-to-create-group-machine-dependencies-agentless.md) is supported natively with Azure Migrate private link support. <br/>[Agent-based dependency visualization](./how-to-create-group-machine-dependencies.md) requires internet connectivity. Learn how to use [private endpoints for agent-based dependency visualization](/azure/azure-monitor/logs/private-link-security). | Azure Migrate: Discovery and assessment |
-**Migration** | Perform [agentless VMware migrations](./tutorial-migrate-vmware.md), [agentless Hyper-V migrations](./tutorial-migrate-hyper-v.md), or use the agent-based approach to migrate your [VMware VMs](./tutorial-migrate-vmware-agent.md), [Hyper-V VMs](./tutorial-migrate-physical-virtual-machines.md), [physical servers](./tutorial-migrate-physical-virtual-machines.md), [VMs running on AWS](./tutorial-migrate-aws-virtual-machines.md), [VMs running on GCP](./tutorial-migrate-gcp-virtual-machines.md), or VMs running on a different virtualization provider. | Migration and modernization
+**Migration** | Perform [agentless VMware migrations](tutorial-migrate-vmware.md), [agentless Hyper-V migrations](./tutorial-migrate-hyper-v.md), or use the agent-based approach to migrate your [VMware VMs](tutorial-migrate-vmware-agent.md), [Hyper-V VMs](./tutorial-migrate-physical-virtual-machines.md), [physical servers](./tutorial-migrate-physical-virtual-machines.md), [VMs running on AWS](./tutorial-migrate-aws-virtual-machines.md), [VMs running on GCP](./tutorial-migrate-gcp-virtual-machines.md), or VMs running on a different virtualization provider. | Migration and modernization
 
 #### Other integrated tools