Hi Mike Probert,
Thanks for posting your question in Microsoft Q&A forum
Could you please verify if the root cause was that the defaultAzureMigrate-HyperVSite-policy was not associated with the Hyper-V site? If that was the issue, please confirm & follow the below steps to resolve,
Register Hyper-V host: Registering Hyper-V hosts to a new Hyper-V Site with fresh vault credentials ensures any old project or tenant associations are replaced, and the hosts are cleanly enrolled in the desired Azure vault infrastructure
New Replication Policy: Creating a new replication policy and linking it to the newly created site allows the replication jobs and policies to operate on the correct infrastructure context, avoiding previous association errors.
Re-associate Hyper-V hosts: to this new site (Site Recovery infrastructure | Hyper-V Hosts | + Server | Download key file) Running the Azure Site Recovery Configurator and adding the new key file on each host refreshes the registration and agent metadata, enabling the accurate report of MARS agent versions and allowing the infrastructure to identify registered hosts for VM replication.
Following this, all Hyper-V hosts report their MARS version and VMs could be replicated.
I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes & upvote if the answer is helpful so that it can help others in the community.