For replicating a virtual machine from an on-premises Hyper-V host to a non-domain-joined host, you must use certificate-based authentication. This is because domain-based authentication like Kerberos is not possible without a domain. You will need to configure both hosts to use HTTPS for the replication protocol, which requires setting up SSL certificates to secure the connection.
How to set up certificate-based authentication
1. On the non-domain-joined replica server:
Enable it as a replica server in Hyper-V Manager.
Configure it to use HTTPS for the communication protocol.
Ensure the certificate is correctly installed and configured on both the Hyper-V replica server and the source host.
2. On the source Hyper-V host (in the domain):
When setting up the replication in the "Enable Replication" wizard, select the non-domain-joined host as the replica server.
Provide the necessary authentication credentials, which will be your certificate information, to establish the connection.
Reference:
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts

https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/configure-azure-monitor

Reference:
https://learn.microsoft.com/en-us/azure/confidential-computing/confidential-vm-overview
https://learn.microsoft.com/en-us/azure/site-recovery/concepts-trusted-vm
https://www.azurepro.ae/azure-site-recovery-now-supports-trusted-launch-vms-heres-what-you-need-to-know/