Azure Storage Mover uses a purpose-built migration agent that is deployed as its own dedicated virtual machine on the on-premises hypervisor rather than as software layered onto an existing guest operating system, so for a Hyper-V environment the correct first step is to download the agent ' s VHD image from the Storage Mover resource in Azure and use it to create a new, separate agent virtual machine on the Hyper-V host, Server1, that hosts the source VM whose file shares need migrating. Once that agent VM is powered on and registered against the Storage Mover resource using an activation key generated in the portal, it can enumerate and transfer the file shares hosted on VM1 with minimal ongoing administration, running the actual copy jobs in the background while VM1 continues serving those shares, and without installing any agent software inside VM1 itself. This approach differs from Azure Migrate ' s Connected Machine agent, which is used for a different assessment-and-lift-and-shift migration workflow that projects on-premises machines into Azure as Azure Arc resources rather than for file-share transfer through Storage Mover, and installing it on either VM1 or Server1 would not accomplish the file-share migration the scenario requires.